Installing ASR 68 on MetaSolv Solution 6.3.1

Pre-Installation Checklist

Ensure the following:

You have installed MetaSolv Solution 6.3.1.
The following environmental variables are set:
```
PATH={jdk1.8}/bin:$PATH
JAVA_HOME={jdk1.8}
MW_HOME= {Oracle_Home}
```
where
- {jdk1.8} is the location where you installed JDK 1.8.
- {Oracle_Home} is the directory location where Oracle Fusion Middleware components are installed. This directory contains the base directory for WebLogic Server.

Installing ASR

To install ASR:

From MSLV_Home, enter the following command:
```
java -jar Asr.R68_0_0.buildNo_M63.jar
```
where:
- MSLV_Home is the directory in which the MetaSolv Solution software is installed.
- buildNo is the build number that contains the ASR installer.
For example:
```
java -jar Asr.R68_0_0.b32_M63.jar
```
The Select MetaSolv home directory window appears.
From the Look In list, click the down arrow and 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 asr68installer is automatically created in the selected directory. Oracle recommends choosing your MSLV_Home directory for this task. MSLV_Home is the directory in which the MetaSolv Solution software is installed.

The installation program auto-launches the installation process by invoking setup.sh (UNIX/Linux) or setup.cmd (Windows) in the MSLV_Home/asr68installer directory.

The welcome screen for the MetaSolv Solution ASR 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 any one of the following installation types:
- Install all ASR Files
- Install Only ASR 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 administration 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.
Restart the application server.

If there are multiple servers running in the domain, all servers should be restarted before deploying the application from the Management Console.

Note:

If there are multiple servers running in the domain, you must run the ASR installation for each server instance.
Continue with the procedures in "Applying the Contents of the Stored Procedures and Prodfixsql Directories".

Applying the Contents of the Stored Procedures and Prodfixsql Directories

To apply the contents of the stored procedures and prodfixsql directories:

Run the pfixSQL_Master.sql file located in the MSLV_Home/server/appserver/sql/ASR68/prodfixsql directory that was created during the install to apply the contents of the ASR prodfixsql directory to the database.

where:
- MSLV_Home is the directory in which the MetaSolv Solution software is installed.
- server is the name of the WebLogic Server.
The pfixSQL_Master.sql script calls all of the other SQL scripts delivered in the directory.
Run the asr_master.sql file located in the MSLV_Home/server/appserver/sql/ASR68/procs directory that was created during the installation to apply the contents of the ASR procs directory to the database.

The asr_master.sql file creates or replaces a series of stored procedures used in Ordering and Billing Forum (OBF) validation. These validations are for the Access Services Ordering Guidelines (ASOG) 67 and ASOG 68 versions. MetaSolv Solution created the single asr_master.sql script to call all of the other SQL scripts delivered in the directory.
Run the asr_audit_master.sql file located in the MSLV_Home/server/appserver/sql/ASR68/procs directory that was created during the installation to apply the contents of the ASR procs directory to the database.

The asr_audit_master.sql file creates or replaces a series of stored procedures and triggers used in capturing the audit and supplement history for ASR orders.
Run DBHealth to recompile all invalid objects.

To run a higher ASR version on a computer that runs a lower version, you must apply the stored procedures and prodfixsql of the higher version.

For example, you may run ASR 68 on a computer where you installed an ASR 67 service pack and applied the associated stored procedures and prodfixsql. To run ASR 68 effectively, you must apply the stored procedures and prodfixsql for ASR 68 to override those that you applied for the ASR 67 service pack.

Deploying ASR on the Application Server in a Single Server Environment

Deploying ASR on the application server in a single server environment involves the following steps:

Undeploying the Existing ASR Application from the Application Server

If you are installing an ASR68 patch or have ASR68 already deployed, undeploy the existing ASR from the application server.

To undeploy the existing ASR 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://wplsunsrv:7001/console
Enter the administration server user name and password when prompted and press Enter to log on.
Under Change Center, click Lock & Edit.
Expand the Domain Structure tree and click Deployments.

The Summary of Deployments window appears.
On the Control tab, select ASR68.
From the Stop list, select Force Stop Now.

Ensure that the state of the ASR 68 application has changed from Active to Prepared.
On the Configuration tab, select ASR68 and click Delete.

The Delete Application Assistant window appears.
Click Yes.

The ASR 68 application is undeployed along with the ASR 68 Web Services.
Under Change Center, click Activate Changes.

Deploying ASR Application on the Application Server

Before you deploy ASR, ensure that the following server is 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 ASR 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://wplsunsrv:7001/console
Enter the administration server user name and password when prompted and press Enter.
Under Change Center, click Lock & Edit.
Expand the Domain Structure tree and click Deployments.

The Summary of Deployments window appears.
On the Configuration tab, select Install.

The Install Application Assistant window appears.
Under Current Location, navigate to the directory from which you want to deploy ASR 68 (for example, opt/metasolv/mslv01/appserver/deploy), select ASR68.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 Change Center, click Activate Changes.
Expand the Domain Structure tree and click Deployments.

The Summary of Deployments window appears.
On the Control tab, select ASR68.
From the Start list, select Servicing all requests.

The Start Application Assistant window appears.
Click Yes.

Ensure that the state of the ASR 68 application has changed from Prepared to Active, which indicates that the ASR 68 application has been deployed along with the ASR 68 Web Services.

Deploying ASR on the Application Server in a Clustered Environment

If the administration server for the domain is on a machine where no managed server process is running, you can run the ASR installer and select the option to only extract the .EAR file. The .EAR file must reside on the machine where the administration server is running in order to deploy to the managed servers in the domain.

Deploying ASR on the application server in a clustered server environment involves the following steps:

Undeploying the Existing ASR Application from the Application Server

If you are installing an ASR68 patch or have ASR68 already deployed, undeploy the existing ASR from the application server.

To undeploy the existing ASR 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://wplsunsrv:7001/console
Enter the administration server user name and password when prompted and press Enter.
Under 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-ASR68.
From the Stop list, select Force Stop Now.

Ensure that the state of the ASR 68 application has changed from Active to Prepared.
On the Configuration tab, select cluster-ASR68 and click Delete.

The Delete Application Assistant window appears.
Click Yes.

The ASR 68 application is undeployed along with the ASR 68 Web Services.
Under Change Center, click Activate Changes.

Deploying ASR Application on the Application Server

Before you deploy ASR, ensure that 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 ASR 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://wplsunsrv:7001/console
Enter the administration server user name and password when prompted and press Enter.
Under Change Center, click Lock & Edit.
Expand the Domain Structure tree and click Deployments.

The Summary of Deployments window appears.
On the Configuration tab, select Install.

The Install Application Assistant window appears.
Under Current Location, navigate to the directory from which you want to deploy ASR 68 (for example, opt/metasolv/mslv01/appserver/deploy), select cluster-ASR68.ear, and then 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 Change Center, click Activate Changes.
Expand the Domain Structure tree and click Deployments.

The Summary of Deployments window appears.
On the Control tab, select cluster-ASR68.
From the Start list, select Servicing all requests.

The Start Application Assistant window appears.
Click Yes.

Ensure that the state of the ASR 68 application has changed from Prepared to Active, which indicates that the ASR 68 application has been deployed along with the ASR 68 Web Services.