Target System Requirements

In the target system, complete the following requirements:

1.     All the basic software required for the installation of OFSAA applications (including infrastructure) are installed and working on the machine identified as the Target OFSAA instance. You can use the Environment Check utility to verify system readiness. For details on how to use the Environment Check Utility, see the OFS Analytical Applications Environment Check Utility Guide.

For details on the software and hardware requirements, see the Hardware and Software Requirements section in the OFS AAAI Application Pack Installation and Configuration Guide.

 

NOTE

Upgrade the Target OS version to the same version as that of the Source OS. Binaries are OS version specific and cloning requires that there is no mismatch of library files.

 

2.     The web server and the web application server are configured. For details on how to configure web servers, see the Configuring Web Server section in the OFS AAAI Application Pack Installation and Configuration Guide.

3.     The OFSAA installation directory is set as $FIC_HOME with the 750 permission.

For example, /scratch/ofsaanew/OFSAA

4.     The OFSAA staging/metadata repository directory is set as ftpshare with the 775 permission.

For example, /scratch/ofsaanew/ftpsharenew

5.     The database connection details such as the RAC/NON-RAC URL, the SID/Service Name, and the user credentials are available.

 

NOTE

Create a new database instance that is different from the database instance used in the Source OFSAA instance.

 

6.     The web server and the web application server identified for the deployment of the OFSAA applications are installed and configured on the machine which is identified as the web server and web application server.

 

NOTE

If you intend to use the same web application server, then create a separate profile (WebSphere) or a domain (WebLogic).

 

7.     The details of the WebSphere profile or the WebLogic domain or the Tomcat context are available.

 

NOTE

Before executing the utility, ensure to configure the RevLog4jConfig.xml file with the default log paths.