| Oracle® Communications Marketing and Advertising Installation Guide Release 5.1 Part Number E20239-01 |
|
|
View PDF |
| Oracle® Communications Marketing and Advertising Installation Guide Release 5.1 Part Number E20239-01 |
|
|
View PDF |
The standard installation of Oracle Communications Marketing and Advertising automatically installs a modified version of Oracle Communications Services Gatekeeper to act as the system's message delivery mechanism.
If your environment already has Services Gatekeeper installed, this installation can be used as the basis for an overlay installation of Marketing and Advertising.
To perform an overlay installation of Marketing and Advertising, prepare your current installation as follows:
After you have installed Marketing and Advertising, you must update your Services Gatekeeper domain configuration. You can only update like to like domains. A clustered domain using a single Oracle database can only be updated to a clustered domain using a single Oracle database, and an HA domain can only be updated to an HA domain, etc.
Marketing and Advertising is compatible only with the most recent version of Services Gatekeeper, version 5.0. If you are running a previous version of the product, you will need to perform an upgrade. See the upgrade documentation for Services Gatekeeper 5.0 for more information.
You must create a database user account for Marketing and Advertising, in addition to the user account you have provisioned for Services Gatekeeper. Depending on the database you are using, you may also need to create a database (MySQL only). For more information on this process, see Creating a MySQL Database.
When running the Marketing and Advertising installation program, choose the MIDDLEWARE_HOME directory that houses your Services Gatekeeper installation. The installer detects the existing Services Gatekeeper installation and adds only the necessary files.
Some existing Services Gatekeeper files will be patched to be compliant for use with Marketing and Advertising. A Smart Update patch, NXPY, is created that contains the modified jar(s) from Services Gatekeeper 5.0 that are needed by Marketing and Advertising.
The NXPY patch contains modified versions of the following files:
wlng.jar
wlngSecurityProviders.jar (jar is backed up and replaced with the patched jar)
com.bea.wlcp.wlng.storage.tc_5.0.jar
Patched ear files from OCSG 5.0 are included in the installer as well. All existing ear files are backed up and replaced with the patched ears.
wlng_nt_sms_px21.ear
wlng_nt_multimedia_messaging_px21.ear
wlng_nt_push_message_ews.ear
wlng_nt_multimedia_messaging_mm7.ear
cdr_to_diameter-single.ear
cdr_to_diameter.ear
If you have previously patched any of the files that were changed by the NXPY Smart Update patch, re-apply those patches.
To update the domain configuration:
Run the domain configuration wizard, selecting Extend an existing Oracle Communications Marketing and Advertising domain.
The Select a WebLogic Domain Directory window opens
Navigate to your current Services Gatekeeper domain home and select it. In a default installation this would be MIDDLEWARE_HOME\user_projects\oscg-domain.
Click Next.
The Select Extension Source window opens.
The correct path to the template extensions is already filled in.
Click Browse to select your template.
The Select a Template dialog box appears.
Select the domain type that matches your current domain: ocma-cluster-rac-domain-ext.jar if you have a RAC-based domain and so forth.
When the dialog box disappears, click the radio button next to Extend my domain using an existing template to make sure it is active.
The Customize JDBC and JMS File Store Settings window opens.
Select the Yes radio button.
The Configure JDBC Data Sources window appears.
Click the ocma.datasource entry.
Add the database information and the username and password you created earlier for Marketing and Advertising.
Click Next.
The Populate Database window appears. It will move to the next to screen automatically.
The update domain wizard in console mode is also supported. See Configuring the Domain Using the Console Configuration Wizard for general information on using the console mode.
In addition there are WLST scripts available. See Configuring the Domain Using the Oracle WebLogic Tool Scripts for general information on using WLST. If you use the WLST scripts, you need to use one additional script, ocma-database-setup.py, to add the Administrative username/password to the database for use with Marketing and Advertising.
The rest of the wizard runs as in the original installation, described in Configuring a Domain with the GUI Configuration Wizard - UNIX/Linux.
If you have previously made changes to your EDR, CDR, or Alarm configurations that you wish to keep, you must merge the contents of your customized configurations with the changes that installing Marketing and Advertising has made.
When you installed the software, your customizations were saved in a file named domainhome\config\custom\wlng-edr.xml.bak. The Marketing and Advertising version is in the same directory, named wlng-edr.xml. Merge the two files into a single file, either by editing the xml file directly or by re-adding your changes using the Services Gatekeeper console extension. On the console, under Domain Structure, click the + by OCSG to open up the console extension. Then click EDR Configuration.
The main Administrative user for Services Gatekeeper must be added to the systemowner management user group in Marketing and Advertising This enables the Administrative user username and password to be used for the initial login to the Marketing and Advertising GUI.
In a standard Marketing and Advertising installation/domain configuration, this is taken care of automatically, but if you are setting up an overlay installation, you need to do this additional step.
To add the main Administrative user to the systemowner group, there are two options:
Use the Administration console
Use a special WLST script
These instructions assume that you have set up your extended domain using the steps described in Updating the Domain Configuration.
To use the Administration console to add your main administrative user to the systemowner group.
Open the administration console.
In the left Domain Configuration panel, click Security Realms.
The Summary of Security Realms page opens.
Click myrealm.
The Settings for myrealm page opens.
Click the Users and Groups tab.
The Users tab containing the list of users is presented.
Click your Administrative user. This should be described as "This user is the default administrator".
The Settings for <user name> table containing the list of users is presented.
Click the Groups tab.
From the Available list on the left side, select systemowner.
Click the right pointing arrow (->) to move it to the Chosen list on the right side.
Click the Save button. Make sure the green "Settings updated successfully" message appears.
You can use a script to add your Administrative user to the systemowner group.
The script is ocma-update-user-group.py in MIDDLEWARE_HOME\wlserver_10.3\common\templates\scripts\wlst.
To run the script, launch it using the parameters:
java weblogic.WLST ocma-update-user-group.py admin server url admin username username systemowner
where:
admin server url is the URL of the running Administration server
admin username is the Administration username for authenticating the action
username is the username to add to the group, which should be the same as the admin username
The script will prompt for your Administration password.
|
 Copyright © 2009, 2011, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|
