Skip Headers
Oracle® Communications Order and Service Management Installation Guide
Release 7.2.2

E35412-05
Go to Documentation Home
Home
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

2 OSM System Requirements

This chapter describes the Oracle Communications Order and Service Management (OSM) system requirements. It also describes information you need during the installation procedure.

Software Requirements

Table 2-1 describes the software required to support the OSM components.

Note:

For all operating systems, check the Oracle Database documentation for any additional operating system patches required to support the database.

Table 2-1 OSM Required Software

Component Product Version Patches Notes

Server Operating System

Oracle Linux (64-bit)

5.3

N/A

Also supported on minor releases higher than 5.3.

Server Operating System

Red Hat Enterprise Linux (64-bit)

5.3

N/A

Also supported on minor releases higher than 5.3.

Server Operating System

Oracle Solaris

10 and 11

N/A

Supported on Sparc platforms only.

Server Operating System

IBM AIX

6.1

N/A

N/A

Server Operating System

Windows XP Professional

SP3

N/A

For development, demonstration and test environments. Not for production use.

Server Operating System

Windows 7 (64-bit)

SP1

N/A

For development, demonstration and test environments. Not for production use

Client Operating System

Windows XP Professional

SP3

N/A

For Windows-only components.

Client Operating System

Windows 7 (64-bit)

SP1

N/A

For Windows-only components.

OSM Web client Browser

Internet Explorer

7.0, 8.0

N/A

Windows 7 SP1 (64-bit) client OS requires version 8.0.

Database Server

Oracle Database

11gRelease 2 (11.2.0.3)

See Notes for required patches.

For non-Windows platforms: patches for the following bugs are required:

13566938 ORA-600 [KCBGTCR_1] ON UPDATE

12627504 ORA-600 [QKKCOMBINE:1]

12535346 ORA-07445: DB PROCESS EXITS WITH CRASH (SEGV) DURING PROCESSING OF INSERT SQL

13572659 DBMS_REDEFINITION DISABLES FKS USED FOR REFERENCE PARTITIONING

13505390 ORA-00600 [KKEDSGETTABBLKCNT: NULL SEGMENT] REPORTED ON QUERY

13060271: ORA 600 [QESMAINITMETADATACTX-THISCTXP1]

13737888: ONLINE DDL:ORA-600[KGHSTACK_UNDERFLOW_INTERNAL_3], [0X2B7F4E1E7678], [KEYBUF]

16850097: ORA-54 WHEN TRY TO ADD CONSTRAINT DISABLE NOVALIDATE

For Windows platforms: Patch 4 is required (Patch Name 13783452 for 32-bit Windows or Patch Name 13783453 for 64-bit Windows)

See "Downloading and Installing Oracle Database Patches".

If you use database partitioning for your OSM server, you must install the Enterprise Edition version of the Oracle database software and enable the partitioning option.

ODAC Database Client

Oracle Data Access Components (ODAC) (32-bit)

11.2.0.3

N/A

The OSM Administrator application requires the ODAC with Oracle Developer Tools for Visual Studio to be on the same machine as the OSM Administrator. This tool contains an Oracle Database client that supports libraries required for the OSM Administrator to connect directly to an OSM Oracle Database server.

Java: 32- or 64-bit JDK (Java SE) for the application server

For Linux

1.6.0_37 or greater

N/A

Do not use any Java version that might be included with the Application Server.

Java: 32- or 64-bit JDK (Java SE) for the application server

For Solaris

1.6.0_37 or greater

N/A

Do not use any Java version that might be included with the Application Server.

Java: 32- or 64-bit JDK (Java SE) for the application server

For AIX

6 SR10 or greater

N/A

6 SR10 corresponds to the 1.6.0_29 Oracle Java fix. Do not use any Java version that might be included with the Application Server.

Java: 32- or 64-bit JDK (Java SE) for the application server

For Windows XP, Windows 7

1.6.0_37 or greater

N/A

Do not use any Java version that might be included with the Application Server.

Application Server

Oracle WebLogic Server (32-bit or 64-bit)

or

Oracle WebLogic Server Upgrade Installer

11gR1 (10.3.6) Generic and Coherence 3.7

10.3.6.0

If unicast messaging mode is used, apply:

12822180

13639449

8737648

OSM provides the following application server options:

  • You can download the generic version of Oracle WebLogic Server included in the OSM software media pack which includes Coherence. This version of Oracle WebLogic Server also requires that the required Java version is installed first.

  • The Oracle WebLogic Server upgrade installer upgrades OSM 7.2 WebLogic 10.3.5 domains and Coherence 3.6 to WebLogic 10.3.6 domains and Coherence 3.7. See "Upgrading the OSM 7.2 WebLogic Domain to WebLogic 10.3.6 and ADF 11.1.1.6" for more information.

Application Server

Application Server Oracle JDBC driver (ojdbc6.jar).

11.2.0.2.0 or later

N/A

OSM uses the Oracle JDBC driver that comes with WebLogic Server. If you perform a Custom installation of your WebLogic Server software, make sure you select the WebLogic JDBC Drivers component.

Application Server

Oracle Application Development Framework (ADF) Application Development Runtime

11g

Patch set 5 (11.1.1.6.0)

ADF is included as a separately installed component in the OSM software media pack.

Third-Party Components

JBoss Cache

1.4.1 SP12

N/A

Download from:

http://sourceforge.net/projects/jboss/files/JBossCache/JBossCache%201.4.1.SP12/

Third-Party Components

Saxon

B 9.1.0.7j

N/A

Download from:

http://sourceforge.net/projects/saxon/files/Saxon-B/9.1.0.7

Third-Party Components

GraphViz

2.8

N/A

Optional, to support the modeldoc tool.

Download from:

http://www.graphviz.org/pub/graphviz/stable/windows/graphviz-2.8.exe

Build Tool

Ant

1.8.1

N/A

Ant is required to use various tools in the OSM SDK including OSM's cartridge management tools.

To ensure tools function correctly, all copies of Ant in use must have the same version number.


About Critical Patch Updates

OSM is supported on all Oracle Critical Patch Updates. You should install all Critical Patch Updates as soon as possible. To download Critical Patch updates, find out about security alerts, and enable email notifications about Critical Patch Updates, see the ”Security” topic on Oracle Technology Network.

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

Oracle Application Integration Architecture for Communications Alignment

See OSM Cartridge Guide for Oracle Application Integration Architecture for information on compatibility between OSM software, OSM Order-to-Activate cartridges, and Oracle's Application Integration Architecture (AIA) for Communications. The OSM Order-to-Activate cartridges are used with the Oracle Communications Order to Cash Integration Pack for Oracle Communications Order and Service Management.

For more information about the Order to Cash business process see Oracle Communications Order to Cash Integration Pack Implementation Guide for Siebel CRM, Oracle Communications Order and Service Management, and Oracle Communications Billing and Revenue Management in the Oracle Application Integration Architecture documentation.

Design Studio Installation and Version Compatibility

For Oracle Communications Design Studio plug-in installation information, see Design Studio Installation Guide.

See Design Studio Compatibility Matrix (included in the Design Studio media pack) for Design Studio for Order and Service Management compatibility information. The Design Studio Compatibility Matrix also provides information about OSM to Oracle Communications ASAP integration using the Design Studio Activation Task. The same information is also relevant to OSM to Oracle Communications IP Service Activator integration using the Design Studio Activation Task.

Oracle VM Support

OSM is supported on Oracle VM Release 3.0 with Oracle Linux.

Hardware Requirements

The following sections describe hardware sizing guidelines for OSM.

Hardware Sizing Guidelines

Table 2-2 and Table 2-3 provide guidelines for estimating the hardware required to achieve the indicated daily order provisioning volumes with OSM.

In the tables, values are approximate. One order is considered to contain 25 automated tasks. A day is considered to be 8 hours.

Table 2-2 Hardware Sizing Guidelines for use with Oracle Solaris 10 and Solaris 11

Deployment Size Small Medium Large

Orders/day

<= 100,000

100,000 <= 500,000

500,000 <= 1 000,000

Sun server model

SPARC T4-1

SPARC T4-1

SPARC T4-2

CPUs

1 core zone of SPARC T4 2.85 GHz (8-Core)

1 SPARC T4 2.85 GHz (8-Core)

2 SPARC T4 2.85 GHz (8-Core)

RAM (GB)

16

64

128

Internal disk space (GB)

4x600 SAS-2 HDD (RAID10)

2x300 (RAID1)

2x300 (RAID1)


Table 2-3 Hardware Sizing Guidelines for use with Oracle Linux 5.x

Deployment Size Small Medium Large

Orders/day

<= 100,000

100,000 <= 500,000

500,000 <= 1 000,000

Linux server model

Sun Server X3-2

Sun Server X3-2

Sun Server X2-4

CPUs

1 Intel Xeon E5-2609 2.4GHz (4-Core)

2 Intel Xeon E5-2640 2.5GHz (6-Core)

2 Intel Xeon E7-4870 series 2.40GHz (10-Core)

RAM (GB)

16

64

128

Internal disk space (GB)

4x600 SAS-2 HDD (RAID10)

2x300 (RAID1)

2x300 (RAID1)


Table 2-4 gives sample database sizes and sample external storage hardware scenarios:

Table 2-4 Oracle Database External Storage Requirements

Deployment Size Small Medium Large

Total disk space for database storage (GB)

no external storage needed

3600 (RAID 1+0)

7200 (RAID 1+0)

Number of disks

N/A

28

20

Disk capacity (GB)

N/A

300 GB SAS-2 (15000 rpm)

600 GB SAS-2 (15000 rpm)

Write Cache SSD

N/A

2 73 GB SAS-2

4 73 GB SAS-2

Sun storage system

N/A

Sun ZFS Storage 7120 Appliance

Sun ZFS Storage 7420 Appliance


Performance Recommendations

Oracle recommends connecting the OSM and database servers with a minimal number of network devices in between. The switch connecting the network devices should be 10 GB capacity. This hardware configuration should produce an optimal network latency between 0.2 and 0.4 msec. Network latency above 1 msec can cause performance degradation.

Hardware Requirements for Development Systems

A demonstration or small development installation can be installed on a system meeting the following minimum requirements:

  • 2 GB RAM

  • one dual-core processor

  • 10 GB of disk space

The numbers provided are guidelines only. Actual disk and memory usage will vary based on the number of users, amount of data, and transaction volume.

For a small, low-volume installation, it is possible to co-locate components such as the Oracle Database and WebLogic Server on the same computer. In this case, the minimum RAM required is 4 GB. (In a high volume production environment, all OSM components must be located on separate computers to provide acceptable performance results.)

Installer Disk Space

Approximately 600MB of disk space is required for temporary use for the OSM installer to run.

Required Information for Installing OSM

You must supply configuration-related information when you install OSM. Some of this information is determined during the installation. However, some information should already have been determined before the OSM installation is begun. Gather this information in advance.

Note:

You can obtain most of the required configuration information from your Oracle database administrator (DBA) and your system administrator.

Oracle Database Information

This information in Table 2-5 is needed to connect to an Oracle database instance.

Table 2-5 Oracle Database Parameters

Parameter Description

Database Instance Host

The IP address or DNS name of the database instance on which the OSM schema will be installed. If you plan to use an Oracle RAC database, you need the Single Client Access Name (SCAN) for this field.

Database Instance Port

The port on which the database instance to which the OSM schema will be installed is listening.

Database Instance SID

The SID of the database instance on which the OSM schema will be installed.

Database Service Name

The name of the service used for OSM client connections.


If the OSM database users have been created prior to the OSM installation, you need to gather the following information in Table 2-6 before installing OSM. If they have not been created beforehand, you can determine the following information during the installation.

Table 2-6 Oracle Credential Information

Parameter Description

Primary Schema Username

Database primary schema username.

Primary Schema Password

Database primary schema username password.

Rule Engine Schema Username

Database rule engine schema username.

Rule Engine Schema Password

Database rule engine schema username password.


Table 2-7 shows the parameters used to establish an administrative connection to the database, so that the tablespaces and schema can be created.

Table 2-7 Oracle Database Admin Credential Information

Parameter Description

Database Admin Username

Username of the Oracle DBA.

Database Admin Password

Password of the Oracle DBA.


Table 2-8 shows the parameters used to indicate the tablespaces being used for the installation.

Table 2-8 Oracle Tablespace Information

Parameter Description

Default Tablespace

Tablespace to use if your data will all be on the same permanent tablespace.

Temporary Tablespace

If your database instance has only one temporary tablespace, the installer will find its name automatically. If there is more than one temporary tablespace in the database instance, you need to know which one OSM is supposed to use.

Model Data Tablespace

Name of the tablespace to use for model data, if different from the default tablespace.

Model Index Tablespace

Name of the tablespace to use for the indexes for the model data, if different from the default tablespace.

Order Data Tablespace

Name of the tablespace to use for order data, if different from the default tablespace.

Order Index Tablespace

Name of the tablespace to use for the indexes for the order data, if different from the default tablespace.


WebLogic Parameters

Table 2-9 shows the parameters related to WebLogic Server. This information is needed to connect to a WebLogic Server.

Table 2-9 WebLogic Parameters

Parameter Description

WebLogic Host Name

The name or IP address of the computer where WebLogic is installed.

WebLogic Port Number

The port number for WebLogic server.

WebLogic System User

The user name of the WebLogic system administrator.

WebLogic System Password

The password of the WebLogic system administrator.


OSM Server Parameters

Table 2-10 shows the parameters related to the OSM server installation. The following information is used to specify the SMTP mail server and the administrative e-mail addresses to deliver notifications via e-mail.

Table 2-10 Email Notification

Parameter Description

Notification Email server

DNS name or IP address of your e-mail server.

Notification Email server Port

Port that the e-mail server is listening.

Administrator Email Address

OSM Administrator's e-mail address.