Deploying Sales Cloud for IBM Notes Sales Cloud · Deploying Sales Cloud for IBM Notes Chapter 2 Installing Oracle Sales Cloud for IBM Notes: Prerequisites 6 7. Change the SQL Predicate

OracleSales CloudDeploying Sales Cloud for IBM Notes

Release 11

Oracle® Sales Cloud Deploying Sales Cloud for IBM Notes

Part Number E67333-04

Copyright © 2011-2016, Oracle and/or its affiliates. All rights reserved.

Author: Gowri Sudhindra

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected byintellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast,modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, ordecompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them tous in writing.

If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the followingnotice is applicable:

U.S. GOVERNMENT END USERS: Oracle programs, including any operating system, integrated software, any programs installed on the hardware, and/or documentation, delivered to U.S. Government end users are "commercial computer software" pursuant to the applicable Federal Acquisition Regulationand agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the programs, including any operatingsystem, integrated software, any programs installed on the hardware, and/or documentation, shall be subject to license terms and license restrictionsapplicable to the programs. No other rights are granted to the U.S. Government.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use inany inherently dangerous applications, including applications that may create a risk of personal injury. If you use this software or hardware in dangerousapplications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. OracleCorporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners.

Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks orregistered trademarks of SPARC International, Inc. AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks ofAdvanced Micro Devices. UNIX is a registered trademark of The Open Group.

This software or hardware and documentation may provide access to or information on content, products and services from third parties. Oracle Corporationand its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. OracleCorporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products,or services.

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc

Oracle customers that have purchased support have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc


http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info

http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs

Oracle Sales CloudDeploying Sales Cloud for IBM Notes

Contents

Preface i

1 About this Guide 1Purpose .................................................................................................................................................................... 1

Additional Rererence Guides ..................................................................................................................................... 1

2 Installing Oracle Sales Cloud for IBM Notes: Prerequisites 3Installing Oracle Sales Cloud for IBM Notes: Prerequisites ........................................................................................ 3

Activating the Package ............................................................................................................................................. 3

Configuring the Installer Download ............................................................................................................................ 6

Customization of IBM Databases: Points to Consider ............................................................................................... 7

3 Installing Oracle Sales Cloud for IBM Notes 9Installing Using Automatic Binary: Procedure ............................................................................................................ 9

Installing Manually: Explained .................................................................................................................................. 16

Configuring .INI File: Explained ................................................................................................................................ 16

Installing Using Microsoft SMS or SCCM: Explained ............................................................................................... 17

Installing Silently Using Windows Group Policy: Procedure ..................................................................................... 18

Installing from Windows Command Prompt: Procedure .......................................................................................... 21

Installing Server Certificate: Procedure .................................................................................................................... 21

Can I use Oracle Sales Cloud for IBM Notes over the Citrix server? ........................................................................ 22

4 Administering Deployment Settings 23Updating the .ini File ............................................................................................................................................... 23

Login Parameters: Explained ................................................................................................................................... 24

5 Upgrading Oracle Sales Cloud for IBM Notes Binary 27Upgrading Binary Manually: Explained .................................................................................................................... 27

Customization Package Update Compatibility: Explained ........................................................................................ 28

Package-Product Compatibility Scenarios: Explained .............................................................................................. 31


6 Configuring Clients to use STS Authentication (SSO) 35Configuring IBM Notes to use STS Authentication: Prerequisites ............................................................................ 35

Obtaining the Configuration File: Explained ............................................................................................................. 35

Installing in STS Authentication Mode: Explained .................................................................................................... 35

Configuring STS Authentication Configuration File for IBM Notes: Explained ............................................................ 36

7 Uninstalling Oracle Sales Cloud for IBM Notes 43Uninstalling using Windows Control Panel: Procedure ............................................................................................. 43

Uninstalling using InstallShield Wizard: Procedure ................................................................................................... 43

Uninstalling using Windows Command Prompt: Procedure ..................................................................................... 44

Uninstalling using Microsoft SCCM: Procedure ....................................................................................................... 44


Preface

i

PrefaceThis preface introduces information sources that can help you use the application.

Oracle Applications HelpUse the help icon to access Oracle Applications Help in the application. If you don't see any help icons on your page,

click the Show Help icon in the global area. Not all pages have help icons. You can also access Oracle Applications Helpat https://fusionhelp.oracle.com/.

Using Applications Help

Watch: This video tutorial shows you how to find help and use help features.

GuidesTo find guides for Oracle Applications, go to the Oracle Help Center at http://docs.oracle.com/

Documentation AccessibilityFor information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Comments and SuggestionsPlease give us feedback about Oracle Applications Help and guides! You can:

• Send e-mail to: [email protected].

• Click your user name in the global area of Oracle Applications Help, and select Send Feedback to Oracle.

https://fusionhelp.oracle.com/

http://apex.oracle.com/pls/apex/f?p=44785:265:0::::P265_CONTENT_ID:10552

http://apex.oracle.com/pls/apex/f?p=44785:265:0::::P265_CONTENT_ID:10552

http://docs.oracle.com/



mailto:[email protected]


Preface

ii


Chapter 1About this Guide

1

1 About this Guide

PurposeThis guide is intended for anyone who is deploying Oracle Sales Cloud for IBM Notes.

The deployment guide describes the deployment methods for the Oracle Sales Cloud for IBM Notes client version 3.06.xx.This document provides screenshots and instructions for the following deployment aspects:

• Instructions for automatic binary deployment

• Instructions for manual .msi installation in per-user mode

• Instructions for SCCM .msi installation over the network in per-user

• Instructions for the upgrade of application binaries

• Instructions for package upgrade, including information on compatibility between the package versions deployed tothe client and the server. Compatibility between the new packages and the binaries being used.

• Instructions for automated deployment of user credentials (login parameters), including steps that describe how toconfigure login parameters using STS

• Instructions for the configuration of First Run Assistant parameters

• Instructions for uninstalling the product

The guide also describes the possible approaches for upgrading the Oracle Sales Cloud for IBM Notes client to a newerversion. It provides theoretical background as well as practical examples and best practices on how to handle the upgrade inspecific scenarios.

Additional Rererence GuidesYou can refer to related guides in Oracle Sales Cloud to understand more about Oracle Sales Cloud for IBM Notes.

Guide Description

Oracle Sales Cloud - Using Sales

Provides help for the sales business process, in a convenient format for downloading or printing.


Chapter 1About this Guide

2


Chapter 2Installing Oracle Sales Cloud for IBM Notes: Prerequisites

3

2 Installing Oracle Sales Cloud for IBM Notes:Prerequisites

Installing Oracle Sales Cloud for IBM Notes: PrerequisitesThis topic details the prerequisites for installing Oracle Sales Cloud for IBM Notes.

Before installing, you must complete the following steps:

1. Ensure that your configuration meets System Requirements.2. Set up at least one e-mail account profile in IBM Notes.3. Activate the IBM Notes Package on the Manage Outlook Client Deployment Packages.4. Configure the IBM Notes Installer download on the Preferences page.

Caution: Set up only one location in IBM Notes before installing Oracle Sales Cloud for IBM Notes. Do notswitch between Locations, since it will lead to plugin malfunction.

A single Domino account should never be shared by multiple installations of Oracle Sales Cloud for IBM Notes. Customerswith multiple Fusion CRM environments must ensure that they use a different Domino account for each installation of the IBMNotes client.



4

Activating the PackageThis topic explains how to activate the IBM Notes package.

To activate the IBM Notes package:

1. Log in to Authorization Management (APM) to change the name of the Active Package.

2. Select Database Resources from the Search drop-down list.3. Search for Outlook Edition Metadata Package.



5

4. Select Outlook Edition Metadata Package and click the Edit icon.

5. On the Edit Data Security page, click the Conditions tab.

6. Select the Outlook Package for Sales Representatives and click the Edit icon.



6

7. Change the SQL Predicate and enter the package name Default IBM Notes client deployment package forsales representative, and click Save.

8. Click Submit.9. On the Confirmation dialog box, click OK.

The IBM Notes package is now activated in Oracle Sales Cloud for sales representatives. Follow the same steps if you wantto set up IBM Notes for a sales manager.

Configuring the Installer DownloadThis topic explains how to configure the IBM Notes installer download.

To configure the IBM Notes installer download:

1. Log in to Oracle Sales Cloud as a sales administrator.2. Navigate to the Setup and Maintenance work area.3. Search for Manage Administrator Profile Values.4. Click the Go to Task icon.



7

5. On the Manage Administrative Profile Values page, enter ZOE in the Profile Option Code field, and click Search.

6. Change the profile values for three profile codes, as defined in the table below.

Note: After you update each of the profile option, click Save before moving to the next profile option.

Profile Code Profile Value

ZOE_ ENABLE_ DOWNLOAD_LINK_32BIT

No

ZOE_ ENABLE_ DOWNLOAD_LINK_64BIT

No

ZOE_ ENABLE_ NOTES_DOWNLOAD_ LINK_32BIT

Yes

You can now download the installer and start your installation.

Customization of IBM Databases: Points to ConsiderOracle Sales Cloud for IBM Notes customization is deployed on top of the mail database (in majority of cases located onIBM Domino Server) or on the Personal Address Book database (located on client). These databases are both created andupdated using IBM's custom (and even user's custom) templates.

As a part of the Oracle Sales Cloud customization process, the installer patches or modifies some of the existing originaldesign elements in the Personal Address Book and mail Notes databases. To protect those changes in design elements fromunexpected external updates, the Prohibit design refresh or replace to modify check box is selected for such patchedelements. Therefore, the customized elements will not be updated with any design refresh or replace, once the custom



8

template is rolled-out. As a result, the IBM Notes mail database's design elements may become incompatible and causeerrors.

IBM Notes

PAB Database

OSC Customization

IBM Domino Server

Mail Database

Custom Template

OSC Customization

ConsiderationsTo avoid errors, you must follow the steps detailed below. If you have Oracle Sales Cloud product or customization installed,and if you need to apply new custom template on top of the mail database:

1. Perform full synchronization with the Oracle Sales Cloud server to up-sync all your local unsaved data.2. Remove Oracle Sales Cloud customization from IBM Notes.3. Deploy your own template on the IBM Notes mail database.4. Install the Oracle Sales Cloud customization again.

Oracle recommends that you test how your customization works with the Oracle Sales Cloud customization using testdeployment, before rolling out your custom template.


Chapter 3Installing Oracle Sales Cloud for IBM Notes

9

3 Installing Oracle Sales Cloud for IBM Notes

Installing Using Automatic Binary: ProcedureThis topic explains how to install Oracle Sales Cloud for IBM Notes using automatic binary. Installing using automatic binary isthe most preferred method of installing.

The automatic binary deployment involves two steps:

1. Downloading and updating the Installer_config.ini file by the sales administrator. For details, see the topicUpdating the .ini File.

2. Installing the IBM Notes client by the sales representative or the sales manager.

Tip: You can run the Oracle Sales Cloud for IBM Notes installation while IBM Notes is running, but you mustreopen IBM Notes to apply changes made to IBM Notes during installation.

To install Oracle Sales Cloud for IBM Notes through automatic binary deployment:

1. Sign in to Oracle Sales Cloud Applications as a sales representative or a sales manager.2. Click the arrow next to the logged in user name, and click Set Preferences.3. Click CRM for Microsoft Outlook Installer.4. In the CRM for Microsoft Outlook Installer page, click the Start Download link.

The download files are installed on your local machine as a zip file. It contains the following files:

◦ OracleSalesCloudforIBMNotes.ini

For more details on setting up the .ini file, see the topic Updating the .ini File.

◦ OracleSalesCloudforIBMNotes.msi

Ensure that the .ini and the .msi files are in the same folder so that the installer picks up information available inthe .ini file.

5. Click the OracleSalesCloudforIBMNotes.msi file to start the installation.



10

6. Click Next on the Welcome page.

If the OracleSalesCloudforIBMNotes.ini configuration file is unavailable, the following warning appears:



11

7. On the Destination Folder dialog box, select the folder where Oracle Sales Cloud for IBM Notes will be installed.

Tip: The default location for the Oracle Sales Cloud for IBM Notes installation is C:\Users\<username>\AppData\Roaming\Oracle\Oracle Sales Cloud for IBM Notes\. To choose another location, click theChange button. Even if the destination folder is changed, the application can still install some files(\Profile folder) in the current user account's folder so that when an end-user with limited privileges runsNotes, the application can still download the package (configuration) and create/update/delete logsfiles.



12

8. Click Next.



13

9. In the Ready to Install the Program dialog box, click Install.

Note: If information such as user name, password, host and so on were not entered in the .ini file, youwill be prompted to enter these details during the install process.

If the installation is successful, the InstallShield Wizard Completed dialog box appears informing you that OracleSales Cloud for IBM Notes has been installed.



14

10. Click Finish.



15

On your computer, if User Account Control (UAC) is turned on, the following confirm installation dialog box appears.Refer to the Microsoft web site to know more about UAC.

11. Click Yes.

The installation is complete.12. Open the IBM Notes Client.13. In the Oracle Sales Cloud for IBM Notes- Login dialog box, enter the user name and password.

Note: The server and port are already populated since these details were available in the .ini file.



16

14. Click Login.

The package is downloaded and it applies the configuration.15. Once the configuration is complete, set the synchronization filters and start the synchronization.

Installing Manually: ExplainedYou can install Oracle Sales Cloud for IBM Notes from the Command Prompt. Per-user is the default installation type. Onlythe user who is currently logged in can use Oracle Sales Cloud for IBM Notes.

IBM Notes Location SelectionOracle Sales Cloud for IBM Notes prompts the user for customization of the current Location when IBM Notes is opened afterinstalling the Oracle Sales Cloud for IBM Notes add-in. The profile used must meet the system requirements.

Installation Wizard and User Interface LanguageOracle Sales Cloud for IBM Notes installation wizard is localized to English language only. However, Oracle Sales Cloud forIBM Notes user interface is localized to many other languages, such as Spanish, Italian, Polish, Finnish, and Russian. Theuser interface language will be the same as the user interface language of IBM Notes installed on the computer.

The Oracle Sales Cloud for IBM Notes help is available only in English.

Note: English is used if Oracle Sales Cloud for IBM Notes is not localized to the language that your IBM Notes islocalized.



17

Configuring .INI File: ExplainedThis topic explains how to create the .ini file

The default connection parameters can be read from the .ini file if this file is present in the same folder as the main installer.If the .ini file is not found, the installation process can still proceed but you will be prompted with the warning message. Youmust specify the connection parameters manually in the Oracle Sales Cloud for IBM Notes dialog box later.

Note: .ini file settings take priority over command line parameters. Therefore, if you have the .ini file placed in thesame folder as your .msi file, and you try to pass the settings through command line, the settings from .ini file willbe used anyway.

Creating .ini Configuration File.ini file is a simple text file that you can create using Notepad or other similar application. To create new .ini file manually, openNotepad and copy the following content to the Notepad:

[ProductSettings]SALES_CLOUD_HIDE_REMEMBER_PASSWORD=#0SALES_CLOUD_USER_NAME=SALES_REPRESENTATIVESALES_CLOUD_SERVER_HOST= e.g. [POD_Identifier].crm.em2.oraclecloud.com SALES_CLOUD_SERVER_METADATA_SUFFIX=OutlookEditionConnector/OutlookMetadataServiceSALES_CLOUD_SERVER_PORT=#443SALES_CLOUD_SERVER_PROTOCOL=httpsSALES_CLOUD_SERVER_SUFFIX=OutlookEditionConnector/OutlookRequestHandlerService

You can then edit the parameters as required. Once it is done, save the file with .ini extension.

Ensure that the file name is the same as the distributive name. For example, Oracle Sales Cloud for IBM Notes.ini. Whilesaving the text file, ensure that the file extension is .ini and not .ini.txt.

Installing Using Microsoft SMS or SCCM: ExplainedYou can install Oracle Sales Cloud for IBM Notes in silent mode by using Microsoft Systems Management Server (SMS) 2003or Microsoft System Center Configuration Manager (SCCM) 2007.

Note: The per-user installation type is the default and recommended installation.

Per-User InstallationTo perform a per-user installation in SMS or SCCM, create a package as follows:

1. Run setup with user rights.2. Run once for a PC or under each user (depending on your need).3. Run the installer when the user is logged in.4. Include all custom properties in the Windows Installer transform file (.mst file):



18

SALES_CLOUD_SERVER_PROTOCOL, SALES_CLOUD_SERVER_PORT,SALES_CLOUD_HIDE_REMEMBER_PASSWORD, SALES_CLOUD_USER_NAME,SALES_CLOUD_SERVER_HOST, SALES_CLOUD_SERVER_METADATA_SUFFIX,SALES_CLOUD_SERVER_PORT, SALES_CLOUD_SERVER_PROTOCOL, SALES_CLOUD_SERVER_SUFFIX

The following is an example of the command-line that starts the per-user Oracle Sales Cloud for IBM Notes installation withthe basic user interface:

msiexec /I "Disk:\...\OracleSalesCloudforIBMNotes.msi" TRANSFORMS="crmdesktop.mst" /qb!

Installing Silently Using Windows Group Policy: ProcedureYou can install Oracle Sales Cloud for IBM Notes in silent mode using Windows Group Policy. The per-user installation type isthe default installation.

Performing a Per-UserComplete the following steps to perform a per-user installation using Windows Group Policy:

1. Ensure that Microsoft .NET 4.0 is installed on the client computers.2. Create the .mst file with the default connection settings (You can use Orca editor).

See the section Creating MST Using Orca Editor for details.3. Place the .mst file in the same folder as the .msi file.4. Make sure that the folder that stores the installer and the .mst file is accessible on the local network for users for

whom the installation is run.5. Set the Deployment type to Assigned.6. Create separated organization units for different groups of PCs or users. For example, you could create two folders

as follows: X64 and X86.

7. Create an installation package in the Windows Group Policy snap-in in the following branch: User Configuration >Software Settings > Software Installation.

8. Right-click Oracle Sales Cloud for IBM Notes and select the Properties menu item.



19

9. On the Modifications tab, add the path to the .mst file:

Note: Windows installer is disabled for users, but enabled for managed applications.



20

10. Restart the user's computer to install the software using Windows Group Policy.

See the section Client-Side Process for details.

Creating MST File Using Orca EditorFollow these steps to create the MST file using the Orca editor:

1. Install and start the Orca editor.2. Click File, Open, Browse to the MSI, and Open to open the original .msi file.3. Click the Transform menu and select the New Transform menu item to start a new transformation.4. Navigate to the Property table and modify the following values:

◦ Add the SALES_CLOUD_SERVER_HOST property, for example, asn.crm.em2.oraclecloud.com.

◦ Add the SALES_CLOUD_SERVER_PROTOCOL property, for example, https.

◦ Add the SALES_CLOUD_SERVER_PORT port number, for example, #443.

5. Click the Transform menu and select the Generate Transform item to generate the transform file.6. Specify a name for the transform file, and click Save.

Defining the Client-Side ProcessTo define the process on the client-side:

1. Run the client PC under the domain user credentials once the user PC is rebooted.

Oracle Sales Cloud installation runs in silent mode.2. Open the Microsoft Registry and check the parameters specified in the .mst file.3. Start IBM Notes.



21

The First Run Assistant wizard appears and prompts you to configure the general parameters of Oracle Sales Cloudfor IBM Notes, such as to specify filters and to schedule an automatic synchronization.

Installing from Windows Command Prompt: ProcedureOracle Sales Cloud for IBM Notes supports silent installation, which is an unattended installation without user interaction.

When you start the installation in silent mode, use the following parameters:

Parameters Description

/i

Installs or configures a product.

/qn

Displays no user interface during the installation, upgrade, or un-installation process.

/l*v C:\log.txt

Records installation in the log.txt file located at C:\. You can change the file name and path ifrequired.

New InstallationTo start the silent installation in per-user mode, use the following command to run the setup:

msiexec /i "Disk:\...\OracleSalesCloudforIBMNotes.msi" SALES_CLOUD_SERVER_HOST="crm-XXX.oracleoutsourcing.com" ALLUSERS="" SALES_CLOUD_SERVER_PROTOCOL="https" SALES_CLOUD_SERVER_PORT="#443" /qn

Minor UpgradeTo start the minor upgrade in per-user mode, use the following command to run the setup:

msiexec /i "Disk:\...\OracleSalesCloudforIBMNotes.msi" REINSTALL=ALL REINSTALLMODE=vomus /qn

Major UpgradeTo start the major upgrade in per-user mode, use the following command to run the setup:

msiexec /i "Disk:\...\OracleSalesCloudforIBMNotes.msi" /qn

Installing Server Certificate: ProcedureInstalling server certificate is optional. In an elevated security environment where you need a secure certificate-basedauthentication, you might choose to install it.

Note: By default, Oracle Sales Cloud for IBM Notes installs without secure certificate-based authentication.



22

If you have installed Oracle Sales Cloud for IBM Notes with a setting of certificate = #1, the First Run Assistant (login window)will fail unless a valid Oracle Sales Cloud Public Certificate is installed. If you choose to install the certificate, you can only do itthrough command prompt.

1. Access the End Point URL for the IBM Notes Request Handler WSDL. For example: http://<host>:<port>/OutlookEditionConnector/OutlookRequestHandlerService?WSDL.

2. Locate the text between the section tagged <dsig:X509Certificate> and </dsig:X509Certificate>.3. Copy this text to a file named certificate.cer.4. Install the Oracle Sales Cloud Public Certificate to the Personal and Trust Root Certification Authorities certificate

store on your computer.

Note: If a version of the certificate already exists on your computer, you must first uninstall it. Searchin the Personal and Trusted Root Certification Authorities certificate store and delete the certificatesissued to service.

In a SAAS environment, the <host> should be crm-<host>. For example, http://crm-<host>:<port>/OutlookEditionConnector/OutlookRequestHandlerService?WSDL.

Can I use Oracle Sales Cloud for IBM Notes over the Citrixserver?Oracle Sales Cloud for IBM Notes is not certified for use with Citrix.

Citrix Technical Support is responsible for any Oracle Sales Cloud for IBM Notes issues resulting from using Oracle SalesCloud for IBM Notes over Citrix. If Oracle Technical Support suspects that the use of Citrix is contributing to unexpectedbehavior, they may request that the behavior be reproduced in an environment without the Citrix server (usually a standarddesktop client without Citrix running) to further isolate the behavior. If the behavior is not reproducible in this manner,customers may be advised to contact Citrix Systems to assist in resolving the problem.

Oracle does not provide any support if any issues arise from use of Oracle Sales Cloud for IBM Notes on Citrix or TerminalServices environment.


Chapter 4Administering Deployment Settings

23

4 Administering Deployment Settings

Updating the .ini FileYou can set up the .ini file with default parameters required to install Oracle Sales Cloud for IBM Notes. During installation, theclient reads values for some of the fields from the .ini file.

To update the .ini file:

1. Sign in to Oracle Sales Cloud Applications as a Sales Administrator.2. Navigate to the Setup and Maintenance work area.3. Search for the Manage IBM Notes Server Configuration Files task.4. Click the Go to Task icon.5. In the Manage IBM Notes Server Configuration Files page, select the Installer_config.ini row.6. Click the Export button and save the file locally.7. Open the .ini file as a notepad, and at the minimum fill in the following details:

Parameter Default Value Description

SALES_ CLOUD_ HIDE_ REMEMBER_PASSWORD

#0

Show/hide Save Password check box inthe Login dialog. #0 - show check box #1 -hide check box Please use # before actualnumber.

SALES_ CLOUD_ SERVER_HOST

Sales Cloud server host name.

SALES_ CLOUD_ SERVER_ METADATA_SUFFIX

outlookEditionConnector/OutlookMetadataService

Typically does not change

SALES_ CLOUD_ SERVER_PORT

#443

Server port name. Please use # beforeactual number.

SALES_ CLOUD_ SERVER_ PROTOCOL

https

Specify the protocol to use: http or https

SALES_ CLOUD_ SERVER_SUFFIX

outlookEditionConnector/OutlookRequestHandlerService

SALES_ CLOUD_ USER_NAME

User name for the login dialog, e,g. SALES_REPRESENTATIVE

SALES_ CLOUD_ USE_ CERTIFICATE

#0

#0 - do not use server certificate This is the default and recommendedoption. #1 - use server certificate. Please use #before actual number.

SALES_CLOUD_ APPCONFIG_URL

"https://www. salescloud2. com/connector.config"

Is used for STS deployments to specify theURL (enclosed with double quotes) for theconnector. config file location.



24

Parameter Default Value Description

SALES_ CLOUD_ SUPPRESS_SYNC_ISSUES

#1

#1 - suppresses notification about syncissues #0 - enables notification about sync issues

SALES_ CLOUD_ CRASHDUMP_ ENABLE

#1

#1 - Automatically create crash dumps #0 - Disabled

SALES_ CLOUD_ DISABLE_ LIVE_UPDATE

#0

#0 - LiveUpdate feature enabled #1 - Disabled

8. Once you complete updating the .ini file, navigate to the Manage IBM Notes Server Configuration Files page again toupload your file.

9. Click the Edit icon.10. In the Edit IBM Server Configuration File window, click Browse and upload the updated .ini file.

Login Parameters: ExplainedThis topic covers deploying login parameters for Oracle Sales Cloud for IBM Notes.

If you want to specify connection parameters and the Oracle Sales Cloud Server URL to which the synchronization engineconnects, you can pass them to msiexec as command-line parameters when installing the product. In this case, the .MST fileis not needed.

The following command-line parameters can be passed to msiexec:

SALES_CLOUD_SERVER_PROTOCOL= "HTTP" | "HTTPS"SALES_CLOUD_SERVER_HOST=<host_name_or_address>SALES_CLOUD_SERVER_PORT=<server_port>SALES_CLOUD_SERVER_SUFFIX=<request_handler_path>SALES_CLOUD_METADATA_SUFFIX=<metadata_service_path>SALES_CLOUD_USE_CERTIFICATE= #0 | #1SALES_CLOUD_USER_NAME = <username > (available since binary version 3.05.06 and higher)SALES_CLOUD_HIDE_REMEMBER_PASSWORD = #0|#1 (available since binary 3.05.06 and higher)SALES_CLOUD_APPCONFIG_URL= "<full url>" (available since binary 3.05.04 and higher)

Parameter Description

SALES_ CLOUD_ SERVER_PROTOCOL

Defines whether the client should use a secure connection protocol (HTTPS) or not (HTTP), withHTTP being the default value.

SALES_ CLOUD_ SERVER_HOST

The computer name or IP address of the target server. This parameter is empty by default.

SALES_ CLOUD_ SERVER_PORT

The port number. By default, port 80 is used.

SALES_ CLOUD_ SERVER_SUFFIX

The path to the Sales Cloud for IBM Notes request handler, which is outlookEditionConnector/OutlookRequestHandlerService by default.



25


SALES_ CLOUD_ SERVER_METADATA_ SUFFIX

The path to the Oracle Sales Cloud for IBM Notes request handler, which isoutlookEditionConnector/ OutlookMetadataService by default.

1 for the SALES_CLOUD _ USE_CERTIFICATE parameter

Enables the Use server certificate option, which is disabled by default.

SALES_ CLOUD_ USER_NAME

Used to specify the user account to be shown in the Login dialog box.

1 for the SALES_ CLOUD_ HIDE_REMEMBER_ PASSWORD parameter

Hides the Save password check box in the Login dialog box.

SALES_CLOUD_ APPCONFIG_URL

Used for STS deployments to specify the URL (enclosed with double quotes) for the connector.config file location. Example URL: https: / / fusovmdmz40-crm-extus oracle. com/ IBMNotesEdition/AppConfigServlet

When installing application versions 3.05.06 or higher, the "#" character must be used in the SALES_CLOUD_SERVER_PORTand SALES_CLOUD _USE_CERTIFICATE parameters. Use the following example to perform an interactive installation:

msiexec /i "Disk:\...\OracleSalesCloudforIBMNotes.msi" SALES CLOUD_SERVER_HOST="crm-XXX.oracleoutsourcing.com"

SALES_CLOUD_SERVER_PROTOCOL="https" SALES CLOUD_SERVER_PORT="#443"

Use this example to perform a silent installation:

msiexec /i "Disk:\...\OracleSalesCloudforIBMNotes.msi" SALES CLOUD_SERVER_HOST="crm-XXX.oracleoutsourcing.com"

SALES_CLOUD_SERVER_PROTOCOL="https" SALES CLOUD_SERVER_PORT="#443" /qn

Note: The values of command-line parameters override the Windows registry values and program defaults. Forexample, the value of the SALES CLOUD_SERVER_PROTOCOL parameter will override the Connector:Protocolentry in the Windows registry, and this value will be used in the Login dialog box.



26


Chapter 5Upgrading Oracle Sales Cloud for IBM Notes Binary

27

5 Upgrading Oracle Sales Cloud for IBM NotesBinary

Upgrading Binary Manually: ExplainedThis topic describes the manual upgrade steps for Oracle Sales Cloud for IBM Notes binary files.

There are two types of Oracle Sales Cloud for IBM Notes binary files upgrades:

• Minor upgrade: A minor upgrade is an update that contains small changes and does not require installing theproduct again. Minor updates can be installed on top of the current version. For example, an upgrade from version3.06.14 to 3.06.15 is a minor upgrade.

• Major upgrade: A major upgrade is a comprehensive upgrade that removes a previous version of Oracle Sales Cloudfor IBM Notes and installs a new version. The major upgrade is usually required when there are significant changes inthe product or when there are changes in the way CRM data is stored in MS IBM Notes (due to Platform upgrade).For example, an upgrade from version 3.06.02 to 3.06.15 is a major upgrade.

Performing a Minor UpgradeWhile performing a minor upgrade, consider the following:

• A minor upgrade is supported only within the same major version of Oracle Sales Cloud for IBM Notes for MS IBMNotes. For example, you can perform a minor upgrade from Oracle Sales Cloud for IBM Notes 3.06.14 to SalesCloud CRM 3.06.15, but you cannot perform a minor upgrade from Oracle Sales Cloud for IBM Notes 3.06.04 toOracle Sales Cloud for IBM Notes 3.06.14.

• A minor upgrade does not change any user data that was not synchronized with the server.

• Upgrade should be performed with closed IBN Notes.

To perform a minor upgrade, run the following command from the command prompt:

msiexec /I "Disk:\...\OracleSalesCloudforIBMNotes.msi" REINSTALL=ALL REINSTALLMODE=vomus /L*v C:\upgradelog.txt

Performing a Major UpgradeWhile performing a major upgrade, consider the following:

• Since the product changes are significant, you cannot perform a major upgrade from Oracle Sales Cloud for IBMNotes 3.05.xx to Oracle Sales Cloud for IBM Notes 3.06.xx without first uninstalling version 3.05.xx.

• Upgrade should be performed with closed IBN Notes.



28

• During the major upgrade, the following messages appear:

To perform a major version update, for example, from version 3.05.xx to version 3.06.xx:

1. Ensure that you have performed full synchronization and backed up your data.2. Uninstall Oracle Sales Cloud for IBM Notes 3.05.xx.3. Install Oracle Sales Cloud for IBM Notes 3.06.xx.

Customization Package Update Compatibility: ExplainedThis topic explains how to perform a customization package update, and covers possible package update scenarios.



29

Compatibility between Particular Oracle Sales Cloud for IBM Notes VersionsIn most cases, each product build consists of two components:

• Binary Installer in MSI format

• Customization Package in ZIP format

Note: Compatibility check between the MSI installer and the customization package is performed only in thesynchronization phase. Compatibility check is not performed, for example, after a minor upgrade.

Hotfix (patch bundle) releases may theoretically require only customization package updates, and sometimes they mightrequire the updates of binary files. If binary is updated and the package update is not required, then the package-binarycompatibility section of the package should be updated. For information on how to update the compatibility rules in thepackage, see the section Info.xml Overview.

When planning an upgrade strategy for Oracle Sales Cloud for IBM Notes, you must consider the following compatibilityaspects:

• Compatibility between two subsequent versions, which dictates the upgrade strategy of binary files, that is if eachparticular upgrade is conducted as a major or minor.

• Compatibility between two subsequent versions: This dictates the upgrade strategy of binary files.

This compatibility aspect dictates whether each particular upgrade is conducted as a major or minor.

• Compatibility between customization package and binary files: This dictates whether the updated customizationpackage can be used with the binary files currently installed. Each time a new package is uploaded to the server anddownloaded as a part of the next synchronization process to the client, special logic is used to distinguish betweenpossible compatibility scenarios and to execute all the required actions. Scenarios in this chapter explain this further.

The <products\> section under Info.xml Overview, along with the preferred_product attribute defines product andpackage compatibility.

• Compatibility between data schemas of two subsequent customization packages:

This type of compatibility dictates whether:

• Synchronization using the previous package will be allowed even if the updated package is not compatible with thecurrent binary files. If synchronization using the outdated package (even when the updated package is available onthe server) is still allowed, then there were no data structure changes on the server between the package updates.

• Full data synchronization is required when a new configuration package is installed on the client.

Common Types of Package-Product CompatibilityWhenever a package update is delivered from the server to the client, special logic is used on the client-side to execute oneof the pre-defined compatibility scenarios.

The scenario selection is based on:

• The information in the compatibility section of info.xml in a new package.

• The comparison of hash values of the fusion_ basic_mapping.xml files from the package that is currently installedand the package that has been downloaded. The following items contribute to a change in the hash value of thefusion_basic_mapping.xml file:

• A list of defined fields across all defined types.



30

• The version attribute of each field.

An update of the version of any field in the fusion_basic_mapping.xml is sufficient to trigger full synchronization.

Following are the main scenarios that arise from possible package-product compatibility combinations:

Scenario Package-product Compatibility

Scenario 1

New package is compatible with current binary files, but full repeat synchronization is required.

Scenario 2

New package is not compatible with current binary files, but synchronization is still allowed.

Scenario 3

New package is not compatible with current binary files and synchronization is not allowed.

Oracle Sales Cloud for IBM Notes package upgrade triggers a repeat structure installation every time there is an upgrade.

Note: The system integrator teams or other users who perform customization are solely responsible forproviding correct information in the info.xml file regarding the compatibility between the vanilla product versions.

Refer to the Info.xml Overview section and the scenarios to understand how to define compatibility information, depending onyour upgrade scenario.

Info.xml OverviewThe Info.xml file must be a part of the customization package. This file defines the package version and provides informationabout compatibility between the package it belongs to and the number of possible product versions it may be applied to.

Following is an example of the Info.xml file:

<package_info> <product> <name>Oracle Sales Cloud for IBM Notes</name> <version>3.06.15.00</version> </product> <compatibility preferred_product="3.06.15.00"> <products>3.06.15.00-3.06.15.99</products> <schemas>3.06.15.00-3.06.15.99</schemas> </compatibility></package_info>

The following table provides a description of sections and attributes:


<Product> section

• Name: Name of the product• Version: version of the release the package belongs to.

<Compatibility> section

• Preferred_product: version of the product that is preferred for this package. This attributeis actually a concatenated part of the resource label displayed to the user in the notificationarea when the current product version appears to be incompatible with the package. Theattribute format is xx.xx.xx.xx.

• Products: this section defines a range of product versions that the package is compatiblewith. As long as the version of the installed product is not within the specified range, the newpackage is never applied, and the user is prompted to upgrade the product. The attributeformat is xx.xx.xx.xx-yy.yy.yy.yy; zz.zz.zz.zz-tt.tt.tt.tt.



31


• Schemas: this section defines a range of packages, which can co-exist with the schemadefined in the new package. As long as the version of the previously deployed package iswithin this range, the product can still synchronize using the previous package, even if theproduct is no longer compatible. The attribute format is xx.xx.xx.xx-yy.yy.yy.yy;zz.zz.zz.zz-tt.tt.tt.tt.

Package-Product Compatibility Scenarios: ExplainedThis topic explains the different scenarios of product-package compatibility for Oracle Sales Cloud for IBM Notes.

New Package is Compatible, Full Resynchronization is RequiredThe Info.xml file of the new package identifies the current product version and the new package as compatible.

The infrastructure prerequisites for this scenario include:

• The user has Build 1 (B1) and Package 1 (P1) deployed on the PC.

• There is a new Build 2 (B2) and Package 2 (P2) available.

• Package P2 defines B1 as compatible.

• Package P2 defines package P1 as compatible with the new data schema.

• Package P2 is deployed to the server.

The Info.xml of Package P2 Configuration example for this scenario is:

P1, B1 = 3.06.14.00; P2, B2 = 3.06.15.00.

<package_info> <product> <name>Oracle Sales Cloud CRM for IBMNotes</name> <version>3.06.15.00</version> </product> <compatibility preferred_product="3.06.15.00"> <products>3.06.14.00-3.06.14.99;3.06.15.00-3.06.15.99</products> <schemas>3.06.14.00-3.06.14.99;3.06.15.00-3.06.15.99</schemas> </compatibility></package_info>

The steps in this scenario are detailed below:

1. Start synchronization.



32

When the synchronization completes, a dialog box appears requesting you to reinstall data structure.

2. Click Yes.

The following notification appears:

3. Close the notification.

Another notification appears that informs the user that the package has been downloaded and installed successfully.

You can now perform the synchronization using a new package until the installation of new binary files is enforced.



33

New Package is Not Compatible, Synchronization is Still AllowedThis scenario represents a transient state, when users and IT can update their binary files while being able to performfull synchronization. The Info.xml file of the new package identifies the current product version and the new package asincompatible.



• There is a new Build 2 (B2) and Package 2 (P2) available to the IT.

• Package P2 defines B1 as incompatible.

• Package P2 defines package P1 as compatible.

• P2 is deployed to the server.


P1, B1 = 3.06.14.00; P2, B2 = 3.06.15.00.

<package_info> <product> <name>Oracle Sales Cloud CRM for IBMNotes</name> <version>3.06.15.00</version> </product> <compatibility preferred_product="3.06.15.00"> <products>3.06.15.00-3.06.15.99</products> <schemas>3.06.14.00-3.06.14.99;3.06.15.00-3.06.15.99</schemas> </compatibility></package_info>


Start the synchronization. When the synchronization completes successfully, the following notification appears:

New Package is not Compatible, Synchronization is Not AllowedThis scenario typically takes place when significant architectural changes are introduced between two subsequent productversions and/or a data schema change occurs. This usually occurs only during a major upgrade.

This scenario has two criteria:

• The Info.xml file of the new package identifies the current product version and the new package as incompatible.



34

• The Info.xml file of the new package identifies exiting package as incompatible with the data schema defined in anew package.



• There is a new Build 2 (B2) and Package 2 (P2) available to the IT.

• Package P2 defines B1 as incompatible.

• Package P2 defines P1 as incompatible.

• P2 is deployed to the server.


P1, B1 = 3.06.14.00; P2, B2 = 3.06.15.00.

<package_info> <product> <name>Oracle Sales Cloud CRM for IBMNotes</name> <version>3.06.15.00</version> </product> <compatibility preferred_product="3.06.15.00"> <products>3.06.15.00-3.06.15.99</products> <schemas>3.06.15.00-3.06.15.99</schemas> </compatibility></package_info>


You start the synchronization. The synchronization stops and the following notification appears:


Chapter 6Configuring Clients to use STS Authentication (SSO)

35

6 Configuring Clients to use STSAuthentication (SSO)

Configuring IBM Notes to use STS Authentication:PrerequisitesBefore configuring IBM Notes to use Security Token Service (STS) authentication, your Oracle Sales Cloud environment mustbe set up to support STS authentication.

Oracle Sales Cloud for IBM Notes supports the STS authentication mode. If configured to use STS authentication, OracleSales Cloud for IBM Notes uses a special configuration file called connector.config. This file stores login information,authentication endpoint URLs, and other required information. The connector.config file is provided by a Sales Cloud CRMserver.

Obtaining the Configuration File: ExplainedOracle Sales Cloud for IBM Notes uses a configuration file called connector.config when it is configured to support SecurityToken Service (STS) authentication. This topic explains how to obtain the connector.config file.

To obtain the connector.config file:

1. Sign in to Oracle Sales Cloud as a sales administrator.2. Navigate to the Setup and Maintenance work area.3. Search for the task Manage Outlook Server Configuration Files, and click the Go to Task icon.

The Manage Outlook Server Configuration Files page appears.

4. Select the App.configuration file, and click the Export button.5. Save the file on your computer.

To upload a new version of the App.configuration file, click the Edit icon on the Manage Outlook Server Configuration Filespage, and click the Browse button to select the file to upload.



36

Installing in STS Authentication Mode: ExplainedTo install Oracle Sales Cloud for IBM Notes with Security Token Service (STS) authentication mode, you must pass theSALES_CLOUD_APPCONFIG_URL parameter to the msiexec command, where SALES_CLOUD_APPCONFIG_URL is the URL tothe remote connector.config file. For example, msiexec /i "Disk:\...\Oracle Sales Cloud CRM for IBMNotes.msi"SALES_CLOUD_APPCONFIG_URL=[URL path to the remote config file]

During installation, two keys are created in the system registry HKEY_CURRENT_USER\Software\Oracle\Oracle Sales Cloudfor IBM Notes\Connector:

• UseSTSMode: The possible values of the key are:

◦ 0: without STS

◦ 1: local config file

◦ 2: remote config file

◦ 3: automatic choice

• AppConfigUrl: Path, to the remote configuration file, specified in theCommand Prompt during installation.

After you complete installation with the STS authorization mode enabled, the Oracle Sales Cloud for IBM Notes - Login dialogbox appears.

Enter your login credentials and login to Oracle Sales Cloud for IBM Notes.



37

Configuring STS Authentication Configuration File for IBMNotes: ExplainedThis topic explains the configuration file structure and provides steps to configure the Connector.Config file.

Configuration File Structure and General SettingsThis section explains the structure of the configuration file and the general settings.

The connector.config file has the following structure:

<?xml version="1.0" encoding="utf-8" ?><configuration>

<configSections> <sectionGroup name="WebServiceConfiguration"> <section allowDefinition="Everywhere" allowLocation="true" name="WebServiceProfiles" type="FusionWebServices.CustomAppConfig.ProfileSection, SalesCloudWebServices, Version=0.0.0.0, Culture=neutral, PublicKeyToken=723e55cb011efbe4"/> <section allowDefinition="Everywhere" allowLocation="true" name="TockenCaching" type="FusionWebServices.CustomAppConfig.TokenCacheSection, SalesCloudWebServices, Version=0.0.0.0, Culture=neutral, PublicKeyToken=723e55cb011efbe4"/> </sectionGroup> </configSections>

<system.serviceModel> <behaviors>...</behaviors> <bindings>...</bindings> <client>...</client> </system.serviceModel>

<WebServiceConfiguration> <TockenCaching/> <WebServiceProfiles> <Profile>...</Profile> <Profile>...</Profile> ... </WebServiceProfiles> </WebServiceConfiguration>

</configuration>

The following table describes the connector.config parameters.


<ConfigSections>

Default ICRM part that does not change as a rule.

<behaviors>

A set of endpoint behavior. This section specifies which service certificates to use.

<bindings>

A set of bindings that describe the method (and corresponding properties) Oracle Sales Cloud forIBM Notes should use to connect to the service.



38


<client>

A set of endpoints that contain URLs of services, binding names, and behavior names.

<TockenCaching>

Security token caching settings. Caching only applies to STS configurations.

<WebServiceProfiles>

A set of Web Service configuration profiles. Describes endpoint names to use as well as thereadable information that is shown in the Credentials dialog box.

For more information on how to configure behaviors, bindings, and other nodes, see the Windows CommunicationFoundation Configuration Schema topic in MSDN.

Configuring Connector.ConfigThis section explains the steps to configure the connector.config file.

To configure connector.config for deployments with STS authentication:

1. Configure the Web Services profiles section.2. Configure the Endpoints section.3. Configure Bindings and Binding Behaviors.4. Configure Security token caching (Optional).

Note: For details of configuration elements, see http://msdn.microsoft.com/en-us/library/ms731354.aspx.

Configuring Web Service ProfilesA set of Web Service Profiles is defined within <WebServiceProfiles> under <Profile> nodes. The profiles will be displayed inthe Credentials dialog box in the same order as declared here.

The Profile node structure is the same as shown in the example below, where the text given inside the CDATA [] tagrepresents the description shown to the end user in the Login dialog box:

<WebServiceProfiles> <Profile Id="HttpProfile" Caption="Profile 1 (Http)" RequestClientEndpointName="DirectSales CloudRequestEndpoint" MetadataClientEndpointName="DirectSales CloudMetadataEndpoint" ManagementClientEndpointName="FusionOverSTSManagementEndpoint" CredentialsType="UserName"> <Description> <![CDATA[Profile details: Sales Cloud Web Service URL: http://slcad665.us.oracle.com Sales Cloud Web Service Security: User Name]] > </Description> </Profile>

<Profile Id="HttpsProfile" Caption="Profile 2 (Https)" RequestClientEndpointName="DirectSales CloudRequestEndpointSSL" MetadataClientEndpointName="DirectSales CloudMetadataEndpointSSL" CredentialsType="UserName"> <Description> <![CDATA[Profile details: Sales Cloud Web Service URL: https://crm2-v1r1-efops-hadep-crm-ext.us.oracle.com Sales Cloud Web Service Security: User Name]] > </Description> </Profile>



39

<Profile Id="STSProfile" Caption="Profile 3 (STS)" RequestClientEndpointName="Sales CloudOverSTSRequestEndpoint" MetadataClientEndpointName="Sales CloudOverSTSMetadataEndpoint" CredentialsType="UserName"> <Description> <![CDATA[Profile details: Sales Cloud Web Service URL: https://slcac778.us.oracle.com Sales Cloud Web Service Security: Security token STS configuration: Bearer Key STS URL: http://slc02qhd.us.oracle.com STS Security: User Name / Certificate]] > </Description> </Profile></WebServiceProfiles>

In the Profile section, you will find the following attributes:

Note: All the settings listed in the table are required.

Attributes Description

Id

Unique internal profile name. This name is used to store the user-selected profile.

Caption

Text shown in the Select Web Service Configuration Profile combo box in the Credentials dialogbox.

RequestClientEndpointName

A name of an endpoint out of a set of declared ones in the <client> section to use for RequestClientin the current profile.

MetadataClientEndpointName

A name of an endpoint out of a set of declared ones in the <client> section to use forMetadataClient in the current profile.

CredentialsType

A type of credentials used with profile endpoints. The allowed values are:• UserName: Prompts the user to enter a user name and a password manually in the

Credentials dialog box.• NTML: User credentials are taken from the domain, and the user is asked to authenticate (if

the user is not logged on).

<Description>

A multi-line description of the current Web Service configuration. The entire value must be wrappedinto <![CDATA[. ..]] > as shown in the example above. This description is displayed in the Profiledetails area.

Configuring the Endpoint SectionTypically, you will need to add or update endpoint information for STS only.

A sample configuration is provided below. More details about parameters and their configuration can be found at http://msdn.microsoft.com/en-us/library/ms731762.aspx.

<client>  <endpoint name="Sales CloudOverSTSRequestEndpoint" address="http://<host>:<port>/OutlookEditionConnector/OutlookRequestHandlerService" binding="customBinding" bindingConfiguration="Sales CloudOverSTSBinding" contract="OutlookRequestHandlerService.OutlookRequestHandlerService"> </endpoint>





40

<endpoint name="Sales CloudOverSTSMetadataEndpoint" address="http://<host>:<port>/OutlookEditionConnector/IBM NotesMetadataService" binding="customBinding" bindingConfiguration="Sales CloudOverSTSBinding" contract="IBM NotesMetadataService.IBM NotesMetadataService"> </endpoint>

 <endpoint name="FusionOverSTSManagementEndpoint" address="http://<host>:<port>/OutlookEditionConnector/ClientManagementService" binding="customBinding" bindingConfiguration="FusionOverSTSBinding"contract="ClientManagementService.ClientManagementService" behaviorConfiguration="secureBehavior_to_slc02qhd_STS"> </endpoint>

</client>

Configuring Bindings and Binding BehaviorThis section covers bindings and binding behavior.

Bindings are not editable in most scenarios. Retain what is available by default:

<bindings> <customBinding> <binding name="Sales CloudOverSTSBinding"> <security defaultAlgorithmSuite="Basic128" authenticationMode="IssuedTokenOverTransport" requireDerivedKeys="false" securityHeaderLayout="Lax" includeTimestamp="true" keyEntropyMode="CombinedEntropy" messageSecurityVersion="WSSecurity11WSTrust13WSSecureConversation13WSSecurityPolicy12BasicSecurityProfile10"> <issuedTokenParameters keyType="BearerKey" tokenType="http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1"> <additionalRequestParameters> <trust:SecondaryParameters xmlns:trust="http://docs.oasis-open.org/ws-sx/ws-trust/200512"> <ns6:KeySize xmlns:ns6="http://docs.oasis-open.org/ws-sx/ws-trust/200512">256</ns6:KeySize> <ns7:KeyType xmlns:ns7="http://docs.oasis-open.org/ws-sx/ws-trust/200512">http://docs.oasis-open.org/ws-sx/ws-trust/200512/Bearer</ns7:KeyType> <ns8:TokenType xmlns:ns8="http://docs.oasis-open.org/ws-sx/ws-trust/200512">http://docs.oasis-open.org/wss/oasis-wss-saml-token-profile-1.1#SAMLV1.1</ns8:TokenType> </trust:SecondaryParameters> </additionalRequestParameters>  <issuer address="https://slc01nys.us.oracle.com/adfs/services/trust/13/usernamemixed" binding="customBinding" bindingConfiguration="STSBinding"> </issuer> </issuedTokenParameters> <localClientSettings cacheCookies="true" detectReplays="true" replayCacheSize="900000" maxClockSkew="00:05:00" maxCookieCachingTime="Infinite" replayWindow="00:05:00" sessionKeyRenewalInterval="10:00:00" sessionKeyRolloverInterval="00:05:00" reconnectTransportOnFailure="true" timestampValidityDuration="00:05:00" cookieRenewalThresholdPercentage="60"/> <localServiceSettings detectReplays="true" issuedCookieLifetime="10:00:00" maxStatefulNegotiations="128" replayCacheSize="900000" maxClockSkew="00:05:00" negotiationTimeout="00:01:00" replayWindow="00:05:00" inactivityTimeout="00:02:00" sessionKeyRenewalInterval="15:00:00" sessionKeyRolloverInterval="00:05:00" reconnectTransportOnFailure="true" maxPendingSessions="128" maxCachedCookies="1000" timestampValidityDuration="00:05:00"/> <secureConversationBootstrap/> </security> <mtomMessageEncoding maxReadPoolSize="64" maxWritePoolSize="16" messageVersion="Soap11" maxBufferSize="5048576" writeEncoding="utf-8"> <readerQuotas maxDepth="65536000" maxStringContentLength="65536000" maxArrayLength="65536000" maxBytesPerRead="65536000" maxNameTableCharCount="65536000"/> </mtomMessageEncoding> <httpsTransport manualAddressing="false" maxBufferPoolSize="65536000" maxReceivedMessageSize="65536000" allowCookies="false" authenticationScheme="Anonymous" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" keepAliveEnabled="true" maxBufferSize="65536000" proxyAuthenticationScheme="Anonymous" realm="" transferMode="Buffered" unsafeConnectionNtlmAuthentication="false" useDefaultWebProxy="true"/>



41

</binding>

<binding name="STSBinding"> <security defaultAlgorithmSuite="Basic128" authenticationMode="UserNameOverTransport" requireDerivedKeys="false" securityHeaderLayout="Lax" includeTimestamp="true" messageProtectionOrder="SignBeforeEncrypt" requireSignatureConfirmation="true" keyEntropyMode="CombinedEntropy" messageSecurityVersion="WSSecurity11WSTrust13WSSecureConversation13WSSecurityPolicy12BasicSecurityProfile10"> <secureConversationBootstrap/> </security> <textMessageEncoding maxReadPoolSize="64" maxWritePoolSize="16" messageVersion="Soap12WSAddressing10" writeEncoding="utf-8"> <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384"/> </textMessageEncoding> <httpsTransport manualAddressing="false" maxBufferPoolSize="524288" maxReceivedMessageSize="65536" allowCookies="false" authenticationScheme="Anonymous" bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard" keepAliveEnabled="true" maxBufferSize="65536" proxyAuthenticationScheme="Anonymous" realm="" transferMode="Buffered" unsafeConnectionNtlmAuthentication="false" useDefaultWebProxy="true"/> </binding> </customBinding></bindings>

Binding Behavior should be configured for each corresponding Web Service type.

Note: Behavior is not used for STS authentication unless a customer has configured STS to use certificate-based authentication.

<behaviors> <endpointBehaviors> <behavior name="DirectSales CloudBehavior"> <clientCredentials> <serviceCertificate> <defaultCertificate x509FindType="FindByThumbprint" storeLocation="CurrentUser" storeName="My" findValue="df 38 f5 b3 d2 80 ae 7d ab ec da 5d bf 44 d3 2a 00 48 94 c7"/> </serviceCertificate> </clientCredentials> </behavior>

<behavior name="DirectSales CloudBehaviorSSL"> <clientCredentials> <serviceCertificate> <defaultCertificate x509FindType="FindByThumbprint" storeLocation="CurrentUser" storeName="My" findValue="e1 de 77 18 be 27 8b 2e fb 8b a2 b3 2f 8d a9 e2 80 1e 03 14"/> </serviceCertificate> </clientCredentials> </behavior>

<behavior name="secureBehavior_to_slc02qhd_STS"> <clientCredentials> <serviceCertificate> <defaultCertificate findValue="OWSM slc02qhd.us.oracle.com" storeLocation="CurrentUser" storeName="My" x509FindType="FindBySubjectName"/> </serviceCertificate> </clientCredentials> </behavior>

</endpointBehaviors></behaviors>



42

Configuring Security Token Caching (Optional)The <TockenCaching> section configures the security token caching in Federated Security scenarios.

This is a required tag. In cases no STS authentication is used in binding, these settings have no effect on the functionality.The following attributes are valid for the <TockenCaching> tag:

Attributes Description

EnableCaching

Enables/ disables token caching. Supported values are True/False.

ExpirationPolicy

Describes token expiration policy that allows Oracle Sales Cloud for IBM Notes to determinewhether to use a cached token or, if it has expired, request a new one. This decision is based on theissue/expiration date. This is used in conjunction with the Time attribute. Supported values are:

• NSecondsAfterTokenIssueTime: Defines a policy to request a new token when a specifiedamount of time passes after the token issue date.

• NSecondsBeforeTokenExpirationTime: Defines a policy to request a new token if the amountof time left before the token expiration date is less than specified.

Time

The amount of time in seconds to use for the expiration policy defined in the ExpirationPolicyattribute.

Log

A file name of a token caching log file. If an empty or invalid value is specified, logging is disabled.System environment variables are allowed. None of the above attributes are mandatory, but the tag itself is mandatory. Here is an example ofhow to configure the <TockenCaching> section: <TockenCaching EnableCaching= "True" ExpirationPolicy= "NSecondsAfterTokenIssueTime"Time="10"/>

Related Topics

• Configuration Elements on MSDN

• Windows Communication Foundation Configuration Schema on MSDN

http://msdn.microsoft.com/en-us/library/ms731354.aspx

https://msdn.microsoft.com/en-us/library/ms731734.aspx


Chapter 7Uninstalling Oracle Sales Cloud for IBM Notes

43

7 Uninstalling Oracle Sales Cloud for IBMNotes

Uninstalling using Windows Control Panel: ProcedureThis topic explains how to uninstall Oracle Sales Cloud for IBM Notes using the Windows Control Panel.

To uninstall from the Windows Control Panel:

1. Open Start, Control Panel, and Programs and Features.2. Select Oracle Sales Cloud for IBM Notes in the list and click Uninstall.

After the un-installation, all Oracle Sales Cloud for IBM Notes folders along with the local CRM data are removed.This completes the un-installation.

Uninstalling using InstallShield Wizard: ProcedureYou can uninstall Oracle Sales Cloud for IBM Notes using the InstallShield Wizard by running the sameOracleSalesCloudforIBMNotes.msi file that was used for the installation.

To uninstall using InstallShield Wizard:

1. Run OracleSalesCloudforIBMNotes.msi.2. On the Welcome page of the InstallShield Wizard, click Next.3. Select the Remove option and click Next.4. Click the Remove button to start the un-installation.



44

The IBM Notes dialog box appears asking you to enter the password.5. Enter your IBM Notes password.6. When the un-installation completes, click Finish to close the InstallShield Wizard.

Uninstalling using Windows Command Prompt: ProcedureThis topic explains how to uninstall Oracle Sales Cloud for IBM Notes from Windows Command Prompt.

To uninstall from Windows Command Prompt:

1. In the Command Prompt (Start -> Run -> cmd), run the following command:

msiexec /x "Disk:\...\OracleSalesCloudforIBMNotes.msi"

2. Click Yes.3. Click Yes again to start the un-installation.

After the un-installation, all Oracle Sales Cloud for IBM Notes folders along with the local CRM data are removed.

Uninstalling using Microsoft SCCM: ProcedureThis topic describes how to uninstall Oracle Sales Cloud for IBM Notes using Microsoft (MS) SCCM.

Follow these steps to uninstall Oracle Sales Cloud for IBM Notes using MS SCCM:

1. Find an Upgrade Code of Profile.msi.2. Identify computers with Oracle Sales Cloud for IBM Notes Profile installed.3. Collect all Product Codes on the network.4. Uninstall Oracle Sales Cloud for IBM Notes Profile in per-user mode on the computers.

Identifying Computers with Oracle Sales Cloud for IBM Notes Profile InstalledThis section describes how to identify computers with Oracle Sales Cloud for IBM Notes profile installed.



45

To identify computers on which CRMD Profile is installed, use the native SCCM reporting service.

1. Before using this service, enable Software Inventory Client Agent in the Configuration Manager Console:

a. Right-click Software Inventory Client Agent item under the Client Agents node in the System CenterConfiguration Manager, and select Properties from the context menu.

b. In the Software Inventory Client Agent Properties dialog box, choose the Enable software inventory onclients option.

2. Generate native SCCM report with inventoried software titles.

a. Expand the Reporting tree node of the Configuration Manager Console, and select New and then select theReport command from the context menu.

b. In the New Report Wizard, add the report name, choose the Software - Companies and Productscategory, and other required parameters. You can also use SQL parameters for detailed reporting.

c. Click Next to go through the wizard and generate the report.

This report contains the list of all workstations and software installed on these computers. Sort clientcomputers, find computers where Oracle Sales Cloud for IBM Notes is installed, and then move thesecomputers to the separate collection.

Collecting All Product Codes at the NetworkProduct Codes on the client computers may vary as different versions of CRMD Profiles may be installed on thesecomputers.

When UpgradeCode is available, you can get the list of ProductCodes for the products you want to uninstall.

1. Create .vbs script with the following content:

Option ExplicitPublic installer, product, propVal, RelProd, prodFound, arg

For Each arg In Wscript.Arguments set installer = CreateObject("WindowsInstaller.Installer") set propVal = installer.RelatedProducts(arg)

For Each RelProd In propVal For Each product In installer.ProductsEx(RelProd, "", 7) WScript.StdOut.Write product.ProductCode Next NextNext

2. Use the Installer.RelatedProducts property from msi.dll to find Product Codes using Upgrade Codes.

The read-only RelatedProducts property returns a StringList object showing the set of all products installed oradvertised for the current user and machine with a specified UpgradeCode property in their Property table.

3. Save the .vbs file to any shared directory on the SCCM server and assign Write permissions for user accounts.4. Run .vbs script to collect Product Codes from client computers. To do this with SCCM package, run the following

command from the command line:

cmd.exe /c cscript.exe /nologo network_path_to_.vbs_script "{UpgradeCode}">network_path_to_output_file

The network_path_to_.vbs_script is a network path to the .vbs file created earlier, and thenetwork_path_to_output_file is a network path to the output text file to collect Product Codes for futureadministrative use. For example:



46

cmd.exe /c cscript.exe /nologo \\dc\CRMD_Codes\get_product_codes.vbs "{BF277E04-E06C-411E-A55A-C0015A170CB0}">\\dc\CRMD_Codes\product_codes.txt

Uninstalling Oracle Sales Cloud for IBM Notes Profile Per-User on the ClientsThis section describes how to uninstall the Oracle Sales Cloud for IBM Notes per-user profile on clients.

To uninstall Oracle Sales Cloud for IBM Notes profile per-user on clients:

1. Create the Uninstall package for this collection to uninstall all versions of CRMD Profile using msiexec command line.

a. In the Configuration Manager Console, navigate to Software Distribution, Packages node and create anew package.

You do not require any more parameters in this step, except Security: select SCCM and workstationadministrative account for package.

b. In the New Package Wizard, specify name and any other required data.

Note: Do not select This package contains source files check box on the second page of thewizard.

2. On the Access Accounts menu for this package, add SCCM administrator with Full Control privileges and domainaccounts of the users that work with Oracle Sales Cloud for IBM Notes.

3. Select the current SCCM Server as Distribution Point.4. Create a new program:

a. Right-clik the Program tree node and select New, and then the Program command from the context menu.b. On the New Program Wizard, specify the program name and the following WMIC command:

msiexec /x {ProductCode}

ProductCode in this command is the Windows Installer ProductCode from the output file of the .vbs script.See an example below:

cmd.exe /c cscript.exe /nologo \\dc\CRMD_Codes\get_product_codes

5. On the Environment tab of the New Program Wizard, select The Program can run: Only when a user is loggedon option and select the Allow users to interact with this program check box.

6. On the Advanced tab, Run once for every user who logs on is selected by default, do not change it.7. Do not modify the default settings on other tabs.

Note: Create and run different packages for all product codes simultaneously or one by one.

Msiexec.exe /x will run in the interactive mode that allows customer to close IBM Notes correctly and follow theuninstall MSI wizard. It also allows to cancel the uninstall process. It is recommended to run an inventory reportagain to be sure that all software was uninstalled. Refer to the Identifying Computers with Oracle Sales Cloud for IBMNotes Profile Installed section of this topic to see the instructions.

You can also use /q key with n parameter to specify the user interface level. It will hide the user interface of theuninstall wizard and run uninstall in silent mode.



47

msiexec "Disk:\...\Sales Cloud for IBM Notes.msi" /x /qn

Note: Oracle recommends that you run uninstall in silent mode. If IBM Notes is running duringuninstall, uninstall will fail and no other actions will be performed.

8. Right-click the Advertisements tree node of the Configuration Manager Console, and create the Advertisement forUninstall package(s) to make this/these package(s) active.

9. Choose the collection of the clients where Oracle Sales Cloud for IBM Notes Profile is installed and assign it to runAs soon as possible. The Advertisement will start as soon as you click Finish.

Note: SCCM runs every package only once, if you do not reactivate it.

10. Run advertise per-user uninstall of Oracle Sales Cloud for IBM Notes Profile using SCCM Advertisement for thepackage.



48

Documents

Deploying Sales Cloud for IBM Notes Sales Cloud · Deploying Sales Cloud for IBM Notes Chapter 2 Installing Oracle Sales Cloud for IBM Notes: Prerequisites 6 7. Change the SQL Predicate