Issues Interacting With BEA WebLogic Servers

This section describes known issues with the WebLogic application.

Restart Option for WebLogic Applications Does Not Function (3932)

Selecting the restart option for WebLogic applications causes errors upon application installation.

Workaround: Do not select the restart option.

SSL Connections to WebLogic Administration Servers Are Not Supported (3919)

When setting up a WebLogic administration server in the N1 Service Provisioning System 4.1, clicking the Secure checkbox will attempt to setup connectivity using SSL. This causes an error when attempting to perform actions that require access to the WebLogic administration server.

Workaround: Always setup WebLogic administration server connections with requiring SSL connectivity. Do not check the Secure checkbox.

Some Changes May Not Appear in Comparison Results for WebLogic Applications (3851/3854/3857)

Changes to Deployment Attributes, for example deployment ordering, staging mode, or deployed, made of WebLogic Applications from the WebLogic Administration Console will not appear in the N1 Service Provisioning System 4.1 comparison results.

Workaround: Make all Deployment Attribute changes to WebLogic Applications through the N1 Service Provisioning System 4.1.

Comparison Results Incorrect For Content Changes Made to the On Disk Representation of WebLogic Application Archives (3835)

If a WebLogic Application is installed using the N1 Service Provisioning System 4.1 and then content changes are made to the on disk WAR archive on the administration server, the changes are not reported in comparison results. The problem does not occur when configuration changes are made.

Workaround: Comparisons can be customized using the generate and prepare extensions with more capabilities to pre-process the on disk representation prior to running the comparison. This may require some advanced scripting.