Issues Interacting With the BEA WebLogic Plug-In

This section describes known issues with the WebLogic plug-in.

EJB Component Is Not Uninstalled (5109783)

If you run the default uninstall procedure for an EJB component that was deployed to more than one virtual WebLogic managed server and select only one of the managed servers to be uninstalled, the EJB component does not appear to be uninstalled from the managed server.

After the uninstall, if you click the tab on the WebLogic console for the managed server from which you uninstalled the EJB, the console correctly reports that the EJB is no longer deployed. Also, when you click the EJB tab, the console reports that the EJB is no longer targeted at the managed server from which it was uninstalled.

However, on the EJB tab, the console reports that the EJB is deployed on the managed server.

If you uninstall the EJB from all managed servers, the EJB is removed from the WebLogic console correctly.

Workaround: The WebLogic Plug-In is uninstalled correctly. Ignore the erroneous display.

Comparison Fails With Snapshot Error When WebLogic Application Was Deleted From the WebLogic Console (6186456)

If you deploy a WebLogic web application that contains a web application container with a WAR file and web application settings and include a snapshot and then delete the web application from the WebLogic Console, the following error displays if you run a model to install comparison on the web application component:

Could not complete operation on webapp domain.
No such webapp exists on domain /domain/. (310101)

The comparison should report a difference between the model and what is installed on the server. However, the comparison fails.

Workaround: No workaround is available.

Comparison Does Not Report Differences For Undeployed Components (6186457)

If you use the WebLogic Console to undeploy a WebLogic WAR or EJB component from a managed server or cluster, the WebLogic Console reports that the WAR or EJB component is still targeted to that managed server or cluster. Consequently, if you run a model to install comparison on the managed server or cluster, the comparison reports no differences. The model to install comparison checks the WebLogic Console and reports targeted applications as deployed.

Workaround: No workaround is available.

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

If a WebLogic application is installed using the N1 Grid Service Provisioning System 5.0 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 preprocess the on disk representation prior to running the comparison. This type of customization might require some advanced scripting.

Cannot Deploy WebLogic EAR Component to a Managed Server Using Service Pack 3 or Later (6200140)

If you are using WebLogic 7.0 Service Pack 3 or later, you cannot deploy WebLogic EAR components. During an attempt to deploy an EAR component, the following message appears:

Execution ended abnormally. (025075)

Workaround: No workaround is available.

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

When setting up a WebLogic administration server in the N1 Grid Service Provisioning System 5.0, clicking the Secure checkbox will attempt to set up connectivity using SSL. This selection 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 select the Secure checkbox.