Implementation Guide › Installation and Deployment › Preparations

Preparations

In order to ensure an efficient installation; it is important for a few things to be prepared in advance:

1. The database export of the development environment. This database export should be performed using CA approved scripts that create an extract (dump) file in order to be able to import it back into the software on the production system.

   Note: It is important that the export be performed by a database user that has sufficient privileges and that this same user is accessible when importing into the database. For this purpose either the 'oblicore' account may be used since this is always created on each system, or alternatively the 'sys' account. However, ensure that the 'sys' password is available on the destination database to allow the import process to occur.

2. Database scripts- if the DBA wishes to alter the database creation scripts, then they should be verified in advance by a CA DBA. These scripts should be verified and ready in advance to allow a smooth installation. It is common for different organizations to have comments and changes that must be approved by the CA database administrator to ensure that the database configuration complies with local policies.
   • Server connectivity and accessibility-both application and web servers should have a remote connection client installed in order to support external accessibility (if physical access is not possible at the installation time, or in the future for support issues). The external accessibility is also important to allow continued monitoring of the system during a settling period. If external remote access is required, this might take longer to organize due to the additional security implications; hence it should be addressed ahead of time.
     Remote connections can be established using any of the following tools:
   • PcAnyWhere
   • Proxy Host / Master
   • Microsoft Terminal Server
   • Remote Desktop
   • VNC
   • Any other remote connection tool supported by the organization.

   Notes:

   1. Microsoft Terminal Server connects to the server by simulating a server login, unlike PcAnyWhere, VNC, Proxy and other tools.
   2. Some Oracle software cannot be installed via Microsoft Terminal Server, and must be installed locally.

3. Data source accessibility-the data source should be accessible for manual manipulation and the ODBC connection should be configured to allow the Adapters to connect to the data source.
4. Server security-in both application and web server, a user profile with local administrator rights is required. If the database platform is a standard Windows OS, a user profile with local administrator rights is also required. For Unix platforms, the database administrator should have the appropriate privileges to create the database on the server.
5. Access to Internet-this allows the System Administrator to connect to the internet for any operating system or application updates if required.
6. A standard users desktop PC, to test the application functionality. Note that the application requires the use of some ActiveX controls to be installed, which is often locked down by organizational security policies.
7. Training schedule with relevant staff-Introductory training that will allow the staff to perform the user acceptance training and to start working with the system