Oracle® Fusion Applications Post-Installation Guide 11g Release 7 (11.1.7) Part Number E22380-08 |
Home |
Contents |
Book List |
Contact Us |
Previous |
Next |
This chapter contains the following:
Setting Up Implicit Personalization Behavior
Setting Up Web Services Security
Note
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 $HOME/bhd/fusionapps/crm/ewm/bhd/bin
directory.
jps-config-jse.xml
default-keystore.jks
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:
Server Platform |
Action |
---|---|
UNIX |
Navigate to the fusionapps/crm/ewm/bhd directory and enter the following command:
|
MS Windows |
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.
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.
Important
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.
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.
Note
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
located at 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:cust-config>
section:
<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
This table covers the configurations you perform for each security scheme.
Security Scheme |
Configuration Required |
---|---|
Secure Sockets Layer (SSL) Security |
A CRM user typically includes the following information in the SR:
Perform the following steps to resolve SSL errors:
|
Message Protection Security |
A CRM user typically includes the following information in the SR:
Perform the following steps to resolve message protection errors:
|