Applications Post-Installation Guide
11g Release 1 (11.1.3)
Part Number E22380-04
This chapter contains the following:
Setting Up E-Mail Marketing
Setting Up SMS Marketing
Setting Up Sales Prediction Engine
Setting Up Implicit Personalization Behavior
The E-Mail Marketing Server is a combination of components designed to support high volume, personalized e-mail messages, and to track e-mail bounces and click-through responses. The bounce handling daemon (BHD) tracks e-mail messages that cannot be delivered, parses the returned e-mail messages, and records the cause of the e-mail bounce.
The bounce handling daemon installation program is available on the Fusion Applications companion disk. Prior to installing the program, ensure you have provisioned the Marketing application, noting the SOA host and port, and determined the designated server to place the daemon. The designated server must have port 25 available.
It is recommended that you place the bounce handling daemon in the DMZ. Optionally, you can place the bounce handling daemon behind an inbound mail transfer agent (MTA). The approach that you choose depends on the configuration of your network, DMZ, existing inbound mail transfer agent, and firewall.
Complete the following steps to install and configure the bounce handling daemon:
Using the companion disk, locate
and run the installation program:
fusionbhd/Disk1/runInstaller. Provide information when prompted, such as the JDK location, designated
BHD server installation directory, and the http or https protocol,
host and port for the Marketing SOA URL.
Navigate to the
WLS_HOME/config/fwmconfig directory and copy the files and
directory listed below to the
bootstrap directory (including the cwallet.sso)
Update the root user permissions to allow read, write, and execute access to the jps-config-jse.xml and default-keystore.jks files and the bootstrap directory.
Update the root user permissions to allow read, write, and execute access to the BHD server installation directory, it's subdirectories and files. The top level BHD server installation directory is specified during the install process.
Grant read access to the fusionapps/crm/ewm/bhd/logs directory to nonroot users to provide availability to application log files.
Sign in as a root user and enter the following to start the BHD service for port 25:
Navigate to the fusionapps/crm/ewm/bhd directory and enter the following command:
Run the bhd.exe executable file.
For more information on provisioning, see the Oracle Fusion Applications Quick Installation Guide. For more information on configuring other aspects of the e-mail server for marketing, see the Oracle Fusion Applications Marketing Implementation Guide.
To use the SMS marketing campaign capability within Oracle Fusion Customer Relationship Management, you need to enable it after installing Oracle Fusion Applications. Customers interested in SMS marketing campaigns will need to complete SMPP Driver configuration in the SOA suite component Oracle User Messaging Service.
An instance of the SMPP driver is already installed as part of the Oracle Fusion Applications installation and is a part of the Oracle User Messaging Service, but it does not point to any User Messaging Server. To configure the SMPP driver, you need to have an account with an SMPP driver gateway vendor. For configuration instructions and the list of verified/approved 3rd party SMPP driver gateway vendors, refer the Oracle Fusion Middleware Administrator's Guide for Oracle SOA Suite on My Oracle Support.
Before proceeding with the enabling process, ensure that you have access rights to update and deploy applications on the WebLogic Administration Console and Oracle Enterprise Manager associated with the Customer Relationship Management domain.
Sign in to the WebLogic Administration Console associated with the Customer Relationship domain.
Under Deployments, you see the application usermessagingdriver-smpp in the Installed state.
Expand usermessagingdriver-smpp and navigate to Targets tab. The Current Targets column shows (None specified), indicating that no target is configured.
On the console, switch to the Lock and Edit mode, update the target to all servers in the CRM_SOACluster, and save the changes.
While remaining in the Lock and Edit mode for the console, navigate to Deployments, select the check box next to usermessagingdriver-smpp and click Update. The Update Application Assistant wizard appears.
For the Deployment Plan Path field, click Change Path and select the Fusion Applications specific deployment plan APPTOP/instance/applications/ums/crm/usermessagingdriver-smpp_FusionPlan.xml.
Proceed to the subsequent screen of the Update Application Assistant wizard and select Release Configuration to commit the changes made until this point. The state of the application usermessagingdriver-smpp changes to Active.
Sign out of WebLogic Administration Console.
Sign in to the Oracle Enterprise Manager associated with the Customer Relationship Management domain.
Expand CRMDomain - User Messaging Service, right-click the application usermessagingdriver-smpp and select SMPP Driver Properties from the context menu.
Configure the driver and apply the changes.
Restart the application usermessagingdriver-smpp to bring into effect the driver configuration changes.
You can now use the SMS Marketing capability of Oracle Fusion Customer Relationship Management.
To run the Oracle Fusion Sales Prediction Engine in Oracle Fusion Applications Customer Relationship Management (CRM), perform the following post-installation tasks if you deployed Oracle Business Intelligence Applications and have created the Oracle Business Analytics Warehouse. For information on deploying and setting up Oracle Business Intelligence Applications, refer to the Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications.
However, if you deployed only Oracle Transactional Business Intelligence, you need not perform these steps to run the Oracle Fusion Sales Prediction Engine.
You can create the Data Warehouse objects using the Sales Predictor Repository Creation Utility (RCU). To run the Sales Predictor RCU , ensure that the Oracle Business Intelligence Application (OBIA) Data Warehouse database and the related schema including database objects such as tables, are available. The Sales Predictor RCU creates Sales Predictor related Data Warehouse database objects such as Oracle Data Mining tables, views, packages, Oracle Real-time Decisions (RTD) Inline Service Processing tables, and the purge package in the existing OBIA schema.
Initiate the Sales Predictor RCU following these instructions.
Access the rcuBIZSPApps.zip file from the following location, and extract its contents to a local directory.
In Windows NT, the location is FAINTEG_BASE/fainteg/shiphome/rcu/nt/rcuBIZSPApps.zip
In Linux, the location is FAINTEG_BASE/fainteg/shiphome/rcu/linux/rcuBIZSPApps.zip
Run the following command pointing to the BIN folder within the local directory:
In Windows NT, use
rcu -variables BI_SCHEMA_NAME=<OBIA Schema name>
In Linux, use
./rcu -variables BI_SCHEMA_NAME=<OBIA Schema name>
<OBIA Schema name> refers to the name of the OBIA schema that is used, and is an input parameter for the Sales Predictor RCU.
The Sales Predictor RCU wizard appears.
On the Welcome page, click Next and on the Create Repository page, ensure that the default option Create is selected and click Next.
On the Database Connection Details page, provide the following information and click Next.
Host Name: Name of the server where the database is located.
Port: The database port number.
Service Name: The service name of the database.
Username: SYS. It is the user name associated with an administrative role.
Password: Password used in combination with the user name to access the database.
Role: SYSDBA. It is the role with administrative access rights.
The provided information is processed through a prerequisite check.
On the confirmation dialog box, click OK.
On the Select Components page, select the Oracle Application Components, and click Next.
On the confirmation dialog box, click OK.
On the Schema Passwords page, ensure that the Use same passwords for all schemas option is selected. Selecting this option provides the password used with the existing OBIA Schema Name.
Enter the password again to confirm it, and click Next.
On the Map Tablespaces page, click Next and on the confirmation box that subsequently appears, click OK.
On the Summary page, review the database information provided until this point. If necessary, click Back to change details in the previous pages.
Click Create to create the Data Warehouse objects. The Completion Summary page confirms the successful creation of the objects.
The Data Warehouse requires a Java Naming and Directory Interface (JNDI) data source connection named DWDS that points to the Online Analytical Processing (OLAP) database residing on Oracle BI server. To create the data source using the RTD WebLogic Server console, follow these instructions.
In the WebLogic Server console, open Services - JDBC - Data Sources and click New.
On the JDBC Data Source Properties page, provide the following details and click Next.
JNDI Name: DWDS
Database Type: Oracle
Database Driver: Oracle Driver (Thin) for Instance connections
On the Transaction Options page, ensure that the default property Supports Global Transactions is selected, and click Next.
On the Connection Properties page, provide the following values, and click Next.
Database Name: The Unique System ID (SID) of the database
Host Name: The name of the computer that hosts the database
Port: The port number of the database
Database User Name: User credential to access the database
Password: The password used in combination with the Database User Name to access the database
On the Test Database Connections page, review the details provided until this point, test the connectivity to the database, and click Next.
Select the Oracle BI Server where you want to make the data source available, and click Finish.
To enable connectivity to Data Warehouse, you must set the value for the profile option.
You can set the value for this profile option using Applications Core Setup, if you have roles allowing access to do so. The Application Implementation Administrator abstract role provides the necessary access.
Sign in to the Oracle Fusion Applications Core Setup.
Under the Tasks menu on the left side of the page, click Manage Administrator Profile Values. The Manage Administrator Profile Values tab appears.
In the Profile Option Code field, enter ZCA_WAREHOUSE_ENABLED_BI and click Search. The profile option appears in the search results.
In the Profile Values region, select the result item associated with the searched profile option, and under the Profile Value column, set the value to Yes.
The Sales Predictor Inline Service within RTD uses the profile option to point to the Data Warehouse tables.
You can point RTD to the Data Warehouse in one of the following ways:
Restart the RTD application server. The Sales Predictor Inline Service is reloaded and points to the Data Warehouse.
Manually redeploy the Sales Predictor Inline Service if restarting the RTD application server does not work. Before you manually redeploy, ensure that the following prerequisites are met:
You have roles allowing access to deploy the Sales Predictor Inline Service.
Java Development Kit (JDK) 1.6 or higher version is available and running on the same server
You must have access to the command line tool zip file rtd-deploytool-11.1.1.zip. The zip file resides within the RTD client zip file (rtd_client_126.96.36.199.0.zip), which is available in the BI_MW_HOME/Oracle_BI1/clients/rtd directory.
To manually redeploy the Sales Predictor Inline Service, follow these instructions.
Extract the contents of the file rtd_client_188.8.131.52.0.zip to a local directory.
In the local directory, go to the folder ./client/CommandLineDeploy, locate rtd-deploytool-11.1.1.zip and extract its contents to a folder.
In that folder, locate ./OracleBI/RTD/deploytool folder and within that folder, open a command prompt terminal.
Ensure that the JDK classpath is set for the command prompt terminal.
Run the command:
java -jar deploytool.jar -deploy -server <Server Host> -port <Port>
-terminateSessions true <Full path of Directory/ Zip File>.
When prompted, provide the user name and password to connect to the RTD server.
The message Deploymentstateid: id. Deployed SPE_ILS.zip to server port in state: Development appears indicating completeness of deployment of the Sales Predictor Inline Service.
The Oracle Fusion Sales Prediction Engine can also use data from the following Data Warehouse entity tables to make more accurate predictions:
Also, it is necessary to load either Assets or Orders tables into the corresponding Data Warehouse table. Once the data in the Data Warehouse entity tables are ready, you can go to the Schedule Predictive Model Training page to run the model training process.
For more information on OBIA, see Oracle Fusion Middleware Configuration Guide for Oracle Business Intelligence Applications.
This topic covers the post-deployment activities required for Oracle Fusion CRM applications that support implicit personalization behavior.
Performing these activities fixes the inconsistent implicit personalization behavior between sessions in the following Oracle Fusion CRM applications:
Oracle Fusion CRM Common
Oracle Fusion Territory Management
Oracle Fusion Customer Center
Oracle Fusion Marketing
Oracle Fusion Order Capture Common Components
Oracle Fusion Sales
Make the following changes to the adf-config.xml file as a post-deployment activity.
These steps are applicable only for the Oracle Fusion CRM applications where implicit personalization behavior is supported.
Shutdown the domain where the application is deployed.
Search for adf-config.xml file. For example, for Sales application, this file is typically
Sales <deploy directory>/SalesApp/V2.0/app/SalesApp/adf/META-INF/adf-config.xml
Back up adf-config.xml file.
Open adf-config.xml file in a text editor and comment out all occurrences of the tag
<adf-faces-config> under the root node
<adf-config>. . .</adf-config>. For example:
<!-- adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/config">. . . </adf-faces-config -->
Add the following after the commented section.
<adf-faces-config xmlns="http://xmlns.oracle.com/adf/faces/config"> <persistent-change-manager> <persistent-change-manager-class>oracle.adf.view.rich.change.MDSDocumentChangeManager</persistent-change-manager-class> </persistent-change-manager> <taglib-config> <taglib uri="http://xmlns.oracle.com/adf/pageeditor"> <tag name="layoutCustomizable"> <!-- Added to pass JAudit--> <attribute name="layout"> <persist-changes>true</persist-changes> </attribute> </tag> </taglib> <taglib uri="http://xmlns.oracle.com/adf/faces/customizable"> <tag name="showDetailFrame"> <persist-operations>all</persist-operations> <!-- Added to pass JAudit--> <attribute name="disclosed"> <persist-changes>true</persist-changes> </attribute> <attribute name="height"> <persist-changes>true</persist-changes> </attribute> </tag> <!-- Added to pass JAudit--> <tag name="portlet"> <attribute name="disclosed"> <persist-changes>true</persist-changes> </attribute> <attribute name="height"> <persist-changes>true</persist-changes> </attribute> </tag> </taglib> <taglib uri="http://xmlns.oracle.com/adf/faces/rich"> <tag name="column"> <persist-operations>all</persist-operations> <attribute name="displayIndex"> <persist-changes>true</persist-changes> </attribute> <attribute name="visible"> <persist-changes>true</persist-changes> </attribute> <attribute name="width"> <persist-changes>true</persist-changes> </attribute> </tag> </taglib> </taglib-config> </adf-faces-config>
Specifically for Customer Center
application, and as an additional step, locate these lines under the
<mds:match path="/oracle/apps/"> <mds:customization-class name="oracle.apps.fnd.applcore.customization.ProductFamilyCC"/> <mds:customization-class name="oracle.apps.fnd.applcore.customization.SiteCC"/> </mds:match>
When you comment the lines, they appear as:
<!--mds:match path="/oracle/apps/"> <mds:customization-class name="oracle.apps.fnd.applcore.customization.ProductFamilyCC"/> <mds:customization-class name="oracle.apps.fnd.applcore.customization.SiteCC"/> </mds:match>
Save and close the file
Start up the domain that hosts the Oracle Fusion CRM application