Appendix C: Creating War Files for Manual Installation

If you are running WebLogic Server 9.2 MP1 and using managed servers, then you must deploy all of the ALSM war files to the managed servers manually. All of the war files should be deployed to the managed server; apcontainer.war must be deployed to the Admin server.

The installer generates the following files in the <ALSM_install>/installer_work/deploy_stage directory:

Optional

Deploying the war files

Basic management components

Sample web services (tutorial.war, tutorialClient.war, tutorialBackup.war, bookmart.war, bookmartClient.war
apcentral.war
apcontainer.war
apasc.war
apmonitor.war

Exception management components

apexmrt.war
notifier.war
apexm.war

Service level management components

aqms.war
notifier.war

Note:

If you are installing the service level components in the same container as the exception management components, you do not need to install another copy of this

domain.war
apwebui.war

Enabling Observation of Service Dependencies

You can view the dependencies among services in the ALSM Management Console. To enable this functionality, complete the following procedure:

Copy ap-mto-runtime.jar to /WebLogic_home/weblogic81/server/lib. You should add this file to any server that hosts services for which you want to observe dependencies. ALSM does not track dependencies of its system services, so you do not need to place this file in the servers hosting the sphere, or service-level or exception management components unless those servers also host business services.
In that same directory (for each server into which you copied the JAR file), edit commEnv.cmd and add the following line to WEBLOGIC_CLASSPATH:

%WL_HOME%\server\lib\ap-mto-runtime.jar

Example

set WEBLOGIC_CLASSPATH=%WL_HOME%\server\lib\ap-mto-runtime.jar;%JAVA_HOME%\lib\tools.jar;%WL_HOME%\server\lib\weblogic_sp.jar;%WL_HOME%\server\lib\weblogic.jar