7 Installing ASAP

This chapter describes how to install Oracle Communications ASAP. Before installing ASAP, read these chapters:

About Installing the ASAP Software

Note:

The term ASAP Server is used throughout this chapter when addressing all ASAP servers collectively.

Oracle recommends that you back up the Oracle WebLogic Server core software and the WebLogic Server domain before installing ASAP. For installation, ASAP must be linked to an as-yet unused WebLogic Server domain. If the ASAP installation fails, and you have not backed up the WebLogic Server domain information, you must recreate the WebLogic Server domain before installing ASAP. See "Creating a Backup of the WebLogic Server."

Note:

Before installing a new version of ASAP, Oracle recommends that you back up all data.

Types of Installation

The ASAP Server software supports three installation options. After you install ASAP, you also have the option to distribute ASAP across multiple UNIX machines.

The installation options are:

  • GUI Installer – This installer mode prompts for required values using a series of dialog boxes (see "Installing ASAP Using the GUI Installer").

  • Console Installer – A prompted installation that uses a console for you to enter values at the command line (see "Installing ASAP Using the Console Installer").

    Note:

    If you do not have a window manager on your UNIX machine, you cannot view the GUI interface. An error message appears notifying you that variables have not been set. In these situations, you must use the console installer.

  • Silent Installer – An automatic installation started from a console that uses prerecorded values entered during GUI install (see "Installing ASAP Using the Silent Installer").

  • Distributed ASAP Install – An installation of ASAP across multiple UNIX machines. (see "Installing ASAP Across Multiple UNIX Machines").

Downloading the ASAP Installation Files

To obtain and uncompress the ASAP software installation files

  1. On the target machine, log in with your UNIX user account for ASAP.

  2. On a Windows workstation, launch Internet Explorer and log in to the Oracle software delivery website.

  3. Download the ASAP software.

  4. Transfer the downloaded TAR file to the target ASAP server machine.

  5. Uncompress and untar the downloaded file to the ASAP_src.

    For example:

    # tar –xvf tar_filename

    The TAR file expands into a set of sub-directories containing the installation files.

  6. Locate and read any README files in the install set.

Note:

If you are concerned that there is insufficient temporary disk space, you can create another temp directory before starting the installation. The installation program writes temp files to that directory. You can optionally use the current or home directory.

The -is:tempdir switch enables you to identify a temporary directory on a partition. Enter the command as follows:

  • asap70ServerAIX61 -is:tempdir Temp_directory_name

  • asap70ServerSolaris -is:tempdir Temp_directory_name

  • asap70ServerLinux -is:tempdir Temp_directory_name

  • asap73ServerHP11iV3Itanium -is:tempdir Temp_directory_name

Configuring, Backing Up, and Starting WebLogic Before Installing ASAP

Before you begin installation of the ASAP server software, you must copy the jconn4.jar file from the ASAP_src/asap_utils folder into the domain_home/lib directory.

To configure, backup, and start the WebLogic server, use the following procedure:

Note:

When you start your WebLogic Server instance, make sure that the ASAP_home/Environment_Profile has not been sourced in your WebLogic server terminal session. This file references environment variables that are incompatible with your WebLogic server. In the context of this procedure, ASAP has not been installed, and this scenario is not possible; however, it can occur after you have installed ASAP.

  1. Copy the jconn4.jar file from your ASAP installation directory to your WebLogic Server domain lib folder.

    cp ASAP_src/asap_utils/jconn4.jar domain_home/lib/

  2. Archive your WebLogic Server domain. For example,

    cd domain_home/
tar cf domain_name.tar domain_home/

    Where domain_name is the name you want to give your WebLogic Server domain backup file.

  3. Start the WebLogic server. You can use nohup to run your WebLogic server in the background.

    cd domain_home/
nohup ./startWebLogic.sh &

  4. Monitor nohup.out file to make sure the domain goes into the RUNNING mode.

    tail -f nohup.out

    The output from this command should end with the following text when it enters the RUNNING mode.

    <Jul 15, 2014 2:50:29 PM EDT> <Notice> <WebLogicServer> <BEA-000360> <Server started in RUNNING mode>

  5. Stop the tail process.

    Ctrl-C

  6. Exit from your oracle user session.

    exit

Installing an ASAP Demonstration System

The instructions in this section assume that you are installing all of the ASAP components, including the database, on a single computer. This computer should meet the hardware requirements for Oracle Linux for a small ASAP system as described in "ASAP Server Hardware Requirements."

The procedure for installing a demonstration system include:

  1. Installing Oracle Linux with the Oracle Validated Package

  2. Preparing the Linux Environment

  3. Downloading and Extracting the ASAP Installation Files

  4. Downloading and Installing the Oracle Database and Client Software

  5. Configuring Database Listener

  6. Creating the Database Instance

  7. Creating Tablespace, Tablespace Users, and Granting User Privileges

  8. Downloading and Installing the WebLogic Server Software

  9. Creating and Configuring a WebLogic Server Domain

  10. Installing ASAP Using the GUI Installer

Installing Oracle Linux with the Oracle Validated Package

Use the following procedure to install Oracle Linux with the Oracle validated software package.

  1. On a Windows workstation, launch Internet Explorer and log in to the Oracle software delivery website.

  2. Select and download Oracle Linux version required for the x86 64 bit platform (see
    "Software Requirements").

  3. Burn the Oracle Linux ISO image to a DVD and install the Oracle Linux software on an x86 64 bit platform using the GUI Linux installer.

  4. Select default installation options until you reach the page where it gives you the option to customize your installation. Select the Customize now, and click Next.

  5. Select Base System from the left menu.

  6. Select System Tools from the right menu.

  7. Click Optional packages.

  8. Select the Oracle Validated RPM package from the package list, and click Next.

    This package provides the following features:

    • Preconfigured Oracle Linux kernel configuration, suitable for the Oracle database. These kernel configuration attributes are sufficient for an ASAP demonstration system; however, for a production environment or test system, configure your kernel parameters as describe in "Setting Linux Kernel Parameters."

    • All Oracle packages required to install and run the Oracle database software

    • Preconfigured oracle database user and groups for database installation

  9. Click Close.

  10. Click Next and continue the installation process.

  11. During the Oracle Linux configuration process, select the following options:

    • Enable the firewall and set SSH, Telnet, and FTP as trusted protocols.

    • Set SELinux to Permissive.

    • Check Enable Network Time Protocol in the Network Time Protocol tab.

Preparing the Linux Environment

Use the following procedure to prepare your Oracle Linux Environment. The steps described in this procedure include:

  • Installing the JDK for WebLogic Server

  • Creating a symbolic link to the JDK from Mozilla Firefox to enable the Java plugin

  • Creating an ASAP user and group

  • Configuring a host name for your installation in the /etc/hosts file

  • Creating the directories for your Oracle Database installation

  • Configuring the oracle user .bashrc file

To prepare the Linux environment:

  1. Log into Oracle Linux as root.

  2. Download the Oracle Linux Java SE version required for the WebLogic Server (see "Software Requirements").

  3. Change the permissions on the Java installation file:

    chmod a+x jdk_install_file

    Where jdk_install_file is the java installation file.

  4. Move the file to a system-wide location such as /usr/local. For example:

    mv jdk_install_file /usr/local

  5. From the new location, install Java SE.

    ./jdk_install_file

  6. Create a symbolic link from the /usr/lib/mozilla/plugins directory to Java_home /jre/lib/i386/libnpjp2.so file (where Java_home is the location where you installed the JDK) to enable the Java plugin for Mozilla Firefox. For example:

    cd /usr/lib/mozilla/plugins
ln -s /usr/local/jdk1.7.x/jre/lib/i386/libnpjp2.so

  7. Create an ASAP user and group as described in "Configuring a UNIX ASAP Group and User."

  8. Determine your IP address for your platform.

    ifconfig

  9. Edit the /etc/hosts file and provide a host name for your IP address. For example:

    # Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1 localhost.localdomain localhost loopback
::1 localhost6.localdomain6 localhost6
10.156.53.74 testsystem.oracle.us.com testsystem loghost

  10. Create and assign permissions to folders in preparation to install your Oracle database. For example:

    mkdir -p /u01/app/
chown -R oracle:oinstall /u01/app/
chmod -R 775 /u01/app/
mkdir /u01/app/oradata /u01/app/fast_recovery_area
chown oracle:oinstall /u01/app/oradata/u01/app/fast_recovery_area
chmod 755 /u01/app/oradata /u01/app/fast_recovery_area

  11. Edit the oracle user's .bashrc system setup file using a text editor such as gedit or vi. This example provides common Oracle database environment variables and paths:

    # .bashrc
 
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
 
# User specific aliases and functions
export ORACLE_SID=ASAP
export ORACLE_HOME=/u01/app/oracle/product/12.1.3/dbhome_1
PATH=$PATH:$HOME/bin:/u01/app/oracle/product/12.1.3/dbhome_1/bin/
export PATH
 
umask 022

Downloading and Extracting the ASAP Installation Files

To download the ASAP installation files use the procedure described in "Downloading the ASAP Installation Files" with the following exceptions:

  • Log in to your Oracle Linux workstation with your asap user account.

  • Download the file directly to your Oracle Linux workstation using Mozilla Firefox.

  • For this demonstration system, create a new directory called asapinstaller in the /home/asap directory and extract the ASAP installation files in this directory. For example:

    cd /home/asap
mkdir asapinstaller
mv ASAP.R7_3_0.B165.linux.tar asapinstaller/
cd asapinstaller
tar -xvf ASAP.R7_3_0.B165.linux.tar

Downloading and Installing the Oracle Database and Client Software

Use the following procedure to download and install the Oracle database and client software.

  1. Log in as the oracle user.

  2. Log in to the Oracle software delivery website.

  3. Select and download the Oracle Database version you require for the Linux x86-64 platform (see "Software Requirements").

    Note:

    Do not download the client from the Oracle software delivery website.

  4. Use the following command to extract the content from the installation files:

    unzip file_name.zip

    Where file_name is the name of the database installation file. There are typically two installation files.

  5. Run the database installer.

    ./database/runInstaller

  6. During the installation process select the default options for all fields except for the following:

    1. Install database software only

    2. Single Database Instance

    3. Enterprise Edition

  7. Follow the GUI instructions to finish the installation.

  8. Download and install the client as described in "Downloading and Installing the Oracle Client Software" using the default options for all fields except for the following:

    1. Select the Administrator Installation Type

    2. Enter /u01/app/oracle/product/12.1.0.2/client_1 for the Software Location

    3. Enterprise Edition

Configuring Database Listener

Use the following procedure to configure a database listener.

  1. Run the Network Configuration Assistant (netca).

    netca

    The Network Configuration Assistant: Welcome screen appears.

  2. Select Listener Configuration.

    The Network Configuration Assistant: Listener Configuration Listener screen appears.

  3. Select Add.

    The Network Configuration Assistant: Listener Configuration, Listener Name screen appears.

  4. Accept default LISTENER. Click Next.

    The Network Configuration Assistant: Listener Configuration, Select Protocols screen appears.

  5. Select Next to accept the default TCP selection.

    The Network Configuration Assistant: Listener Configuration, TCP/IP Protocol screen appears.

  6. Select Use the standard port number 1521. Click Next.

    The Network Configuration Assistant: Listener Configuration, More Listeners? screen appears.

  7. Select No. Click Next.

    The Network Configuration Assistant: Listener Configuration Done screen appears.

  8. Click Next.

  9. Click Finish.

Creating the Database Instance

Use the following procedure to configure a database instance.

  1. Run the Database Configuration Assistant (dbca).

    dbca

    The Database Configuration Assistant: Welcome screen appears.

  2. Click Next.

    The Database Configuration Assistant: Step 1 of 12: Operations screen appears.

  3. Select Create a Database.

  4. Click Next.

    The Database Configuration Assistant: Step 2 of 12: Database Templates screen appears.

  5. Select General Purpose or Transaction Processing.

  6. Click Next.

    The Database Configuration Assistant: Step 3 of 12: Database Identification screen appears.

  7. Enter ASAP for the Global Database Name and SID fields.

  8. Click Next.

    The Database Configuration Assistant: Step 4 of 12: Management Options screen appears.

  9. Click Next to accept the default options.

    The Database Configuration Assistant: Step 5 of 12: Database Credentials screen appears.

  10. Select Use the Same Administrative Password for All Accounts.

  11. Enter a Password in the Password and Confirm Password fields.

    Note:

    Mark down the password you used. You will need this password for the procedure described in "Creating Tablespace, Tablespace Users, and Granting User Privileges."

  12. Click Next.

    The Database Configuration Assistant: Step 6 of 12: Database File Locations screen appears.

  13. Click Next to accept the default options for storage type and location of data files.

    The Database Configuration Assistant: Step 7 of 12: Recovery Configuration screen appears.

  14. Click Next to accept the default flash recovery area options.

    The Database Configuration Assistant: Step 8 of 12: DatabaseContent screen appears.

  15. Click Next to accept default options for Sample Schema and Custom Scripts tabs.

    The Database Configuration Assistant: Step 9 of 12: Initialization Parameters screen appears.

  16. Click Finish.

    The Create Database - Summary screen appears.

  17. Click OK to create your database.

  18. Click Exit.

Creating Tablespace, Tablespace Users, and Granting User Privileges

Use the following procedure to create a tablespace, tablespace user, and grant privileges.

  1. From the Unix terminal, log into the database instance with the sys user account.

    sqlplus sys/password as sysdba

    Where password is the password you choose for your sys account (see "Creating the Database Instance").

  2. Run the following command to create your tablespace.

    CREATE TABLESPACE "POOL_TS" LOGGING DATAFILE '/u01/app/oracle/POOLS_TS.dbf' SIZE 6000M REUSE AUTOEXTEND ON NEXT 1000K MAXSIZE UNLIMITED DEFAULT STORAGE (INITIAL 128K NEXT 128K MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0);

  3. Create a new user for the tablespace. For example:

    CREATE USER "ASAP_SYS" PROFILE "DEFAULT" IDENTIFIED BY "ASAP_SYS" DEFAULT TABLESPACE "POOL_TS" TEMPORARY TABLESPACE "TEMP" ACCOUNT UNLOCK;

  4. Grant privileges to your tablespace user account. For example:

    GRANT CREATE ANY CONTEXT TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT CREATE ANY TABLE TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT CREATE ANY VIEW TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT CREATE SNAPSHOT TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT CREATE SYNONYM TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT CREATE TABLE TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT CREATE USER TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT CREATE VIEW TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT GRANT ANY PRIVILEGE TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT QUERY REWRITE TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT UNLIMITED TABLESPACE TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT SELECT ON "SYS"."V_$PARAMETER" TO "ASAP_SYS" WITH GRANT OPTION;
GRANT "CONNECT" TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT "DBA" TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT "EXP_FULL_DATABASE" TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT "IMP_FULL_DATABASE" TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT "RESOURCE" TO "ASAP_SYS" WITH ADMIN OPTION;
GRANT EXECUTE ON SYS.DBMS_LOCK TO "ASAP_SYS" WITH GRANT OPTION;
GRANT SELECT ON DBA_TABLESPACES TO "ASAP_SYS" WITH GRANT OPTION;

  5. Log out of sqlplus.

    exit

  6. Log into the root user account from the oracle user session.

    su root

  7. Copy the ora_system_procs.sh from the ASAP installation directory to the oracle user account home directory.

    cd /home/asap/asapinstaller/asap_utils/
cp ora_system_procs.sh /home/oracle

  8. Set permissions for the ora_system_procs.sh file.

    cd /home/oracle
chmod 755 ora_system_procs.sh

  9. Log out of the root user session.

    exit

  10. As oracle user, run the ora_system_procs.sh script.

    cd /home/oracle
./ora_system_procs.sh

  11. Enter Y and press Enter to continue.

  12. Enter the password you created for your sys database user account (see "Creating the Database Instance") and press Enter.

    Note:

    The script may produce the following error message. 
    drop public synonym set_session
*
ERROR at line 1:
ORA-01432: public synonym to be dropped does not exist

    Ignore this message.

  13. Become root user.

    su root

  14. Copy the Database tnsnames.ora file to your asap user account home directory.

    cp /u01/app/oracle/product/12.1.3/dbhome_1/network/admin/tnsnames.ora /home/asap

  15. Change the permissions on the tnsnames.ora file.

    cd /home/asap
chmod 755 tnsnames.ora

  16. Log out of root user.

    exit

  17. Log out of oracle user.

    exit

Downloading and Installing the WebLogic Server Software

Use the following procedure to download and install the WebLogic Server software.

  1. Log in as the asap user.

  2. Log in to the Oracle software delivery website.

  3. Select and download the WebLogic version you require for the Linux x86-64 platform (see "Software Requirements").

  4. Change the permissions on the installation .jar file so that your WebLogic Server user can run it. For example:

    chmod a+x fmw_12.1.3.0.0_wls.jar

  5. If you are running X-Windows on a remote display, export the display. For example:

    export DISPLAY=10.15.16.17:0.0.

  6. Start the WebLogic installer. For example:

    cd /usr/local/jdk1.7.x/bin/
./java -jar /home/oracle/Desktop/fmw_12.1.3.0.0_wls.jar

    Note:

    Make sure you use ./ before the java command to use the correct JDK.

  7. Click Next.

  8. Click Next to accept the default Middleware home directory (for example, /home/asap/Oracle/Middleware and follow the Installation Instructions.

  9. Select the Custom installation type from the Choose Install Type screen.

  10. Click Next.

  11. Deselect the Coherence Server components from the component list.1

  12. Click Next.

  13. Click Next to select the Local JDK (for example Sun SDK 1.7.x (/usr/local/jdk1.7.x)).

  14. Click Next to select the default product installation directory for your WebLogic Server (for example /home/asap/Oracle/Middleware/wlserver_10.3).

  15. Review the Installation Summary, and click Next to start the installation process.

  16. After the installation is complete, deselect Run Quickstart.

  17. Click Done.

Creating and Configuring a WebLogic Server Domain

Use the following procedure to create and configure a WebLogic server domain.

  1. Log in as the asap user.

  2. Follow the procedure describe in "Creating a WebLogic Server Domain" and select the default options except for those described in Table 7-1.

    Table 7-1 WebLogic Server Domain Demonstration System Installation Values

    Installer Screen Fields Value

    Specify Domain Name and Location

    Domain name:

    Domain location:

    basedomain

    /home/asap/Oracle/Middleware/user_projects/domains

    Configure Administrator User Name and Password

    Name:

    User password:

    Confirm user password:

    weblogic

    weblogic1

    weblogic1

    Select Optional Configuration

    Select only the Administrator Server option. This demonstration system does not require a managed server.

    N/A

    Configure the Administration Server

    Name:

    Listen address:

    Listen port:

    SSL listen port:

    Select SSL enabled.

    AdminServer

    All Local Addresses

    7001

    7002

  3. Configure, backup, and start the WebLogic server as described in "Configuring, Backing Up, and Starting WebLogic Before Installing ASAP."

Installing ASAP Using the GUI Installer

Use the following procedure to install an ASAP demonstration system using the GUI installer.

  1. Log in as the asap user.

  2. Define the TNS_ADMIN variable and set it to the location of your tnsnames.ora file.

    export TNS_ADMIN=/home/asap

  3. Follow the procedure describe in "Installing ASAP Using the GUI Installer" and select the default options except for those described in Table 7-2.

    Table 7-2 ASAP Demonstration System Installation Values

    Installer Screen Fields Value

    Enter Server Destination Directory

    Directory Name

    /home/asap/asap73

    Configure ASAP UNIX Environment Variables

    Environment ID

    Directory Name

    demo

    /u01/app/oracle/product/12.1.3/client_1

    Configure ASAP Database

    Name of RDBMS Server

    Oracle Server DBA User Name

    Oracle Server DBA Password

    ASAP

    ASAP_SYS

    ASAP_SYS

    Configure ASAP Database Tablespaces

    For all Data Segments and Index Segments

    For the Temporary Tablespace

    POOLS_TS


    TMP

    Configure ASAP Database User Password

    For all Password and Confirm-Password fields.

    abcd

    Configure Oracle WebLogic Server for ASAP

    Host Name of Oracle WebLogic Server

    Port Number of WebLogic Server

    User Name of Oracle WebLogic Server Administrator

    Password of Oracle WebLogic Server Administrator

    localhost.localdomain

    7001


    weblogic


    weblogic1

Installing ASAP Using the GUI Installer

Note:

If you cancel the installation of ASAP, the files that have been created in up to that point are not removed automatically. If you want to remove these files, you must do so manually. See "Re-Running the ASAP Server Installation."

Also, ASAP database schemas may have been created. Your Database Administrator can refer to ASAP_src/asap_utils/sample_drop_user.ksh for a sample script to drop the schemas that were created.

Note:

To execute ASAP server installer in GUI mode, you must set up your X-Windows properly. Consult your X-Windows Manager documentation for assistance.

If you are working from the actual UNIX machine, the GUI is displayed locally using X-Windows.

If you are working from a remote machine:

  • Enter who to get a list of current users. Locate your IP address.

  • Enter, for example, export DISPLAY=IP Address:0.0 if using bash. (The command may be slightly different if you are using a different shell.)

  • Ensure that an X-Windows client is configured and running on your remote machine before starting the GUI mode installation process.

To install the ASAP Server using the GUI installer:

  1. Log in using your UNIX user account for ASAP.

    Note:

    The ASAP Server installation process must be run while logged in using the ASAP environment user account. Oracle recommends that the ASAP user's home directory is provided as the installation location for the ASAP software so that the installation process has read/write access to the installation target directory.

  2. Ensure that the /var/tmp directory is empty. The Oracle JDBC driver uses this directory to store temporary files. If this directory is unavailable or otherwise unusable, the java virtual machine will fail, and this will cause the ASAP installation to fail.

  3. Go to ASAP_src.

  4. Start the GUI installer for the platform you are using:

    • For the IBM AIX platform:

      asap70ServerAIX61

    • For the HP Itanium platform:

      asap73ServerHP11iV3Itanium

    • For the Solaris platform:

      asap70ServerSolaris

    • For the Linux platform:

      asap70ServerLinux

    Note:

    If the installer does not launch, enter the following command at the UNIX prompt: export NO_J2D_DGA=true and then relaunch the installer.

    Note:

    The installer may show a "quota not found" message on the console. This message can be ignored.

    Note:

    Monitor the console output in the shell from which you initiate the installer. Informational and error messages are written to the console.

    The ASAP splash screen appears, followed by the Welcome dialog box.

  5. Review the pre-installation requirements on screen and ensure that you have observed the listed recommendations.

  6. Click Next.

    The Enter Server Destination Directory dialog box appears.

  7. Do one of the following:

    • In the Directory Name field, enter the name of the directory where you want to install the ASAP Server.

      Note:

      The absolute path of the directory cannot exceed 48 characters.

    • To install the ASAP Server to a specific directory, click Browse and locate the appropriate directory.

    To simplify configuration, install ASAP to the user's home directory.

  8. Click Next.

    The Select Installation Type dialog box appears.

  9. Select the type of ASAP installation you require.

    • If you selected Typical, the Disk Space Required dialog appears. This installation option installs the base ASAP components, configured the WebLogic server and database for ASAP and installs the POTS demo cartridge. Skip the next step.

    • If you selected Custom, the Select Components dialog appears. This installation option allows you to select the ASAP components you want to install. Continue with the next step.

  10. (Optional) In the Select Components dialog box, select the ASAP Server components you want to install and configure. Components and configurations that you can select are:

    • ASAP

      • ASAP core components: This component provides the core ASAP software components. You must install the ASAP core components. The other components can be installed later by re-running the installer.

      • ASAP samples and demonstration models: This component provides samples and demonstration models that you can use with ASAP. You must select this component if you want to configure ASAP demonstration models. You must de-select the Configure ASAP sub-component, Configure Oracle WebLogic server for ASAP and deploy Security, JSRP, and SADT to de-select the ASAP samples and demonstration models sub-component.

      • ASAP X2X component: This components is for Solaris only, and has been deprecated. This component provide support for ASAP to NE connectivity over X.25 and X.29 protocols.

      • ASAP SNMP component: This components is for Solaris only. This component provides support for the SNMP protocol. This component provides support for ASAP to NE connectivity over SNMP.

    • Configure ASAP

      • Configure ASAP UNIX environment variables: This configuration option configured the ASAP_home/Environment_Profile with the UNIX environment variables required to run ASAP.

      • Configure ASAP database: This configuration option creates and applies the ASAP server schemas and tables to the ASAP database instance tablespaces.

      • Configure Oracle WebLogic server for ASAP and deploy Security, JSRP, and SADT: This configuration option configures the ASAP WebLogic server components. You can also select the Configure Demonstration Service Activation Model option that provides demonstration service modes.

        Note:

        ASAP supports the following demonstration models:

        • ATM/FR Service Activation Model

        • 3G Wireless Service Activation Model

        • POTS Service Activation Model

        • IP/VPN Service Activation Model

        These demonstration models are part of the ASAP samples and demonstration models ASAP sub-component. You cannot install the demonstration models without installing this ASAP sub-component.

        You can use these demonstration models to test ASAP. See "Testing the ASAP Server Installation."

  11. Click Next.

    The Components Selected - Disk Space Required dialog appears, providing summary information on the ASAP Server installation location, the server components to be installed, and the total size (in MB) of the installation.

  12. Click Next.

    The Configure ASAP UNIX Environment Variables dialog box appears.

  13. Do the following:

    1. Select the mode that you want to operate in (Development or Production).

    2. In the ASAP Environment ID field, enter ASAP_envID (where ASAP_envID is the environment ID for your ASAP instance).

    3. Do one of the following:

      • In the Directory Name field, enter the name of the base directory of your Oracle Database client installation Oracle_client_home.

      • Click Browse and navigate to Oracle_client_home.

  14. Click Next.

    Note:

    If you receive an error message stating "Oracle Home is invalid – missing bin/sqlplus or lib/libclntsh. Please check with your system administrator and re-enter the value".

    The Configure ASAP UNIX Environment Variables - ASAP Server Port dialog box appears.

    The port numbers shown for the ASAP servers are default port numbers. Depending on your environment, you may want to change the port numbers. Oracle recommends that you view the system file /etc/services to check which ports are currently assigned in order to avoid conflicts.

    The following UNIX command returns the ports that are currently in use, but does not indicate what ports are not currently in use, but are nonetheless assigned:

    netstat -n | grep Port_number

  15. Click Next.

    The Configure ASAP Database dialog box appears.

  16. Complete the required Oracle Database information:

    • In the Name of Oracle RDBMS Server field, enter the name of the destination Oracle RDBMS server that ASAP will use (tnsnames.ora entry name).

    • In the Oracle Server DBA User Name field, enter your Oracle system account user name.

    • In the Oracle Server DBA Password field, enter your password for the Oracle system account user name.

      Note:

      If you encounter a "Failed to resolve name" error, copy the tnsnames.ora and listener.ora files from the Oracle_home/network/admin location to the $TNS_ADMIN location and repeat the installation.

      Refer to "Re-Running the ASAP Server Installation" for important tasks that must be completed before re-running a failed installation.

      Note:

      If you are installing ASAP and Oracle WebLogic Server on different machines, ensure that the alias of the DB connect string (the Oracle Database SID) is referenced in the tnsnames.ora files on both machines.

  17. (Optional) Do the following:

    • (Optional) If you want ASAP to use Oracle users that your DBA has already created, select the Have you created Oracle Users? option. This skips the database schema creation part of the installation process.

      For information about already existing Oracle users (that is from a previous installation), see "Creating Oracle Database Users."

    • (Optional) If you are installing ASAP on an Oracle Real Application Clusters (RAC) database, do the following:

      1. Select the Is this an Oracle RAC database? option.

      2. Enter the RAC Database Connection String. Information for at least two Oracle RAC nodes must be provided and separated by a comma. The format for this connection string is:

        host1:port:servicename,host2:port:servicename

        Where host1 and host2 is the name or IP address of your Oracle RAC databases, port is the port number for the Oracle RAC databases, and servicename is the service name for the Oracle RAC databases.

  18. Click Next.

    The Configure ASAP Database Tablespaces dialog box appears. The Data and Index tablespaces are populated with the Oracle Database Server information provided.

  19. (Optional) If you had selected Have you created Oracle Users option in the previous step, enter the tablespace data and index names you recorded in "Oracle Database Information."

    The Configure ASAP Database User Password dialog box appears.

  20. Enter and confirm the password for each database schema you recorded in "Oracle Database Information."

    Note:

    If you selected to use pre-created users, you are not prompted to confirm the passwords.

  21. Click Next.

    The Configure WebLogic Server for ASAP dialog box appears.

  22. Complete the required WebLogic Server information:

    1. In the Host Name of WebLogic Server field, enter the name or IP address of the server on which the WebLogic Server has been created.

    2. In the Port Number of WebLogic Server field, enter the port number as defined during the configuration of the WebLogic Server domain.

    3. In the User Name of WebLogic Server Administrator field, enter the WebLogic Server administrator account user name.

    4. In the Password of WebLogic Server Administrator field, enter the WebLogic Server administrator account password.

    5. (Optional) If you are installing ASAP WebLogic server components using the SSL port, do the following:

      1. Select the Connect to WebLogic Server using SSL option.

      2. Enter or browse to a path to an SSL KeyStore File.

        Note:

        Your WebLogic server instance provides a demo SSL keystore file at Middleware_home/server/lib/DemoTrust.jks that can be used in a test environment.

      Note:

      If the WebLogic Server information is incorrect, or a connection to the server cannot be made, a dialog box appears with the following message:

      "Connection Fail: Invalid URL, User ID or Password."

  23. Click OK and correct the WebLogic Server information, then click Next to try again.

  24. Click Next.

    The Configure WebLogic Server Domain and Server dialog box appears.

  25. In the Oracle WebLogic Server field, select one of the following:

    • AdminServer: Select this option if you are installing ASAP to the admin server.

    • ManagedServer: Select this option if you are installing ASAP to a managed server.

    The ASAP Server Installation Summary dialog box appears.

  26. Click Next.

    The ASAP Server Installation Summary dialog box appears.

  27. When you install ASAP for the first time, a response file is automatically created in ASAP_home. However, if you want to explicitly save your settings to a file, click Save As to choose a target directory.

    The response file is a text file that contains a record of the selections for the installation you have just completed. This text file is used to perform subsequent, silent installations. For more information, see "Installing ASAP Using the Silent Installer."

  28. Click Next.

    The Installing ASAP dialog box appears. The installation executes and provides information as the installation progresses.

    After the installation completes, the Installation Summary dialog box appears.

  29. Review the summary and click Finish.

  30. Review the messages written to the console to confirm that no errors occurred during the installation. Should you need to re-install, see "Re-Running the ASAP Server Installation."

  31. Stop and restart the WebLogic Server.

  32. Go to the home directory for the user account you used to create ASAP. For example:

    cd $HOME

  33. Archive the InstallShield directory and move it to a secure location. You will need this directory if you decide to upgrade ASAP.

    Caution:

    You cannot upgrade ASAP without the InstallShield directory that the ASAP installer creates when you initially install ASAP.

Installing ASAP Using the Console Installer

When the ASAP installation wizard runs in console mode, information is sent to the console rather than to the wizard dialogs.

To install the ASAP Server using the console installer:

  1. Log in using your UNIX user account for ASAP.

  2. Ensure that the /var/tmp directory is empty. The Oracle JDBC driver uses this directory to store temporary files. If this directory is unavailable or otherwise unusable, the java virtual machine will fail, and this will cause the ASAP installation to fail.

  3. Go to the directory that contains the ASAP installation files you uncompressed (ASAP_src). See "Downloading the ASAP Installation Files."

  4. Start the console installer for the platform you are using:

    • For the IBM AIX platform:

      asap70ServerAIX61 -console

    • For the IBM AIX platform:

      asap73ServerAIX61 -console

    • For the HP Itanium platform:

      asap73ServerHP11iV3Itanium -console

    • For the Solaris platform:

      asap70ServerSolaris -console

    • For the Linux platform:

      asap70ServerLinux -console

    Note:

    If the installer does not launch, enter the following command at the UNIX prompt: export NO_J2D_DGA=true and then relaunch the installer.

    Note:

    The installer may show a "quota not found" message on the console. This message can be ignored.

    The ASAP console Welcome and pre-installation requirements text appears. Review the pre-installation requirements text and ensure that you have observed the listed recommendations.

  5. Press Enter to scroll to the bottom of the text.

  6. Type 1 and press Enter to continue.

    The Enter Server Destination Directory text appears.

  7. In the Directory Name field, enter the name of the directory where you want to install the ASAP Server.

    Note:

    The absolute path of the directory cannot exceed 48 characters.

  8. Type 1 and press Enter to continue.

    The Select Installation Type text appears.

  9. Select the type of ASAP installation you require.

    • If you type 1 for the Typical installation type, the Disk Space Required text appears. Skip the next three steps.

    • If you type 2 for the Custom installation type, the Select Components text appears. Continue with the next step.

  10. (Optional) Type 1 and press Enter to continue.

    The Select Components text appears.

  11. (Optional) Type 1 or 2 to select or expand and select the ASAP Server components you want to install. You can select the following components and configuration options:

    • ASAP

      • ASAP core components: This component provides the core ASAP software components. You must install the ASAP core components. The other components can be installed later by re-running the installer.

      • ASAP samples and demonstration models: This component provides samples and demonstration models that you can use with ASAP. You must select this component if you want to configure ASAP demonstration models. You must de-select the Configure ASAP sub-component, Configure Oracle WebLogic server for ASAP and deploy Security, JSRP, and SADT to de-select the ASAP samples and demonstration models sub-component.

      • ASAP X2X component: This components is for Solaris only, and has been deprecated. This component provide support for ASAP to NE connectivity over X.25 and X.29 protocols.

      • ASAP SNMP component: This components is for Solaris only. This component provides support for the SNMP protocol. This component provides support for ASAP to NE connectivity over SNMP.

    • Configure ASAP

      • Configure ASAP UNIX environment variables: This configuration option configured the ASAP_home/Environment_Profile with the UNIX environment variables required to run ASAP.

      • Configure ASAP database: This configuration option creates and applies the ASAP server schemas and tables to the ASAP database instance tablespaces.

      • Configure Oracle WebLogic server for ASAP and deploy Security, JSRP, and SADT: This configuration option configures the ASAP WebLogic server components. You can also select the Configure Demonstration Service Activation Model option that provides demonstration service modes.

        Note:

        ASAP supports the following demonstration models:

        • ATM/FR Service Activation Model

        • 3G Wireless Service Activation Model

        • POTS Service Activation Model

        • IP/VPN Service Activation Model

        These demonstration models are part of the ASAP samples and demonstration models ASAP sub-component. You cannot install the demonstration models without installing this ASAP sub-component.

        You can use these demonstration models to test ASAP. See "Testing the ASAP Server Installation."

  12. (Optional) Type 1 and press Enter to continue.

    Text that describes the components, and the total size of the components appears.

  13. Type 1 and press Enter to continue.

    The Configure ASAP UNIX Environment Variables text appears.

  14. Do the following:

    1. Select the mode that you want to operate in by typing 1 for Development or 2 for Production. Type 0 when you are finished.

    2. In the ASAP Environment ID field, enter an envID for ASAP.

    3. In the Directory Name field, enter the name of the base directory of your Oracle Database client installation Oracle_client_home.

  15. Type 1 and press Enter to continue.

    Note:

    If you receive an error message stating "Oracle Home is invalid – missing bin/sqlplus or lib/libclntsh. Please check with your system administrator and re-enter the value".

    The Configure ASAP UNIX Environment Variables -ASAP Server Port text appears.

  16. Each server has a default port number. Select one of the following options:

    • Press enter to accept the default port number.

    • Type a new port number for each server, and press enter.

      The port numbers shown for the ASAP servers are default port numbers. Depending on your environment, you may want to change the port numbers. Oracle recommends that you view the system file /etc/services to check which ports are currently assigned in order to avoid conflicts.

      The following UNIX command returns the ports that are currently in use, but does not indicate what ports are not currently in use, but are nonetheless assigned:

      netstat -n | grep Port_number

  17. Type 1 and press Enter to continue.

    The Configure ASAP Database text appears.

  18. In the Name of Oracle RDBMS Server field, enter the name of the destination Oracle RDBMS server that ASAP will use (tnsnames.ora entry name) and press Enter.

  19. (Optional) If you want ASAP to use Oracle users that your DBA has already created, type 1 to select the Have you created Oracle Users? option. This skips the database schema creation part of the installation process. Type 0 to skip this option.

    For information about already existing Oracle users (that is from a previous installation), see "Creating Oracle Database Users."

  20. In the Oracle Server DBA User Name field, enter your Oracle system account user name and press enter.

  21. In the Oracle Server DBA Password field, enter your password for the Oracle system account user name and press Enter.

  22. (Optional) If you are installing ASAP on an Oracle RAC database, do the following:

    1. Type 1 to select the Is this an Oracle RAC database? option, and press Enter.

    2. Press Enter.

    3. Enter the RAC Database Connection String. Information for at least two Oracle RAC nodes must be provided and separated by a comma. The format for this connection string is:

      host1:port:servicename,host2:port:servicename

      Where host1 and host2 is the name or IP address of your Oracle RAC databases, port is the port number for the Oracle RAC databases, and servicename is the service name for the Oracle RAC databases.

    4. Press Enter.

  23. Type 1 and press Enter to continue.

    Note:

    If you encounter a "Failed to resolve name" error, copy the tnsnames.ora and listener.ora files from the Oracle_home/network/admin location to the $TNS_ADMIN location and repeat the installation.

    Refer to "Re-Running the ASAP Server Installation" for important tasks that must be completed before re-running a failed installation.

    Note:

    If you are installing ASAP and Oracle WebLogic Server on different machines, ensure that the alias of the DB connect string (the Oracle Database SID) is referenced in the tnsnames.ora files on both machines.

    The Configure ASAP Database Tablespaces text appears listing all available tablespaces on your Oracle database instance.

  24. Select the number for the tablespace you want to use for each ASAP server schema data and index segments and press Enter.

    Note:

    If you had selected Have you created Oracle Users option, enter the tablespace data and index names you recorded in "Oracle Database Information."

  25. Select the number for the tablespace you want to use for TEMP_TS and press Enter.

  26. Press Enter.

  27. Type 1 and press Enter to continue.

    The Configure ASAP Database User Password text appears.

  28. Enter a password and press Enter.

  29. Enter the password again and press Enter to confirm the password for each database schema you recorded in "Oracle Database Information." If you are using pre-created user names and passwords, this options does not appear.

  30. Type 1 and press Enter to continue.

    The Configure WebLogic Server for ASAP text appears.

    Note:

    You can deploy multiple ASAP instances against the same WebLogic Server with different domains. You cannot use the same domain for different ASAP instances.

  31. In the Host Name of WebLogic Server field, enter the name or IP address of the server on which the WebLogic server domain has been created and press Enter.

  32. (Optional) If you are installing ASAP WebLogic server components using the SSL port, do the following:

    1. Type 1 to select the Use SSL option and press Enter.

    2. Press Enter to confirm.

  33. In the Port Number of WebLogic Server field, enter the port number as defined during the configuration of the WebLogic Server domain.

  34. In the User Name of WebLogic Server Administrator field, enter the WebLogic Server administrator account user name.

  35. In the Password of WebLogic Server Administrator field, enter the WebLogic Server administrator account password.

  36. (Optional) Enter a path to an SSL KeyStore File.

    Note:

    Your WebLogic server instance provides a demo SSL keystore file at Middleware_home/server/lib/DemoTrust.jks that can be used in a test environment.

  37. Type 1 and press Enter to continue.

    Note:

    If the WebLogic Server information is incorrect, or a connection to the server cannot be made, a dialog box appears with the following message:

    "Connection Fail: Invalid URL, User ID or Password."

    Click OK and correct the WebLogic Server information, then click Next to try again.

    The Configure WebLogic Server Domain and Server text appears.

  38. Select the WebLogic server you want to use by typing the number corresponding to the WebLogic server you want to use, then press Enter. The options are:

    • AdminServer: Select this option if you are installing ASAP to the admin server.

    • ManagedServer: Select this option if you are installing ASAP to a managed server.

  39. Type 1 and press Enter to continue.

    The ASAP Server Installation Summary text appears.

  40. Type 1 and press Enter to begin the installation.

    The Installation Summary text appears. Review the messages written to the console to confirm that no errors occurred during the installation. Should you need to re-install, see "Re-Running the ASAP Server Installation."

  41. Stop and restart the WebLogic Server.

  42. Go to the home directory for the user account you used to create ASAP. For example:

    cd $HOME

  43. Archive the InstallShield directory and move it to a secure location. You will need this directory if you decide to upgrade ASAP.

    Caution:

    You cannot upgrade ASAP without the InstallShield directory that the ASAP installer creates when you initially install ASAP.

Installing ASAP Using the Silent Installer

You can create a response file using the ASAP GUI installer that records all settings and selections you made using the GUI installer. You can use this file to perform subsequent, silent installations on other machines. You cannot use the console installer to create a response file. In addition to the settings contained in the response file, the silent installer also create a CSF wallet containing the passwords for each database schema and the user names and passwords for the Oracle DBA and WebLogic Server you recorded in "WebLogic Server Connection Information." For more information about the CSF wallet, see the ASAP System Administrator's Guide. The silent installer prompts you to enter these user names and passwords during the silent installation process.

You can edit the variables contained in the response file before running the silent installation, as required, but do not change the name of the response file.

To create a response file using the GUI installer (without installing ASAP):

  1. Perform the installation steps and answer the prompts.

    1. In the Select Installation Type dialog box of the ASAP Installer, select a Custom install.

    2. In the Select Components dialog box, select ASAP core components and the options available under the Configure ASAP option.

    3. In the subsequent dialog boxes, enter the information for the ASAP environment.

  2. When you reach the Summary dialog box, click Save As to save the response file. You must use the following naming convention for your response file:

    • For Solaris:

      asap73ServerSolaris.response

    • For AIX:

      asap73ServerAIX61.response

    • For HP Itanium:

      asap73ServerHP11iV3Itanium.response

    • For Linux:

      asap73ServerLinux.response

    The response file is saved to the ASAP_home directory (where ASAP_home is the location of your ASAP server installation directory).

  3. Cancel the installation to exit the GUI installer.

  4. (Optional) You can edit the response file so that each installer has the specific information that is required.

To start a silent installation:

  1. Move the response file to the ASAP_src/asap_utils directory. For example:

    mv asap73ServerSolaris.response ASAP_src/asap_utils

  2. Ensure that all the files in the ASAP_src/asap_utils directory have read write permissions.

  3. Set the path for the ORACLE_HOME environment variable to the Oracle Client. For example:

    export ORACLE_HOME=Oracle_client_home
export PATH=$ORACLE_HOME/bin:$PATH

  4. Set the path for the TNS_ADMIN environment variable to the location of your tnsnames.ora file. For example:

    export TNS_ADMIN=$HOME

  5. (Optional) Customize the silent installer asap730ServerSilent script, which is located in the ASAP_src/asap_utils/ directory.

    • Specify the name of the generated installer log file by adding the following line to the bottom of the script text file:

      ../asap73ServerOperating_System -is:log ./log_file_name.log -silent -options ./response_file.response

      The log file is saved in the ASAP_src/asap_utils directory.

    • Specify a temporary directory to be used by the silent installer by modifying the following line at the bottom of the script text file:

      ../asap73ServerOperating_System -is:tempdir ./temp_directory -is:log ./log_file_name.log -silent -options ./response_file.response

    Where Operating_System represents your platform operating system, such as Solaris,AIX, or Linux.

  6. At the command prompt, launch the silent installer:

    asap730ServerSilent

Installing ASAP Across Multiple UNIX Machines

To install ASAP across multiple UNIX machines:

Note:

This procedure uses the sample configuration file
ASAP_home/samples/sadt/SampleCommonConfig/SlaveNEP.xml as a template for creating a remote slave control server, NEP/JNEP server, and SRP server. Other server combinations are possible.

  1. Install ASAP to the UNIX machine you want to use for the master ASAP environment using the typical installation option as described in "Installing ASAP Using the GUI Installer."

  2. Install ASAP to the UNIX machine you want to use for the slave ASAP environment using the custom installation option, and selecting only the Core ASAP component.

    Note:

    You must install Oracle client on the UNIX machine hosting the slave ASAP environment. For more information, see "Downloading and Installing the Oracle Client Software."

    Note:

    If you want to create more than one slave ASAP environment, you must also install the Core ASAP components to these environments.

  3. In the master ASAP environment terminal session, test you ASAP installation as described in "Verifying the ASAP Installation."

  4. From the slave ASAP environment terminal session, create a .rhosts file in the home directory of the ASAP user account you used to install the ASAP core components. You must also do this for any additional slave ASAP environments.

    cd $HOME
touch .rhosts

  5. With a text editor, add an entry in the .rhosts file in the home directory of the login user. For example:

    + username
hostname

    Where username is the user name for the master UNIX machine and hostname is the hostname for the master UNIX machine. This allows the specified user on the master UNIX server, to run "rsh" to execute commands on the slave environment.

  6. From the master ASAP environment, test the rsh connection to the slave ASAP environment.

    rsh -l username hostname pwd

    Where username is the user name of the slave ASAP environment, and hostname is the hostname for the slave ASAP environment.

  7. From the slave ASAP environment, check for available ports that you can use for your slave ASAP servers. Use the following command to identify available ports:

    netstat -n | grep port_number

    Where port_number is the port number you want to check.

    Note:

    The
    ASAP_home/samples/sadt/SampleCommonConfig/SlaveNEP.xml requires five available ports.

  8. In the master ASAP environment, open the ASAP_home/samples/sadt/SampleCommonConfig/SlaveNEP.xml with a text editor.

  9. Change the following:

    • (mandatory) For a remote Control server, in the remoteSlaveControlServer element,

      1. Add the hostname for the slave ASAP environment to the <hostname></hostname> element.

      2. Add a port number for the slave Control server to the <interfacePort></interfacePort> element.

    • (optional) If you are adding a remote NEP server, in the nepServer element,

      1. Add the hostname for the slave ASAP environment to the <hostname></hostname> element.

      2. Add a port number for the slave NEP server to the <interfacePort></interfacePort> element.

      3. Add a JInterpreter port number for the slave NEP server to the <jinterpreterPort></jinterpreterPort> element.

    • (optional) If you are adding a remote SRP server, in the genericServer element,

      1. Add the hostname for the slave ASAP environment to the <hostname></hostname> element.

      2. Add a port number for the slave SRP server to the <interfacePort></interfacePort> element.

      3. Add a SRP Listen port number for the slave SRP server to the <SRPListenPort></SRPListenPort> element.

    Note:

    If you are not using either the SRP or NEP server configurations, delete the genericServer or nepServer elements and all child elements within them.

  10. Source the master ASAP environment ASAP_home/Environment_Profile.

    . ./Environment_Profile

  11. Start ASAP in the master ASAP environment.

    start_asap_sys -d

  12. Start the ASAP WebLogic server.

  13. Go to the ASAP_home/samples/sadt/SampleCommonConfig/ directory.

  14. Use sactConfig to upload the server SlaveNEP.xml file.

    sactConfig SlaveNEP.xml

  15. Go to ASAP_home in the master ASAP environment.

    cd $ASAP_BASE

  16. Archive the following files and folders:

    • ASAP_home/Environment_Profile

    • ASAP_home/config/ASAP.cfg

    • ASAP_home/SYBASE/interfaces

    • ASAP_home/lib/

    • ASAP_home/install/cwallet.sso

    • ASAP_home/ASAP.properties

    • ASAP_home/programs/JInterpreter

    For example:

    zip -r Masterfile.zip Environment_Profile config/ASAP.cfg SYBASE/interfaces lib/ install/cwallet.sso ASAP.properties programs/JInterpreter

  17. Copy the archive to the ASAP_home directory in your slave environment, using FTP for example.

  18. From the slave ASAP environment change the permissions for the archive.

    chmod 755 Masterfile.zip

  19. Extract the archive.

    unzip Masterfile.zip
replace config/ASAP.cfg? [y]es, [n]o, [A]ll, [N]one, [r]ename: A

  20. From ASAP_home/programs create a symbolic link for the slave NEP server using the following command:

    ln -s JInterpreter NEPSlave_jinterpreter

  21. Open ASAP_home/Environment_Profile with a text editor.

  22. Change the following variables:

    • DEV_BASE: Change the path for this variable to the ASAP_home for slave ASAP environment.

    • ASAP_BASE: Change the path for this variable to the ASAP_home for slave ASAP environment.

    • ORACLE_HOME: Change the path for this variable to the location of the Oracle client for the slave ASAP environment.

  23. From the master ASAP environment, open ASAP_home/Environment_Profile with a text editor.

  24. Add the following variables:

    export SLAVE_CONTROL_SERVERS="SlaveCtrl:Host:ASAP_home:username"
export ASAP_PROFILE="ASAP_home/Environment_Profile"

    Where:

    • SlaveCtrl is the slave control server name as defined in tbl_appl_proc table in the ASAP CONTROL database. This value is mandatory.

    • Host is the hostname or IP address of the UNIX machine where the slave control server resides. This value is optional. If no slave control server is specified, the interfaces file ASAP_home/SYBASE/interfaces is referenced to find the host for that server (assuming that the Interfaces file is being used on this platform and is located in its default directory).

    • ASAP_home is the ASAP base directory of the slave control server. This value is optional. If it is not provided, the master control server's directory will be used as the default.

    • username is the UNIX user ID for this slave control environment. This value is optional. If not provided, the master control server's login ID will be used as the default by the remote shell.

      For example:

      export SLAVE_CONTROL_SERVERS="CTRLSLV1:test.host:/home/asap/asap72:user1"
export ASAP_PROFILE="/home/asap/asap72/Environment_Profile"

  25. If the tnsnames.ora file is not located in $ORACLE_HOME/network/admin, do the following steps:

    1. From the slave ASAP environment, change the permissions for ASAP_home/scripts/start_slave_control using the following command:

      chmod 755 start_slave_control

    2. Open the ASAP_home/scripts/start_slave_control with a text editor.

    3. Remove the comment symbol "#" from the $TNS_ADMIN variable and provide a path to the tnsnames.ora file

  26. From the master ASAP environment, restart ASAP.

    start_asap_sys -d

Re-Running the ASAP Server Installation

Note:

Re-running a failed installation without performing the tasks below will result in another failed installation.

Note:

If the installer finds $HOME/InstallShield/..., an upgrade installation is run to add components onto an existing installation, instead of a new complete installation.

To re-run the ASAP Server installation:

  1. Stop the WebLogic Server:

    cd domain_home/bin
./stopWebLogic.sh -U wls_admin_user

  2. Uninstall the ASAP Server software by changing to the $ASAP_BASE/_uninst directory and running ./uninstall.sh to trigger the uninstall utility. See "Uninstalling ASAP UNIX Servers" for details.

  3. Perform any manual cleanup tasks as indicated by the uninstaller.

  4. Log in and delete the ASAP_home directory contents (where ASAP_home is the location of your ASAP server installation directory). For example:

    cd $ASAP_BASE
rm -r *

    Caution:

    Be careful which directory you run this command against. It is possible to damage your system configuration if you make an error.

  5. This will leave a directory called .jvm. This must also be removed.

    rm -rf .jvm

  6. Also remove .asap.java.pids and .ASAP.

    rm -rf .asap.java.pids
rm -rf .ASAP

  7. ASAP database schemas may have been created. Your Database Administrator can refer to ASAP_src/asap_utils/sample_drop_user.ksh for a sample script to drop the schemas that were created.

  8. Either restore the backup of the unused ASAP WebLogic Server domain domain_home or create a new domain_home. The installation process will not work on a domain that has been used in a previous installation attempt.

  9. Restart the WebLogic Server. For example:

    cd domain_home
./startWebLogic.sh

  10. Re-run the ASAP Server installation process.

If you are re-running the ASAP Server installation after a previous successful installation:

If you choose not to delete the ASAP home directory ASAP_home, delete the $HOME/InstallShield directory (if it exists) in order to trigger a full re-install instead of an upgrade install. During an upgrade install, not all installation parameters are collected. The InstallShield directory may exist under the $HOME directory, if $HOME does not match $ASAP_BASE.

Troubleshooting a Failed ASAP Installation

This section explains how to troubleshoot error messages that you may encounter during an unsuccessful ASAP installation.

Java Heap Space Exception Prevents ASAP Installation

A Java heap exception may be caused because the physical memory, CPU speed, or the quantity of CPUs is less than the minimum requirements. The JVM, which is initiated by the ASAP installer to deploy the EAR file, runs out of memory and returns the Java heap space exception in the log.

Ensure that your system meets or exceeds the minimum requirements, as outlined in "ASAP Server Hardware Requirements."

If you discovers a Java heap space exception in the installation log after a failed ASAP installation:

  1. Open the deployWbApp script file in the ASAP_home/scripts/ directory.

  2. Update the deployWbApp script by adding the following option:

    -Xmx128m

  3. Restart the installer by using the following command:

    java -Xmx128m -Xms128m weblogic.Deployer -adminurl WL_url -username WL_username -name WL_name -targets server_name -source EAR_file_path -upload -deploy