This chapter explains how to install LSR 10.2 on Oracle WebLogic Server for all platforms.
Ensure the following:
You have installed Oracle Communications MetaSolv Solution 6.3 or later.
The following environment variables are set:
PATH=jdkVersion/bin:$PATH MW_HOME=/oracle/middleware/oracle_home JAVA_HOME=jdkVersion
where:
MW_Home is the directory in which Oracle WebLogic Server is installed.
jdkVersion is the directory location where you installed the JDK.
Note:
LSR 10.2 is supported only on MSS 6.3 and later.See MSS Installation Guide for information on software versions and requirements.
To install LSR 10.2:
From MSLV_Home, enter the following command:
java -jar Lsr.R10_2_0.buildNo_M63.jar
where:
MSLV_Home is the directory in which the MetaSolv Solution software is installed.
buildNo is the build number.
For example:
java -jar Lsr.R10_2_0.b47_M63.jar
The Select MetaSolv home directory window appears.
From the Look In list, select a directory in which the installation program files can be stored and used during the installation process, and then click Select.
A directory named lsr10.2installer is automatically created in the selected directory. Oracle recommends choosing your MSLV_Home directory for this task.
The installation program launches the installation process by running setup.sh (UNIX/Linux) or setup.cmd (Windows) in the MSLV_Home/lsr10.2installer directory.
The welcome screen for the MetaSolv Solution LSR installation appears.
Click Next.
The Details window appears.
Enter the path and name of the MetaSolv Home directory, MetaSolv Domain directory, and MetaSolv Server directory or click Open to search for the directories.
Click Next.
The Install Type window appears.
Select one of the following installation types:
Install all LSR Files
Install Only LSR EAR File
When prompted for the Install Type, if the environment is a clustered environment, you can choose an option to extract the EAR file only. Use this option to extract the EAR file on the Admin server for deployment to separate managed servers. For a non-clustered environment, choose the option to install and deploy all files.
Click Next.
The Install Summary window appears.
Click Finish.
Note:
If you are installing LSR in a clustered environment, and if you select admin server as the MetaSolv server, then you must copy the loggingconfig_LSR10.xml file to the MSLV_Home\m63domain\servers\mslvadmin\appserver\config directory.where:
MSLV_Home is the directory on the clustered server where MSS is installed; for example, /opt/m63Cluster/cluster.
m63domain is the domain home directory.
mslvadmin is directory where the administration server is installed.
Rename this file to loggingconfig_cluster-LSR10.xml and place it in every managed server's config directory at MSLV_Home\mslv01\appserver\config directory, where mslv01 is the name of the directory where the managed server is installed.
You must apply the contents of the prodfixsql directory.
To apply LSR database changes:
Run the lsr_master.sql file located in the MSLV_Home/server/appserver/sql/LSR10/prodfixsql directory, where server is the name of the WebLogic server.
Run DBHealth, which recompiles all invalid objects.
Deploying LSR 10.2 on the application server in a single-server environment involves the following:
Undeploying the existing LSR 10.2 application from the application server
Deploying LSR 10.2 on the application server
To undeploy LSR 10.2 from the application server:
Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console
where:
ServerName is the name of the administration server.
Port is the administration server port number.
For example:
http://myserver:7001/console
Enter the administration user name and password when prompted and press Enter.
Under the Change Center, click Lock & Edit.
Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.
On the Control tab, select LSR10.
From the Stop list, select Force Stop Now.
Ensure that the state of the LSR 10.2 application has changed from Active to Prepared.
Select LSR10 from the Configuration tab and click Delete.
The Delete Application Assistant window appears.
Click Yes.
Under the Change Center, click Activate Changes.
The LSR 10.2 application is undeployed.
Before you deploy LSR 10.2, ensure the following servers are running:
Administration server
If it is not running, start it using the following startup script:
For UNIX:
domain_directory/startServerName.sh
For Windows:
domain_directory/startServerName.cmd
where:
domain_directory is the WebLogic server domain directory.
ServerName is the name of the administration server.
To deploy LSR 10.2 on the application server:
Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console
where:
ServerName is the name of the administration server.
Port is the administration server port number.
For example:
http://myserver:7001/console
Enter the administration user name and password when prompted and press Enter.
Under the Change Center, click Lock & Edit.
Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.
On the Configuration tab, click Install.
The Install Application Assistant window appears.
Under Current Location, navigate to the directory from which you want to deploy LSR 10.2 (for example, opt/metasolv/mslv01/appserver/deploy), select LSR10.ear, and then click Next.
The Choose targeting style window appears.
Select Install this deployment as an application and click Next.
Under Source accessibility, select I will make the deployment accessible from the following location.
Click Finish.
Under the Change Center, click Activate Changes.
Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.
On the Control tab, select LSR10.
From the Start list, select Servicing all requests.
The Start Application Assistant window appears.
Click Yes.
Ensure that the state of the LSR 10.2 application has changed from Prepared to Active.
If you receive the following error in the appserver.mss.log file during LSR deployment,
”log4j: ERROR Attempted to append to closed appender named [XMLFileApp”
do the following:
Open the loggingconfig_LSR10.xml file located in the MSLV_Home/server/appserver/config directory, where server is the name of the WebLogic server.
Remove the following entries:
category name="cmm.LSR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger"additivity="false"><level value ="error" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/> <appender-ref ref="XMLFileApp"/> </category> <category name="LSR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false"> <level value="error" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/> <appender-ref ref="XMLFileApp"/> </category> <category name="cmm.LSR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false"> <level value ="error" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/> <appender-ref ref="XMLFileApp"/> </category>
Save and close the file.
Restart the server.
If the administration server for the domain is on a machine where no managed server process is running, you can run the LSR installer and select the option to only extract the EAR file. The EAR file must reside on the machine where the admin server is running to deploy to the managed servers in the domain.
Deploying LSR 10.2 on the application server in a clustered-server environment involves the following:
Undeploying the existing LSR 10.2 application from the application server
Deploying LSR 10.2 on the application server
To undeploy LSR 10.2 from the application server:
Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console
where:
ServerName is the name of the administration server.
Port is the administration server port number.
For example:
http://myserver:7001/console
Enter the administration user name and password when prompted and press Enter.
Under the Change Center, click Lock & Edit.
Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.
On the Control tab, select cluster-LSR10.
From the Stop list, select Force Stop Now.
Ensure that the state of the LSR 10.2 application has changed from Active to Prepared.
On the Configuration tab, select cluster-LSR10 and click Delete.
The Delete Application Assistant window appears.
Click Yes.
Under the Change Center, click Activate Changes.
The LSR 10.2 application is undeployed.
Before you deploy LSR 10.2 deployment, ensure the following servers are running:
Administration server
If it is not running, start it using the following startup script:
For UNIX:
domain_directory/startAdminServer.sh
For Windows:
domain_directory/startAdminServer.cmd
where:
domain_directory is the WebLogic server domain directory.
Managed server or servers
Start any managed servers that are not running using the following startup script:
For UNIX:
domain_directory/startServerName.sh
For Windows:
domain_directory/startServerName.cmd
where:
domain_directory is the WebLogic server domain directory.
ServerName is the name of the administration server.
To deploy LSR 10.2 on the application server:
Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console
where:
ServerName is the name of the administration server.
Port is the administration server port number.
For example:
http://myserver:7001/console
Enter the administration user name and password when prompted and press Enter.
Under the Change Center, click Lock & Edit.
Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.
On the Configuration tab, click Install.
The Install Application Assistant window appears.
Under Current Location, navigate to the directory from which you want to deploy LSR 10.2 (for example, opt/metasolv/mslv01/appserver/deploy).
Select cluster-LSR10.ear, and click Next.
The Choose targeting style window appears.
Select Install this deployment as an application and click Next.
The Select deployment targets window appears.
Under Clusters, select All servers in the cluster.
Under Source accessibility, select I will make the deployment accessible from the following location.
Click Finish.
Under the Change Center area, click Activate Changes.
Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.
On the Control tab, select cluster-LSR10.
From the Start list, select Servicing all requests.
The Start Application Assistant window appears.
Click Yes.
Ensure that the state of the LSR 10.2 application has changed from Prepared to Active.
If you receive the following error in the appserver.mss.log file during LSR deployment,
”log4j: ERROR Attempted to append to closed appender named [XMLFileApp”
do the following:
Open the loggingconfig_LSR10.xml file located in the MSLV_Home/managedserver/appserver/config directory, where managedserver is the WebLogic managed server.
Remove the following entries:
category name="cmm.LSR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger"additivity="false"><level value ="error" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/> <appender-ref ref="XMLFileApp"/> </category> <category name="LSR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false"> <level value="error" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/> <appender-ref ref="XMLFileApp"/> </category> <category name="cmm.LSR" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLogger" additivity="false"> <level value ="error" class="com.metasolv.common.framework.logging.api.log4jext.MSLVLevel"/> <appender-ref ref="XMLFileApp"/> </category>
Save and close the file.
Restart the server.
The process for using LSR with Web services involves the following steps:
Deploying LSR Web Service on the Application Server in a Single Server Environment
Deploying LSR Web Service on the Application Server in a Clustered Environment
Deploying LSR Web service on the application server in a single-server environment involves the following:
Undeploying the existing LSR Web service 10.2 application from the application server
Deploying LSR Web service 10.2 on the application server
To undeploy LSR Web service 10.2 from the application server:
Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console
where:
ServerName is the name of the administration server.
Port is the administration server port number.
For example:
http://myserver:7001/console
Enter the administration user name and password when prompted and press Enter.
Under the Change Center, click Lock & Edit.
Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.
On the Control tab, select LSR_WebService.
From the Stop list, select Force Stop Now.
Ensure that the state of the LSR Web service 10.2 application has changed from Active to Prepared.
On the Configuration tab, select LSR_WebService and click Delete.
The Delete Application Assistant window appears.
Click Yes.
Under the Change Center, click Activate Changes.
The LSR Web service 10.2 application is undeployed.
Before you deploy LSR Web service 10.2, ensure the following servers are running:
Administration server
If it is not running, start it using the following startup script:
For UNIX:
domain_directory/startServerName.sh
For Windows:
domain_directory/startServerName.cmd
where:
domain_directory is the WebLogic server domain directory.
ServerName is the name of the administration server.
To deploy LSR Web service 10.2 on the application server:
Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console
where:
ServerName is the name of the administration server.
Port is the administration server port number.
For example:
http://myserver:7001/console
Enter the administration user name and password when prompted and press Enter.
Under the Change Center, click Lock & Edit.
Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.
On the Configuration tab, click Install.
The Install Application Assistant window appears.
Under Current Location, navigate to the directory from which you want to deploy LSR Web service 10.2 (for example, opt/metasolv/mslv01/appserver/deploy), select LSR_WebService.ear, and then click Next.
The Choose targeting style window appears.
Select Install this deployment as an application and click Next.
Under Source accessibility, select I will make the deployment accessible from the following location.
Click Finish.
Under the Change Center, click Activate Changes.
Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.
On the Control tab, select LSR_WebService.ear.
From the Start list, select Servicing all requests.
The Start Application Assistant window appears.
Click Yes.
Ensure that the state of the LSR Web service 10.2 application has changed from Prepared to Active.
Deploying LSR Web service on the application server in a clustered-server environment involves the following:
Undeploying the existing LSR Web service 10.2 application from the application server
Deploying LSR Web service 10.2 on the application server
To undeploy LSR Web service 10.2 from the application server:
Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console
where:
ServerName is the name of the administration server.
Port is the administration server port number.
For example:
http://myserver:7001/console
Enter the administration user name and password when prompted and press Enter.
Under the Change Center, click Lock & Edit.
Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.
On the Control tab, select LSR_WebService.
From the Stop list, select Force Stop Now.
Ensure that the state of the LSR Web service 10.2 application has changed from Active to Prepared.
On the Configuration tab, select LSR_WebService and click Delete.
The Delete Application Assistant window appears.
Click Yes.
Under the Change Center, click Activate Changes.
The LSR Web service 10.2 application is undeployed.
Before you deploy LSR Web service 10.2, ensure the following servers are running:
Administration server
If it is not running, start it using the following startup script:
For UNIX:
domain_directory/startAdminServer.sh
For Windows:
domain_directory/startAdminServer.cmd
where:
domain_directory is the WebLogic server domain directory.
Managed server or servers
Start any managed servers that are not running using the following startup script:
For UNIX:
domain_directory/startServerName.sh
For Windows:
domain_directory/startServerName.cmd
where:
domain_directory is the WebLogic server domain directory.
ServerName is the name of the administration server.
To deploy LSR Web service 10.2 on the application server:
Start the WebLogic Server Administration Console using the following URL:
http://ServerName:Port/console
where:
ServerName is the name of the administration server.
Port is the administration server port number.
For example:
http://myserver:7001/console
Enter the administration user name and password when prompted and press Enter.
Under the Change Center, click Lock & Edit.
Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.
On the Configuration tab, click Install.
The Install Application Assistant window appears.
Under Current Location, navigate to the directory from which you want to deploy LSR Web service 10.2 (for example, opt/metasolv/mslv01/appserver/deploy), select LSR_WebService.ear, and then click Next.
The Choose targeting style window appears.
Select Install this deployment as an application and click Next.
Under Source accessibility, select I will make the deployment accessible from the following location.
Click Finish.
Under the Change Center, click Activate Changes.
Expand the Domain Structure tree and click Deployments.
The Summary of Deployments window appears.
On the Control tab, select LSR_WebService.ear.
From the Start list, select Servicing all requests.
The Start Application Assistant window appears.
Click Yes.
Ensure that the state of the LSR Web service 10.2 application has changed from Prepared to Active.