3 ASAP System Requirements

This chapter describes the hardware, operating system, software, server, and database requirements for installing Oracle Communications ASAP.

Hardware Requirements

The number and configuration of the machines that you employ for your ASAP installation depend on the scale and the kind of deployment you have planned according to your network(s).

ASAP Server Hardware Requirements

The ASAP hardware requirements described in this section are based on the ASAP implementation size classifications defined in "ASAP Server Implementation Size".

Table 3-1 provides the small, medium, and large implementation hardware requirements for ASAP installed on the Solaris platform.

Table 3-1 Hardware Requirements for Solaris

Software Components	Small SystemSPARC T4 2.85 GHz (8 threads per core)	Medium SystemSPARC T4 2.85 GHz (8 threads per core)	Large SystemSPARC T4 2.85 GHz (8 threads per core)
ASAP Server and WebLogic Server	1 core, 4 GB RAM, 4 x 73 GB (RAID5)	1 core, 8 GB RAM	2 cores, 16 GB RAM
Oracle Database	1 core, 6 GB RAM	1 core, 12 GB RAM	2 cores, 32 GB RAM
External Storage for Oracle Datafiles	N/A	14 x 73 GB (RAID 1+0)	28 x 73 GB (RAID 1+0)

Table 3-2 provides the small, medium, and large implementation hardware requirements for ASAP installed on the AIX (IBM) platform.

Table 3-2 Hardware Requirements for AIX (IBM)

Software Components	Small SystemPOWER6 5.0 GHz (2 threads per core)	Medium SystemPOWER6 5.0 GHz (2 threads per core)	Large SystemPOWER6 5.0 GHz (2 threads per core)
ASAP Server and WebLogic Server	1 core, 4 GB RAM, 4 x 73 GB (RAID5)	4 cores, 8 GB RAM	8 cores, 16 GB RAM
Oracle Database	1 core, 6 GB RAM	2 cores, 12 GB RAM	4 cores, 32 GB RAM
External Storage for Oracle Datafiles	N/A	14 x 73 GB (RAID 1+0)	28 x 73 GB (RAID 1+0)

Table 3-3 provides the small, medium, and large implementation hardware requirements for ASAP installed on an Intel Linux platform.

Table 3-3 Hardware Requirements for Intel (Linux)

Software Components	Small SystemE5-2690 2.9 GHz (2 threads per core)	Medium SystemE5-2690 2.9 GHz (2 threads per core)	Large SystemE5-2690 2.9 GHz (2 threads per core)
ASAP Server and WebLogic Server	2 cores, 4 GB RAM, 4 x 73 GB (RAID5)	3 cores, 8 GB RAM	4 cores, 16 GB RAM
Oracle Database	2 cores, 6 GB RAM	3 cores, 12 GB RAM	4 cores, 32 GB RAM
External Storage for Oracle Datafiles	N/A	14 x 73 GB (RAID 1+0)	28 x 73 GB (RAID 1+0)

Table 3-4 provides the small, medium, and large implementation hardware requirements for ASAP installed on an HP Itanium platform.

Table 3-4 Hardware Requirements for HP Itanium

Software Components	Small SystemItanium2 1.6 GHz	Medium SystemItanium2 1.6 GHz	Large SystemItanium2 1.73 GHz
ASAP Server and WebLogic Server	2 cores, 4 GB RAM, 4 x 73 GB (RAID5)	8 cores, 8 GB RAM	16 cores, 16 GB RAM
Oracle Database	2 cores, 6 GB RAM	4 cores, 12 GB RAM	8 cores, 32 GB RAM
External Storage for Oracle Datafiles	N/A	14 x 73 GB (RAID 1+0)	28 x 73 GB (RAID 1+0)

ASAP Order Control Application Hardware Requirements

The Order Control Application (OCA) client can be deployed on a Windows XP SP3 or Windows 7 platform. Ensure that the target machines for the OCA installation meet the following hardware requirements:

OCA client installer is 35 MB
Disk space requirements for the following components are 26 MB and include:
- Java Runtime Environment 1.7.0_51
- OCA Client software
- BI Publisher Report Templates
x86 Intel or AMD 32-bit architecture

Software Requirements

Ensure that you have the supported patch levels of the operating environment and additional software components (including Oracle Database Server and Oracle WebLogic Server). For information about patch levels, see "Patch Requirements".

Use the My Oracle Support Certifications tab to access the latest software platform support information. See knowledge article 1491004.1 or My Oracle Support Help for additional information:

https://support.oracle.com

Table 3-5 lists operating systems and software that support ASAP. Consult with your Oracle Database and UNIX administrators to confirm that you have the required system elements.

Table 3-5 ASAP Software Requirements

Component	Product	Version	Patches	Notes
Server Operating System	Oracle Linux (64-bit)	Linux 5 update 8 or higher (such as Linux 5.8, 5.9, or 5.10) Linux 6 update 2 or higher (such as Linux 6.2, 6.3, 6.4, or 6.5)	N/A	Oracle recommends the latest available update. Oracle products certified on Oracle Linux are also certified and supported on Red Hat Enterprise Linux due to implicit compatibility between both distributions. Oracle does not run any additional testing on Red Hat Enterprise Linux products.
Server Operating System	Oracle Solaris on SPARC architecture (32-bit and 64-bit)	10, 11	N/A	N/A
Server Operating System	IBM AIX (64-bit)	6.1	N/A	N/A
Server Operating System	Hewlett Packard HP-UX for Itanium (64-bit)	11i V3	N/A	N/A
Server Operating System	Oracle VM for use with Oracle Linux	3.0	N/A	N/A
Operating System for the Order Control Application	Windows XP on x86 Intel or AMD 32-bit architecture (For OCA only)	SP3	N/A	N/A
Operating System for the Order Control Application	Windows 7 on x86 Intel or AMD 32-bit architecture (For OCA only)	N/A	N/A	N/A
Application Server	Oracle WebLogic Server 11g Enterprise Edition (generic installer)	10.3.6	N/A	The generic version of the WebLogic Server software can be found as a separate downloadable item with the ASAP software. This version does not include a JDK. You must download and install the JDK for your platform as listed in this table before you install WebLogic Server.
Application Server	Application Server RDBMS Thin JDBC driver (ojdbc6.jar). This driver is an optional WebLogic Server component. You must install this component before you install ASAP. During the installation of the WebLogic Server software, make sure you select WebLogic JDBC Drivers.	10.3.6	N/A	N/A
Java	32- or 64-bit Oracle JDK (Java SE) for WebLogic Server. Select the JDK for your platform.	For Linux or Solaris: 1.7.0 with the latest Critical Patch Update AIX: IBM Java 1.7 (This IBM JDK corresponds to Java SE version 1.7.x) HP-UX: 1.7.0	N/A	The generic WebLogic Server available with the ASAP software from the Oracle software delivery Web site can run in 32-bit or 64-bit mode, depending on the JDK (Java SE) version you use.
Database Server	Oracle Database 11g R2 Enterprise Edition for the following platforms: Oracle Solaris HP-UX Oracle Linux IBM AIX	11.2.0.4	Available in patch 13390677	For information about downloading these databases see "Downloading and Installing the Oracle Database Software".
Database Client	Oracle Client for the following platforms: Oracle Solaris HP-UX Oracle Linux IBM AIX	11.2.0.4	Available in patch 13390677	For information about downloading this client see "Downloading and Installing the Oracle Client Software".
Reporting Solution for the OCA Client	Business Intelligence (BI) Publisher for use with the OCA Client (Thick or Thin)	11G	N/A	N/A
IDE	Oracle Communications Design Studio for ASAP Cartridge Development	7.2.4	N/A	N/A
IDE	Fort C++ (C/C++ Compiler) for creating custom SRP	Sun Studio 12 Update 1	N/A	N/A
OCA Java Applet Thin Client Browser Support	Microsoft Internet Explorer 1024 x 768 resolution monitor with 256 colors recommended (640 x 480 is minimum resolution required)	7, 8	N/A	N/A
OCA Java Applet Thin Client Browser Support	Mozilla Firefox	3.5 or higher	N/A	N/A
JDK (Java SE) for OCA thin client	32-bit JDK (Java SE) for Windows XP SP3 or Windows 7 OCA thick client deployment	1.7.x	N/A	Download this JDK for the OCA Thick client only. The OCA java applet Thin client automatically installs the appropriate JDK when you run the client using Internet Explorer or Firefox.

Information Requirements

During ASAP installation, you are required to enter configuration values, such as host names and port numbers. This section describes the information that you will be required to provide during the installation process. You define some of these configuration values when you install and configure the Oracle database, client, and WebLogic Server.

Note:

It is advisable that you print the table(s) and enter your values for future reference.

You will be required to enter these values during the installation process.

Oracle Database Information

Table 3-6 lists the Oracle Database information that you are required to provide during the ASAP installation process.

Table 3-6 Database Information Required in the ASAP Installation Process

Installer Field	Description	Value
Directory Name:	The base directory of the Oracle Database Client software. For example: /u01/app/oracle/db/11.2.0.4/client_1 The ASAP Installer requires that you enter this value.
Name of RDBMS Server	The tnsnames.ora entry name of the database instance on which the ASAP schemas will be installed (for example ASAPDB). The ASAP Installer requires that you enter this value.
Oracle Server DBA User Name	User name of the Oracle DBA for the predefined SYS user account. The ASAP Installer requires that you enter this value.
Oracle Server DBA Password	Password of the Oracle DBA for the predefined SYS user account. The ASAP Installer requires that you enter this value.
System Admin User Name	User name of the predefined Oracle database SYSTEM user account. You need this account to run ora_system_procs.sh script after you install ASAP for the first time.
System Admin Password	Password for the predefined Oracle database SYSTEM user account. You need this password to run ora_system_procs.sh script after you install ASAP for the first time.

Table 3-7 lists schema details that you are required to provide during installation.

Table 3-7 Schema user Information

Installer Field	Description	Value
Data Segment Index Segment	You must create one or more tablespaces and associated data files for the ASAP schemas (SARM, CTRL, ADM, SRP, and NEP) before you install ASAP. The ASAP installer requires you to select tablespaces in which to create data and index segments for each ASAP schema. For example ASAP_DATA ASAP_INDEX The sample values provided here show one tablespace for all data and one for all index segments, however this is not mandatory. For example, you can create one tablespace for all the segments or individual tables spaces for every data and index segments for every server (see "Database and Client Planning").
TMP_TS	You must select a temporary tablespace, for example, TEMP. The ASAP Installer requires that you enter this value.
Server Port Numbers	The ASAP Installer automatically generates ports for ASAP servers and checks that these ports do not conflict with other ASAP environments. However, you can also select your own values during the installation process. You can select port for the following servers (where envid represents you ASAP environment ID): SARMenvid CTRLenvid SRP_envid NEP_envid ADM_envid OCA_envid JSRPenvid - Sending WO JSRPenvid - Receiving WO event NEPenvid NEPenvid - jListener	Provide a server port number.

Installer Field

Description

Value

Data Segment

Index Segment

You must create one or more tablespaces and associated data files for the ASAP schemas (SARM, CTRL, ADM, SRP, and NEP) before you install ASAP. The ASAP installer requires you to select tablespaces in which to create data and index segments for each ASAP schema. For example

ASAP_DATA
ASAP_INDEX

The sample values provided here show one tablespace for all data and one for all index segments, however this is not mandatory. For example, you can create one tablespace for all the segments or individual tables spaces for every data and index segments for every server (see "Database and Client Planning").

TMP_TS

You must select a temporary tablespace, for example, TEMP.

The ASAP Installer requires that you enter this value.

Server Port Numbers

The ASAP Installer automatically generates ports for ASAP servers and checks that these ports do not conflict with other ASAP environments. However, you can also select your own values during the installation process.

You can select port for the following servers (where envid represents you ASAP environment ID):

SARMenvid
CTRLenvid
SRP_envid
NEP_envid
ADM_envid
OCA_envid
JSRPenvid - Sending WO
JSRPenvid - Receiving WO event
NEPenvid
NEPenvid - jListener

Provide a server port number.

For more information about creating tablespaces, see "About Creating and Configuring the Oracle Database".

WebLogic Connection Information

Table 3-8 lists WebLogic Server connection details that you are required to provide during installation.

Table 3-8 WebLogic Server Connection Information

Information Type	Description	Value
Host Name of Oracle WebLogic Server	You provide the host name for the WebLogic Server instance to define it uniquely for the specific purpose of installing, and working with, ASAP (for example, localhost). The ASAP Installer requires that you enter this value.
Port Number of Oracle WebLogic Server	This is the port number assigned to this specific the WebLogic Server (for example 7001). The ASAP Installer requires that you enter this value.
User Name of Oracle WebLogic Server Administrator	Your WebLogic Server user name. You define this name when create an Oracle WebLogic Server domain. The ASAP Installer requires that you enter this value.
Password of Oracle WebLogic Server Administrator	You define this password along with the user name when you create an Oracle WebLogic Server domain. The ASAP Installer requires that you enter this value.

Patch Requirements

This section documents required software patches for ASAP 7.2.

There are currently Oracle Client, or Oracle Database patches required to install ASAP; however, new patches and security updates should be applied as they become available (see "About Critical Patch Updates" for more information).

Oracle WebLogic Server 10.3.6 Patches

You must download PSU Patch 13529623. Go to the Oracle support Web site to download the patches:

https://support.oracle.com

Use the WebLogic Server Oracle Smart Update tool to apply the downloaded patch. For more information, see the discussion on applying and managing patches in the Oracle Smart Update documentation on Oracle Technology Network:

http://download.oracle.com/docs/cd/E14759_01/index.htm

About Critical Patch Updates

Oracle provides a Critical Patch Update Advisory Web page that is updated on a quarterly basis. ASAP supports all Critical Patch Updates. Install all applicable Critical Patch Updates as soon as possible.

To check for Critical Patch Updates, find out about security alerts, and enable email notifications about Critical Patch Updates, see the Security topic on Oracle Technology Network at:

http://www.oracle.com/technetwork/topics/security/whatsnew/index.html