This chapter describes how to install Oracle Communications Billing and Revenue Management Elastic Charging Engine (ECE). Before you install ECE, read these chapters:
You can install ECE by using the GUI installation or the silent installation. The silent installation procedure enables you to perform a noninteractive installation of ECE. You can use the silent installation to install ECE quickly on multiple systems.
The silent installer uses a response file in which you specify installation settings. To obtain the response file, you first run the GUI installation, which generates the response file. See "ECE Installation Options" and "Elastic Charging Engine Installer Screens" for more information.
For installation instructions, see the following sections:
The steps for installing ECE by using the GUI installation depend on the ECE software components you choose to install:
To install an ECE standalone system, select the Standalone installation option.
This option installs a self-contained, nonproduction version of ECE that is not integrated with Oracle Communications Billing and Revenue Management (BRM) or Pricing Design Center (PDC). Use the stand-alone system for evaluation, demonstration, and functional testing.
See "Installing a Standalone ECE System" for more information.
To install an ECE integrated system, do one of the following:
Select the Complete option to install all ECE software components, including all BRM and PDC integration packs.
Select the Custom option to choose one or more components to install each time you run the installer.
See "Installing All ECE Components" and "Installing Individual ECE Components" for more information.
To upgrade an existing ECE 11.3 installation, select the Patchset option.
For more information, see "Upgrading Existing ECE 11.3 Installation".
To install all ECE components, select the Complete installation option, which installs ECE Server, ECE Diameter Gateway, and all ECE integration packs. Use this option for an ECE integrated installation.
During the installation, you will need the required information that you previously collected. See "Information Requirements."
To install all ECE components:
Create a temporary directory (temp_dir).
Go to the My Oracle Support Web site:
Sign in with your user name and password.
Click the Patches & Updates tab.
From the list, select Patch Name or Number.
In the text field, enter 28738541 and click Search.
The Patch Search Results page appears.
Click the patch name.
The patch details appear.
From the Platform list, select the platform and click Download.
The File Download dialog box appears.
Download the p28738541_113090_platform.zip software pack to temp_dir, where platform is linux or solaris.
Unzip p28738541_113090_platform.zip and extract the contents to temp_dir:
The extracted software pack has the following structure:
ocece/Disk1/install
ocece/Disk1/stage
Go to the ocece/Disk1/install/ directory, and run one of the following commands:
To start the GUI installer:
./runInstaller
To start the GUI installer and create a silent installer response file during the installation:
./runInstaller -record -destinationFile path
where path is the response file location and name.
The Welcome screen appears.
Click Next.
The Specify Inventory Directory and Credentials screen appears.
Note:
The installer creates an Inventory directory if it does not detect any installed Oracle products on the system. The Inventory directory manages all Oracle products installed on your system.In this screen, enter the following if you do not want to accept the defaults:
Full path of the inventory directory
Name of the operating system group that has write permission to the inventory directory
Click Next.
The Select Installation Type screen appears.
Select Complete, and click Next.
The Specify Home Details screen appears.
Enter the following information:
In the Name field, enter a name for the installation, or select a name from the list.
In the Path field, enter the full path or browse to the directory in which to install ECE.
Click Next.
The Select ECE Security Options screen appears.
Select one of the ECE security options described in the following table.
For more information, see BRM Elastic Charging Engine Security Guide.
| Option | Description |
|---|---|
| Security disabled | Enables no security configurations.
(Single server installation only) |
| Security enabled without SSL | Enables the following security configurations:
|
| Security enabled with SSL | Enables the following security configurations:
|
Click Next.
The Config Data Details screen appears.
In the Directory field, enter the path or browse to the directory where ECE gets the XML files that contain configuration data (mediation specifications).
After installation, when you load data into ECE, the loading utility reads and loads configuration data from this directory.
For more information about configuration data, see the discussion about implementing ECE with BRM in BRM Elastic Charging Engine Implementation Guide.
Click Next.
The Persistence Data Details screen appears.
In the Directory field, enter the path or browse to the directory into which the ECE BrmCdrPluginDirect Plug-in will write call detail record (CDR) files of rated events.
This is the directory where the plug-in stores completed CDR files that are ready to be processed by BRM.
Click Next.
The ECE Cluster Details screen appears.
Enter information about the ECE cluster:
Note:
(Linux) If you used the ece_provision script to provision your environment for an ECE installation, the user name for host machines you enter in the ECE Cluster Details screen must be the same user name you entered for the ECE_USER field in the ece_provision_config.sh file.In the User Name for Host Machines field, enter the user name you specified when you created the ECE user account prior to installation. All machines in the cluster must have the same user name.
This user name is used by the Elastic Charging Controller to identify the remote machines on which to deploy ECE.
In the Java Heap Settings field, specify the memory to allocate to each node in the ECE cluster.
The memory applies to each node for the driver machine and all server machines.
In the Cluster Name field, enter the cluster name used by applications to identify ECE in the cluster. For example, Oracle Enterprise Manager Cloud Control uses the cluster name to locate ECE nodes for monitoring.
The cluster name must contain fewer than 32 characters.
Click Next.
The Coherence Grid Security screen appears.
Note:
(Linux) If you used the ece_provision script to provision your environment for an ECE installation, authorized host list information you enter in the Coherence Grid Security screen must be the same host information you entered for the HOST field in the ece_provision_config.sh file.Specify the machines allowed to be part of the Coherence cluster and the credentials required for accessing the cluster.
To specify the machines, do one or both of the following:
In the Host Details in comma separated format field, list the host names or IP addresses of all machines on which ECE nodes will reside. Separate each value with a comma.
Include your computer name in this field. Do not enter localhost or a loopback address.
Include all server machines across which the Coherence grid is deployed and any other machine that is to be part of the grid.
Specify a range of allowed addresses for hosts in the same subnet as follows:
In the Host Details Range from IP Address field, enter the valid IP address that starts the range.
In the Host Details Range to IP Address field, enter the valid IP address that ends the range.
To specify the credentials required to access the cluster:
In the Alias Name for Coherence grid security field, enter the account alias that defines the administrator for securing the Coherence cluster.
In the Password for the alias field, enter the password used to access the cluster security key in the Coherence keystore (the ECE_home/oceceserver/config/server.jks file).
This is the password for Coherence cluster security.
You use this password when enabling SSL.
See the discussion about Coherence cluster security in BRM Elastic Charging Engine Security Guide.
Click Next.
The Oracle NoSQL Database Details screen appears.
Specify the NoSQL database connection information:
In the Host Name field, enter the host name or IP address of the machine on which the Oracle NoSQL database is installed.
In the Port Number field, enter the port number assigned to the NoSQL database service.
In the NoSQL Datastore Name (database name) field, enter the name of the NoSQL data store into which ECE will publish rated events.
This is where Rated Event Publisher writes rated events generated by the ECE server.
Click Next.
The KeyStore Credentials screen appears.
Specify the keystore credential information required for the ECE installation.
For information about keystore credentials, see BRM Elastic Charging Engine Security Guide and the discussion about setting up and managing ECE security in BRM Elastic Charging Engine System Administrator's Guide.
In the Key Password for Boundary System Alias field, enter the password ECE uses to access the boundary system alias key in the keystore JKS file (ECE_home/oceceserver/config/keystore.jks).
In the Certificate store password field, enter the password used to access the server JKS file and the keystore JKS file:
ECE_home/oceceserver/config/keystore.jks
Stores symmetric keys for boundary system password encryption.
ECE_home/oceceserver/config/server.jks
Stores credentials for cluster node authentication details. This file is also used for encrypting intra-cluster communication over SSL.
These files share the same key and store password.
In the DName (Distinguished Name) field, specify the credentials that define what users are authorized to do regarding cluster security.
Examples:
CN=Administrator,OU=Rating,O=CompanyB
Or:
CN=Developer,OU=ECE
where:
CN is the common name for the user.
OU is the organizational unit of the user.
O is the organization of the user.
The combined DName values are similar to a group in UNIX.
Tip:
The value set here (in creating the certificate) is used for authentication in the cluster and must be the same as the value used in the ECE_home/oceceserver/config/permissions.xml file, which is created after installation and used for authorization in the cluster.You use the DName value when enabling SSL.
The DName value is used as a command line parameter for creating the server.jks keystore and the keystore.jks keystore.
Click Next.
The ECE Notification Queue Details screen appears.
Enter the Java Message Service (JMS) credentials for the JMS server on which the ECE notification queue (JMS topic) is to reside.
ECE publishes notification events into this JMS queue (JMS topic), which external systems can use to obtain data for their own processing.
After you install ECE, you run a post-installation script that creates the JMS queue (JMS topic) on the server.
In the Host Name field, enter the host name of the server. on which the JMS queue (JMS topic) resides.
In the Port Number field, enter the port number of the server.on which the JMS queue (JMS topic) resides.
In the User Name field, enter the user name for logging in to the server. on which the JMS queue (JMS topic) resides.
In the Password field, enter the password for logging in to the server. on which the JMS queue (JMS topic) resides.
In the Connection Factory Name field, enter the connection factory name used to create connections to the JMS queue (JMS topic) queue.
After installing ECE, you run an ECE post-installation script that creates the JMS queue (JMS topic) on the server. The connection factory name entered here is used by the script to create connections to the JMS queue (JMS topic).
In the Topic Name field, enter the name of the JMS queue (JMS topic) on the server, to which ECE publishes notification events.
After installing ECE, you run a post-installation script that creates the JMS queue (JMS topic) on the server. The topic name entered here is the name the ECE post-installation script uses to create the JMS queue (JMS topic).
In the Suspense Queue Name field, enter the name for the suspense queue, to which ECE pushes the failed notifications.
Click Next.
The ECE Notification Queue SSL Details screen appears.
Enter secure socket layer (SSL) information required to connect to the Java Message Service (JMS) queue to which ECE publishes notification events:
If you will not use SSL to encrypt communication between ECE and the JMS queue, select the Disable SSL option.
If you select this option, do not enter values in the following fields.
In the Keystore password field, enter the password used to access the SSL keystore file.
In the Keystore location field, enter the full path to the SSL keystore file.
Click Next.
The BRM Gateway Details screen appears.
Enter the BRM Gateway connection details:
In the Host Name field, enter the IP address or the host name of the computer on which BRM is configured.
In the CM Port field, enter the port number assigned to the CM.
In the User Name field, enter the BRM user name.
In the Password field, enter the password for logging in to BRM.
If you will not use SSL to encrypt communication between ECE and BRM through BRM Gateway, select the Disable SSL option.
If you select this option, do not change the value in the following field.
If SSL is enabled for BRM Gateway but the Oracle wallet file containing the SSL trusted certificates for BRM Gateway is not in the default location (/opt/wallet/client/cwallet.sso), replace the default path in the Wallet File Absolute Path field with the full path to the actual location.
Click Next.
The External Manager (EM) Gateway Details screen appears.
Specify the EM Gateway information:
In the Number EM Gateways field, enter the number of EM Gateway instances you want ECE to run automatically when you start EM Gateway.
In the Starting Port Number field, enter the port number assigned to EM Gateway.
If you have more than one EM Gateway instance, this is the starting port number. Subsequent port numbers increase by one for each additional EM Gateway instance. For example, if the starting port number is 15502 and you specify three EM Gateway instances, ports 15502, 15503, and 15504 are used by EM Gateway processes.
Ensure that no other processes on the machine use port numbers assigned to EM Gateway instances.
If you will not use SSL to encrypt communication between BRM and ECE through EM Gateway, select the Disable SSL option.
If you select this option, do not enter or change values in the following fields.
If you do not want authentication to be performed to check whether EM Gateway is allowed to communicate with ECE, select the Client Authentication Disabled option.
If you select this option, do not change the value in the following fields.
If SSL is enabled for EM Gateway but the Oracle wallet file containing the SSL trusted certificates for EM Gateway is not in the default location (/opt/wallet/server/cwallet.sso), replace the default path in the Client wallet field with the full path to the actual location.
Click Next.
The PDC Pricing Components Queue Details screen appears.
Enter the system connection information of the server on which the JMS queue for PDC pricing component data resides.
PDC publishes pricing component data into this queue. ECE will listen on this JMS queue to consume the pricing component data.
In the Host Name field, enter the IP address or the host name of the computer on which the PDC JMS queue to which PDC publishes the pricing data resides.
In the Port Number field, enter the port number of the computer on which the PDC JMS queue resides.
In the User Name field, enter the user name for logging in to the server on which the PDC JMS queue resides.
In the Password field, enter the password for logging in to the server on which the PDC JMS queue resides.
If you will not use SSL to encrypt communication between BRM and PDC, select the Disable SSL option.
If you select this option, do not enter values in the following fields.
In the PDC Keystore Password field, enter the password used to access the SSL keystore file.
In the Keystore Path field, enter the full path to the SSL keystore file.
Click Next.
The BRM Database Connection Details screen appears.
Specify the BRM database connection information:
In the JDBC URL field, enter the following colon-separated values:
Driver:@HostName:Port:ServiceName
where:
Driver is the driver used to connect to the BRM database.
HostName is the IP address or the host name of the computer on which the BRM database is configured.
Port is the port number assigned to the BRM database service.
ServiceName is name of the BRM database service.
For example:
jdbc:oracle:thin:@localhost:1521:PINDB
In the User Name field, enter the BRM database schema user name.
In the Password field, enter the password for the BRM database user.
In the Queue Name field, enter the name of the Oracle Advanced Queuing (AQ) database queue that the Account Synchronization DM uses to publish business events for ECE to consume.
ECE listens on this queue for loading update requests from BRM.
In the Suspense Queue Name field, enter the name of the Oracle AQ database queue to which ECE moves events for failed update requests for later reprocessing.
After installing ECE, you can use an ECE post-installation script to create this queue. When prompted by the script, enter the queue name you entered here.
In the Acknowledgement Queue Name field, enter the name of the Oracle AQ database queue to which ECE publishes acknowledgments for BRM.
For example, ECE uses this queue to send acknowledgment events to BRM during the rerating process, indicating that the process can start or finish.
After installing ECE, you can use an ECE post-installation script to create this queue. When prompted by the script, enter the queue name you entered here.
Click Next.
The Diameter Gateway Details screen appears.
Enter information that Diameter clients use to identify your Diameter Gateway server:
If you do not want Diameter Gateway to start when ECE starts, select the Skip option.
If you select this option, do not enter values in the following fields.
In the Origin Host field, enter the value for the Origin-Host attribute-value pair (AVP) to be sent in the Diameter request.
This is a unique identifier that you assign your Diameter Gateway server on its host. It can be any string value.
The value set here is used by the Diameter client to identify your Diameter Gateway server as the connecting Diameter peer that is the source of the Diameter message.
For more information about how the Origin-Host AVP can be specified, refer to Internet Engineering Task Force (IETF) Network Working Group RFC 3588 (Diameter Base Protocol).
In the Origin Realm field, enter the value for the Origin-Realm AVP to be sent by the Diameter Gateway in outgoing Diameter requests.
This is the signaling realm (domain) that you assign your Diameter Gateway server.
The value set here is used by Diameter clients to identify your Diameter Gateway server as the source of the Diameter message.
For more information about how the Origin-Realm AVP can be specified, refer to Internet Engineering Task Force (IETF) Network Working Group RFC 3588 (Diameter Base Protocol).
The Diameter Gateway details you enter in this screen apply to one Diameter Gateway node instance that listens to all network interfaces for Diameter messages, which is suitable for basic testing directly after installation.
For a distributed environment, you must add Diameter Gateway node instances to your topology and configure a unique network interface for each instance after installation. See the discussion about adding Diameter Gateway nodes for online charging in "ECE Post-Installation Tasks".
Click Next.
The RADIUS Gateway Details screen appears.
Enter information that RADIUS clients use to identify your RADIUS Gateway server:
If you do not want RADIUS Gateway to start when ECE starts, select the Skip option.
If you select this option, do not enter values in the following fields.
In the Name field, enter the name of the RADIUS Gateway instance.
In the Port field, enter the port number assigned to RADIUS Gateway.
In the Shared Secret field, enter the common password shared between the RADIUS Gateway server and Network Access Server (NAS). It is used by the RADIUS protocol for security.
In the Wallet Location field, enter the path to the Oracle wallet that contains the SSL authentication and signature credentials (such as private keys, and certificates) and the root key for the RADIUS Gateway server.
The RADIUS Gateway details you enter in this screen apply to a single RADIUS Gateway instance (node) that listens to all network interfaces for RADIUS messages, which is suitable for basic testing directly after installation.
For a distributed environment, you must add RADIUS Gateway instances (nodes) to your topology and configure a unique network interface for each instance after installation. See the discussion about adding RADIUS Gateway nodes in "ECE Post-Installation Tasks".
Click Next.
The Third-Party Library Details screen appears.
In the Directory field, enter the patch or browse to the directory that contains the JAR files required by ECE, which you copied to this directory before running the installer.
Click Next.
The Summary screen appears.
Review your selections, and click Install.
The Install screen appears, and the installation begins.
Note:
If you click Cancel after the installation begins, the installation stops, but files already copied are not removed.When the installation is done, the End of Installation screen appears.
The installer checks for all required software and displays errors if it detects any missing or unavailable components or if any connectivity issues occur.
For information about verifying the installation of ECE, see "Verifying the ECE Installation."
For information about ECE installer logs, see "Troubleshooting the ECE Installation."
An ECE standalone system is a self-contained, nonproduction version of ECE that is not integrated with BRM or Pricing Design Center (PDC). Use the stand-alone system for evaluation, demonstration, and functional testing.
During the installation, refer to the required information that you previously collected. See "Information Requirements".
To install a standalone ECE system:
Create a temporary directory (temp_dir).
Go to the My Oracle Support Web site:
Sign in with your user name and password.
Click the Patches & Updates tab.
From the list, select Patch Name or Number.
In the text field, enter TBD and click Search.
The Patch Search Results page appears.
Click the patch name.
The patch details appear.
From the Platform list, select the platform and click Download.
The File Download dialog box appears.
Download the pTBD_113090_platform.zip software pack to temp_dir, where platform is linux or solaris.
Unzip pTBD_113090_platform.zip and extract the contents to temp_dir:
The extracted software pack has the following structure:
ocece/Disk1/install
ocece/Disk1/stage
Go to the ocece/Disk1/install/ directory, and run one of the following commands:
To start the GUI installer:
./runInstaller
To start the GUI installer and create a silent installer response file during the installation:
./runInstaller -record -destinationFile path
where path is the response file location and name.
The Welcome screen appears.
Click Next.
The Specify Inventory Directory and Credentials screen appears.
Note:
The installer creates an Inventory directory if it does not detect any installed Oracle products on the system. The Inventory directory manages all Oracle products installed on your system.In this screen, enter the following if you do not want to accept the defaults:
Full path of the inventory directory
Name of the operating system group that has write permission to the inventory directory
Click Next.
The Select Installation Type screen appears.
Select Standalone, and click Next.
The Specify Home Details screen appears.
(Optional) Enter the following information if you do not want to accept the default values:
In the Name field, enter a name for the standalone ECE installation, or select a name from the list.
In the Path field, enter the full path or browse to the directory in which to install the standalone ECE software.
Click Next.
The Select ECE Security Options screen appears.
Select one of the ECE security options described in the following table.
For more information, see BRM Elastic Charging Engine Security Guide.
| Option | Description |
|---|---|
| Security disabled | Enables no security configurations.
(Single server installation only) |
| Security enabled without SSL | Enables the following security configurations:
|
| Security enabled with SSL | Enables the following security configurations:
|
Click Next.
The Persistence Data Details screen appears.
In the Directory field, enter the path or browse to the directory into which the ECE BrmCdrPluginDirect Plug-in will write call detail record (CDR) files of rated events.
This is the directory where the plug-in stores completed CDR files that are ready to be processed by BRM.
Click Next.
The ECE Cluster Details screen appears.
Enter information about the ECE cluster:
Note:
(Linux) If you used the ece_provision script to provision your environment for an ECE installation, the user name for host machines you enter in the ECE Cluster Details screen must be the same user name you entered for the ECE_USER field in the ece_provision_config.sh file.In the User Name for Host Machines field, enter the user name you specified when you created the ECE user account prior to installation. All machines in the cluster must have the same user name.
This user name is used by the Elastic Charging Controller for identifying the remote machines on which to deploy ECE.
In the Java Heap Settings field, specify the memory to allocate to each node in the ECE cluster.
The memory applies to each node for the driver machine and all server machines.
In the Cluster Name field, enter the cluster name used by applications to identify ECE in the cluster. For example, Oracle Enterprise Manager Cloud Control uses the cluster name to locate ECE nodes for monitoring.
The cluster name must contain fewer than 32 characters.
Click Next.
The Coherence Grid Security screen appears.
Note:
(Linux) If you used the ece_provision script to provision your environment for an ECE installation, authorized host list information you enter in the Coherence Grid Security screen must be the same host information you entered for the HOST field in the ece_provision_config.sh file.Specify the machines allowed to be part of the Coherence cluster and the credentials required for accessing the cluster.
To specify the machines, do one or both of the following:
In the Host Details in Comma Separated Format field, list the host names or IP addresses of all machines on which ECE nodes will reside. Separate each value with a comma.
Include your computer name in this field. Do not enter localhost or a loopback address.
Include all server machines across which the Coherence grid is deployed and any other machine that is to be part of the grid.
Specify a range of allowed addresses for hosts in the same subnet as follows:
In the Host Details Range from IP Address field, enter the valid IP address that starts the range.
In the Host Details Range to IP Address field, enter the valid IP address that ends the range.
To specify the credentials required to access the cluster:
In the Alias Name for Coherence Grid Security field, enter the account alias that defines the administrator for securing the Coherence cluster.
In the Password for the Alias field, enter the password used to access the cluster security key in the Coherence keystore (the ECE_home/oceceserver/config/server.jks file).
This is the password for Coherence cluster security.
You use this password when enabling SSL.
See the discussion about Coherence cluster security in BRM Elastic Charging Engine Security Guide.
Click Next.
The Oracle NoSQL Database Details screen appears.
Specify the NoSQL database connection information:
In the Host Name field, enter the host name or IP address of the machine on which the Oracle NoSQL database is installed.
In the Port Number field, enter the port number assigned to the NoSQL database service.
In the NoSQL Datastore Name (database name) field, enter the name of the NoSQL data store into which ECE will publish rated events.
This is where Rated Event Publisher writes rated events generated by the ECE server.
Click Next.
The KeyStore Credentials screen appears.
Specify the keystore credential information required for the ECE installation.
For information about keystore credentials, see BRM Elastic Charging Engine Security Guide and the discussion about setting up and managing ECE security in BRM Elastic Charging Engine System Administrator's Guide.
In the Key Password for Boundary System Alias field, enter the password ECE uses to access the boundary system alias key in the keystore JKS file (ECE_home/oceceserver/config/keystore.jks).
In the Certificate store password field, enter the password used to access the server JKS file and the keystore JKS file:
ECE_home/oceceserver/config/keystore.jks
Stores symmetric keys for boundary system password encryption.
ECE_home/oceceserver/config/server.jks
Stores credentials for cluster node authentication details. This file is also used for encrypting intra-cluster communication over SSL.
These files share the same key and store password.
In the DName (Distinguished Name) field, specify the credentials that define what users are authorized to do regarding cluster security.
Examples:
CN=Administrator,OU=Rating,O=CompanyB
Or:
CN=Developer,OU=ECE
where:
CN is the common name for the user.
OU is the organizational unit of the user.
O is the organization of the user.
The combined DName values are similar to a group in UNIX.
Tip:
The value set here (in creating the certificate) is used for authentication in the cluster and must be the same as the value used in the ECE_home/oceceserver/config/permissions.xml file, which is created after installation and used for authorization in the cluster.You use the DName value when enabling SSL.
The DName value is used as a command line parameter for creating the server.jks keystore and the keystore.jks keystore.
Click Next.
The ECE Notification Queue Details screen appears.
Enter the Java Message Service (JMS) credentials for the JMS server on which the ECE notification queue (JMS topic) is to reside.
ECE publishes notification events into this JMS queue (JMS topic), which external systems can use to obtain data for their own processing.
After you install ECE, you run a post-installation script that creates the JMS queue (JMS topic) on the server.
In the Host Name field, enter the host name of the server on which the JMS queue (JMS topic) resides.
In the Port Number field, enter the port number of the server on which the JMS topic resides.
In the User Name field, enter the user name for logging in to the server on which the JMS queue (JMS topic) resides.
In the Password field, enter the password for logging in to the server on which the JMS queue (JMS topic) resides.
In the Connection Factory Name field, enter the connection factory name used to create connections to the JMS queue (JMS topic) queue.
After installing ECE, you run an ECE post-installation script that creates the JMS queue (JMS topic) on the server. The connection factory name entered here is used by the script to create connections to the JMS queue (JMS topic).
In the Topic Name field, enter the name of the JMS queue (JMS topic) on the server to which ECE publishes notification events.
After installing ECE, you run a post-installation script that creates the JMS queue (JMS topic) on the server. The topic name entered here is the name the ECE post-installation script uses to create the JMS queue (JMS topic).
Click Next.
The ECE Notification Queue SSL Details screen appears.
Enter secure socket layer (SSL) information required to connect to the Java Message Service (JMS) queue to which ECE publishes notification events:
If you will not use SSL to encrypt communication between ECE and the JMS queue, select the Disable SSL option.
If you select this option, do not enter values in the following fields.
In the Keystore password field, enter the password used to access the SSL keystore file.
In the Keystore location field, enter the full path to the SSL keystore file.
Click Next.
The Diameter Gateway Details screen appears.
Enter information that Diameter clients use to identify your Diameter Gateway server:
If you do not want Diameter Gateway to start when ECE starts, select the Skip option.
If you select this option, do not enter values in the following fields.
In the Origin Host field, enter the value for the Origin-Host attribute-value pair (AVP) to be sent in the Diameter request.
This is a unique identifier that you assign your Diameter Gateway server on its host. It can be any string value.
The value set here is used by the Diameter client to identify your Diameter Gateway server as the connecting Diameter peer that is the source of the Diameter message.
For more information about how the Origin-Host AVP can be specified, refer to Internet Engineering Task Force (IETF) Network Working Group RFC 3588 (Diameter Base Protocol).
In the Origin Realm field, enter the value for the Origin-Realm AVP to be sent by the Diameter Gateway in outgoing Diameter requests.
This is the signaling realm (domain) that you assign your Diameter Gateway server.
The value set here is used by Diameter clients to identify your Diameter Gateway server as the source of the Diameter message.
For more information about how the Origin-Realm AVP can be specified, refer to Internet Engineering Task Force (IETF) Network Working Group RFC 3588 (Diameter Base Protocol).
The Diameter Gateway details you enter in this screen apply to one Diameter Gateway node instance that listens to all network interfaces for Diameter messages, which is suitable for basic testing directly after installation.
For a distributed environment, you must add Diameter Gateway node instances to your topology and configure a unique network interface for each instance after installation. See the discussion about adding Diameter Gateway nodes for online charging in "ECE Post-Installation Tasks".
Click Next.
The RADIUS Gateway Details screen appears.
Enter information that RADIUS clients use to identify your RADIUS Gateway server:
If you do not want RADIUS Gateway to start when ECE starts, select the Skip option.
If you select this option, do not enter values in the following fields.
In the Name field, enter the name of the RADIUS Gateway instance.
In the Port field, enter the port number assigned to RADIUS Gateway.
In the Shared Secret field, enter the common password shared between the RADIUS Gateway server and Network Access Server (NAS). It is used by the RADIUS protocol for security.
In the Wallet Location field, enter the path to the Oracle wallet that contains the SSL authentication and signature credentials (such as private keys, and certificates) and the root key for the RADIUS Gateway server.
The RADIUS Gateway details you enter in this screen apply to a single RADIUS Gateway instance (node) that listens to all network interfaces for RADIUS messages, which is suitable for basic testing directly after installation.
For a distributed environment, you must add RADIUS Gateway instances (nodes) to your topology and configure a unique network interface for each instance after installation. See the discussion about adding RADIUS Gateway nodes in "ECE Post-Installation Tasks".
Click Next.
The Third-Party Library Details screen appears.
In the Directory field, enter the patch or browse to the directory that contains the JAR files required by ECE, which you copied to this directory before running the installer.
Click Next.
The Summary screen appears.
Review your selections, and click Install.
The Install screen appears, and the installation begins.
Note:
If you click Cancel after the installation begins, the installation stops, but files already copied are not removed.When the installation is done, the End of Installation screen appears.
The installer checks for all required software and displays errors if it detects any missing or unavailable components or if any connectivity issues occur.
For information about verifying the installation of ECE, see "Verifying the ECE Installation."
For information about ECE installer logs, see "Troubleshooting the ECE Installation."
The ECE installer enables you to install one or more of the following individual ECE components:
ECE Server. This option is equivalent to the ECE Complete installation. See "Installing All ECE Components."
ECE Third-Party Dependent JARs. This option installs the ojdbc7.jar and wlthint3client.jar files, which enable the ECE installer to connect ECE to BRM if BRM is in a secure mode. To obtain the JAR files required to install ECE in a secure mode, see "Obtaining Required JAR Files."
ECE SDK. This option installs the ECE software development kit. See the discussion about the ECE SDK in BRM Elastic Charging Engine Implementation Guide for more information.
During the installation of these components, refer to the required information that you previously collected. See "Information Requirements".
To install an individual ECE component:
Create a temporary directory (temp_dir).
Go to the My Oracle Support Web site:
Sign in with your user name and password.
Click the Patches & Updates tab.
From the list, select Patch Name or Number.
In the text field, enter 28738541 and click Search.
The Patch Search Results page appears.
Click the patch name.
The patch details appear.
From the Platform list, select the platform and click Download.
The File Download dialog box appears.
Download the p28738541_113090_platform.zip software pack to temp_dir, where platform is linux or solaris.
Unzip p28738541_113090_platform.zip and extract the contents to temp_dir:
The extracted software pack has the following structure:
ocece/Disk1/install
ocece/Disk1/stage
Go to the ocece/Disk1/install/ directory, and run one of the following commands:
To start the GUI installer:
./runInstaller
To start the GUI installer and create a silent installer response file during the installation:
./runInstaller -record -destinationFile path
where path is the response file location and name.
The Welcome screen appears.
Click Next.
The Specify Inventory Directory and Credentials screen appears.
Note:
The installer creates an Inventory directory if it does not detect any installed Oracle products on the system. The Inventory directory manages all Oracle products installed on your system.In this screen, enter the following if you do not want to accept the defaults:
Full path of the inventory directory
Name of the operating system group that has write permission to the inventory directory
Click Next.
The Select Installation Type screen appears.
Select Custom, and click Next.
The Specify Home Details screen appears.
(Optional) Enter the following information if you do not want to accept the default values:
In the Name field, enter a name for the component installation, or select a name from the list.
In the Path field, enter the full path or browse to the directory in which to install the component.
Click Next.
The Available Product Components screen appears.
In the Components list, select the components to install, and deselect any other selected components.
Click Next.
Do one of the following:
If a screen other than the Summary screen appears, provide the requested information, and click Next.
Continue moving through the screens until the Summary screen appears.
If the Summary screen appears, review your selections, and click Install.
The Install screen appears, and the installation begins.
Note:
If you click Cancel after the installation begins, the installation stops, but files already copied are not removed.When the installation is done, the End of Installation screen appears.
The installer checks for all required software and displays errors if it detects any missing or unavailable components or if any connectivity issues occur.
For information about verifying the installation of ECE, see "Verifying the ECE Installation."
For information about ECE installer logs, see "Troubleshooting the ECE Installation."
The silent installation uses a response file in which you have set installation information. To obtain the response file, you run the GUI installer for the first install. The GUI installer generates a response file that contains the key-value pairs based on the values that you specify during the GUI installation. You can then copy and edit the response file to create additional response files for installing ECE on different machines.
The response file must contain the key-value pairs for the mandatory installation parameters used for the ECE software component you install. All information requested in the GUI installation is associated with mandatory parameters.
The parameters in the response file can also be specified on the command line, although specifying all of them on the command line is not recommended. You could, however, have a standard file with set options and then specify, for example, the log locations on the command line. If an option is specified both in the file and on the command line, the command-line option takes precedence over the value in the file.
To create a response file:
Run the GUI installation for the ECE software component you want to install. Use the command that generates a response file. See "Installing ECE by Using the GUI Installation."
A response file containing the required parameters is generated in the ECE_home/Disk1/stage/Response directory.
Copy the response file, and give the copy a different file name.
You can create as many response files as needed.
Modify the response file you copied by specifying the key-value information for the parameters you want in your installation.
Save and close the response file.
To perform a silent installation:
Create a response file. See "Creating a Response File."
Create a temporary directory (temp_dir).
Go to the My Oracle Support Web site:
Sign in with your user name and password.
Click the Patches & Updates tab.
From the list, select Patch Name or Number.
In the text field, enter 28738541 and click Search.
The Patch Search Results page appears.
Click the patch name.
The patch details appear.
From the Platform list, select the platform and click Download.
The File Download dialog box appears.
Download the p28738541_113090_platform.zip software pack to temp_dir, where platform is linux or solaris.
Unzip p28738541_113090_platform.zip and extract the contents to temp_dir:
The extracted software pack has the following structure:
ocece/Disk1/install
ocece/Disk1/stage
Copy the response file you created to the machine on which you will run the silent installation.
On the machine on which you will run the silent installation, go to the ocece/Disk1/install/ directory, and run the following command:
./runInstaller.sh [parameter=value] -responseFile path -silent
where:
path is the location and name of your response file.
parameter is the name of an installation parameter.
value is the value of the installation parameter.
For example:
./runInstaller.sh INSTALL_TYPE=Complete -responseFile /tmp/ece_complete.rsp -silent
The ECE installer checks for all required software and writes errors to a log file if it detects any missing or unavailable components or if any connectivity issues occur.
For information about verifying the installation of ECE, see "Verifying the ECE Installation."
For information about ECE installer logs, see "Troubleshooting the ECE Installation."
After you install ECE, perform the post-installation tasks. See "ECE Post-Installation Tasks."
Note:
To uninstall ECE, you run the GUI installation and click Next until you reach the Specify Home Details screen. In the Specify Home Details screen, click Installed Products. In the Inventory screen, select the ECE components to uninstall, and then click Remove.