Form Rendering issues when Package JDBC Modules option is used in WebLogic

You may experience form rendering issues for fragmented forms if you use the Package JDBC Modules (secure datasources) option when you configure your LiveCycle ES2 installation on WebLogic using LiveCycle Configuration Manager.

Ensure that you do not use the Package JDBC Modules (secure datasources) option when you run LiveCycle Configuration Manager. Use the following procedure to secure the data sources on your WebLogic server after you have run LiveCycle Configuration Manager. This procedure resolves the form rendering issues.

Under Domain Structure, click Security Realms.

On the next screen, select myrealm.

On the next screen, click the Users and Groups tab, and then click New.

Under Create a New User, specify the value for the properties, and then click OK.

In the Name box, type the user name (such as LCUser).
In the Password box, type the password.
In the Confirm Password box, type the password again.

Under Users, select the user name you created (LCUser in this example). On the next screen, click the Groups tab.

On the next screen, select Administrators in the Available table.

Click the right arrow button and add Administrators to the Chosen table, and then click Save.

Create a jndi.properties file in a known location and add its path in the classpath of the managed server. This file must contain the following:

java.naming.security.credentials=[password]

Under Change Center in the WebLogic Server Administration Console, click Lock & Edit.

Under Domain Structure, click Environment > Servers and, in the right pane, click the server created for the managed server.

Click the Server Start tab and, in the Class Path box, append the folder containing the jndi.properties file, as shown in these examples:

(Windows): %CLASSPATH%;[folder location];

(UNIX): $CLASSPATH:[folder location]:

Click Save and then click Activate Changes.

Restart the managed server so that the JNDI properties take effect.

Under Domain Structure, click Environment > Servers and, in the right pane, click the managed server.

On the next screen, click View JNDI Tree. A new window appears with the JNDI Tree Structure.

Under the JNDI Tree Structure, navigate to the datasource objects according to their JNDI names:

Click IDP_DS.

Click Security > Policies, and then click Add Conditions.

Select User in the Predicate List and click Next.

In the User Argument Name box, type the user name (such as LCUser), and click Add.

Click Finish to go back to the Policies screen, and then click Save.

Repeat steps 5 to 9 for EDC_DS.

Restart the managed server.

If you have already secured the datasources for Business Activity Monitoring ES2, ensure that you use the same username and password in the jndi.properties file you created for BAM. For more information, see the Installing and Deploying LiveCycle ES2 for WebLogic guide.

Twitter™ and Facebook posts are not covered under the terms of Creative Commons.

Legal Notices | Online Privacy Policy

Form Rendering issues when Package JDBC Modules option is used in WebLogic

Issue

Solution

Create a user account in the Administrator group in WebLogic's security realm:

Create a jndi.properties file:

java.naming.security.principal=[user name]

Log in to WebLogic Server Administration Console.

Secure the datasources (IDP_DS and EDC_DS):

Additional information

Ask the Community

Contact Us