Prerequisites for Creating a Connection

Subscribe to the Oracle CX Sales and B2B Service

This action enables you to create an Oracle CX Sales and B2B Service user account with the correct privileges. You specify this user account when creating an Oracle CX Sales and B2B Service Adapter connection on the Connections page.

Enable Event Subscriptions in the Oracle CX Sales and B2B Service

Before you can subscribe to events with the Oracle CX Sales and B2B Service Adapter, you must perform a series of configuration tasks. For this example, Oracle Service Cloud (RightNow) Adapter is the other connection with the Oracle CX Sales and B2B Service in this integration.

Verify the Source System Record in the Oracle CX Sales and B2B Service

The integration is designed to work with the Oracle CX Sales and B2B Service Release 10.

To verify the source system record in the Oracle CX Sales and B2B Service:

Log in to an Oracle CX Sales and B2B Service instance with a user with system administrator privileges.
Navigate to the Setup and Maintenance page.
Select the All Tasks tab.
Enter Manage Trading community Source System in the Name field, and click Search.
In the Search Results section, click the icon under Go to Task.

The Manage Trading Community Source Systems page is displayed.
Select Starts with from the Code drop-down menu.
To the right of Starts with, enter a value in the field, then click Search. For this example, RNOW is entered.
In the Search Results section, verify the value you entered (for this example, RNOW) is displayed in the Code column and ensure the Enable for Trading Community Members checkbox is selected. If the Enable for Trading Community Members check box is not selected, then perform the following steps:
1. Select the RNOW row.
2. Click the Edit icon.
3. Select the Enable for Trading Community Members checkbox.

Create the Source System Record in the Oracle CX Sales and B2B Service

To create the Source System Record in the Oracle CX Sales and B2B Service:

If the Source System definition RNOW record is not found in the Oracle CX Sales and B2B Service instance, then follow the steps below to create one:

Log in to the Oracle CX Sales and B2B Service instance with a user with system administrator privileges.
Navigate to the Setup and Maintenance page.
Select the All Tasks tab.
Enter Manage Trading community Source System in the Name field, and click Search.
In the Search Results section, click the icon under Go to Task.

The Manage Trading Community Source Systems page is displayed.
Select Starts with from the Code drop-down menu.
Enter RNOW in the field, then click Search. For this example, Oracle Service Cloud (RightNow) Adapter is the other connection with which the Oracle CX Sales and B2B Service is communicating.
Under Search Results, click the New icon.
On the Create Source System page, fill in the values as follows. For this example, Oracle Service Cloud (RightNow) Adapter is the other connection with which the Oracle CX Sales and B2B Service is communicating.
- Code field: Enter RNOW.
- Name field: Enter Service Cloud.
- Description: field: Enter a description. For example:
```
Maintains cross references between the Oracle Fusion Applications database and records imported using comma-separated files.
```
- Enable for Trading Community Members checkbox: Select the checkbox.
Click Save, then click Close.

Verify Source System Entities

To verify source system entities:

Navigate to the Setup and Maintenance page.
Select the All Tasks tab.
Enter Manage Source System Entities in the Name field, and click Search.
In the Search Results section, click the icon under Go to Task.

The Manage Source System Entities page is displayed.
From the Source Systems for Trading Community Members list, select Service Cloud (RightNow). For this example, Oracle Service Cloud (RightNow) Adapter is the other connection with which the Oracle CX Sales and B2B Service is communicating.
In the Service Cloud (RightNow): Entities section, ensure that the Address, Contact Points, and Parties checkboxes are selected.

Enable the Trading Community Events Profile Option

This profile option only applicable to Trading Community Architecture (TCA) objects such as Accounts and Contacts. If the profile option is set to No out of the box, the events for the Accounts and Contacts objects are disabled. The rest of the objects do not require any profile option and are enabled to raise business events out of the box.

To enable the trading community events profile option:

Navigate to the Setup and Maintenance page.
Select the All Tasks tab.
Enter Manage Trading Community Common Profile Options in the Name field, and click Search.
In the Search Results section, click the icon under Go to Task.

The Manage Trading Community Common Profile Options page is displayed.
Select HZ_ENABLE_EVENT_TRACKING.

The Manage Trading Community Common Profile Options page for the HZ_ENABLE_EVENT_TRACKING page is displayed.
In the HZ_ENABLE_EVENT_TRACKING:Profile Values section, set the Site level Profile Value to Yes.
Click Save, then click Close.
On the Manage Trading Community Common Profile Options page, select HZ_INVOKE_OBJ_WF_ON_TRACKING.

The Manage Trading Community Common Profile Options page for the HZ_INVOKE_OBJ_WF_ON_TRACKING page is displayed.
In the HZ_INVOKE_OBJ_WF_ON_TRACKING: Profile Values section, set the Site level Profile Value to Yes.
Click Save, then click Close.

Create Custom Business Events

You can create custom business events in Application Composer that are visible for selection when configuring the Oracle CX Sales and B2B Service Adapter as a trigger connection in the Adapter Endpoint Configuration Wizard. You must access Application Composer through the Oracle Fusion Applications user interface. Select CRM Cloud from the Applications list in Application Composer to create the custom objects and promote them as custom events to be consumed by the Oracle CX Sales and B2B Service Adapter.

See technical note 2535444.1 at My Oracle Support for instructions.

Create an Integration User Account

To invoke an Oracle CX Sales and B2B Service service catalog or event catalog web service from Oracle Integration, you create a separate user.

To create the integration user account:

Log in to the Oracle CX Sales and B2B Service with a user with system administrator privileges.
Navigate to Navigator > My Team > Manage Users.

The Manage Users page is displayed.
Click Manage Users.
Click the Create New User icon beside Show Photo.

Enter the following information, and click Save.

Field	Description
Last Name	Enter `CUSTOMER_OIC_INTEG_USER`
Email	Enter a valid email address.
Hire Date	Enter the date.
User Name	Enter `CUSTOMER_OIC_INTEG_USER`.
Person Type	Enter `Employee`.
Legal Employer	Select a valid legal organization.
Business Unit	Select a valid business unit.
Send user name and password	Select this checkbox.
User Login	Enter `CUSTOMER_OIC_INTEG_USER`.
Password	Enter a password for the username.

A notification email is sent to the email address after the user is created.

Log out of the Oracle CX Sales and B2B Service.
Log in to the Oracle CX Sales and B2B Service instance with CUSTOMER_OIC_INTEG_USER and the temporary password provided in the notification email.
Change the password after logging in initially.

The Oracle CX Sales and B2B Service page appears.
Log out of the Oracle CX Sales and B2B Service.

Assign Integration Roles

You associate a user with roles and privileges in Oracle Authorization Policy Manager on the Oracle Entitlements Server for Releases 10 and 11. If using Releases 12 and later, you use the Security Console to manage users and roles.

You can configure an Oracle Integration instance to use the Username Password Token security policy to access the resources in an Oracle CX Sales and B2B Service Adapter instance.

An Oracle CX Sales and B2B Service Adapter instance exposes service catalogs and event catalogs to Oracle Integration. These resources are secured in the Oracle CX Sales and B2B Service Adapter. You need to assign the required roles and privileges to a user.

Note:

For prebuilt integrations, you must use the name CUSTOMER_OIC_INTEG_USER. In prebuilt integrations, connections and filter expressions for echo suppression refer to CUSTOMER_OIC_INTEG_USER as the user name. For new integrations, the user name can be anything.

Role	Description
ALL_INTEGRATION_POINTS_ALL_DATA	Starting with release 12, this role is no longer supported. When existing customers upgrade to release 12, users with this role continue using it, although it is hidden from the Security Console. If you create a new integration user in release 12 or later, you cannot assign this role.
Customer Relationship Management Application Administrator	This role is supported in releases 12 and later.
SOAOperator	This role is required to receive business events.
FND_MANAGE_CATALOG_SERVICE_PRIV	Role for managing the web services catalog.

Additional roles may be required per each interface requirement.

Note:

You must have administrator privileges in Oracle Authorization Policy Manager to perform the following steps.

Assigning Integration Roles in Releases 12 and Later

Use the Security Console to manage application security such as roles, users, certificates, and administration tasks. Access to the Security Console is provided by the predefined Security Manager role. Access the Security Console in the following ways:

Use the Manage Job Roles or Manage Duties tasks in the Setup and Maintenance work area.
Select Navigator > Tools > Security Console.

Description of the illustration sales_cloud_security.png

For example, the Roles page for the Integration Specialist user looks as follows:

Description of the illustration int_special.png

See Oracle Cloud Applications Security Console of Securing Sales and Service.

Assigning Integration Roles in Releases 10 and 11

Log in to Oracle Authorization Policy Manager.
Under Search, select Users from the For dropdown list.
Enter CUSTOMER_OIC_INTEG_USER (for prebuilt integrations) or any name (for new integrations) in the Search field, then click the Search icon.
Select that name in the search results, then click the View icon.
On the username tab (CUSTOMER_OIC_INTEG_USER or whatever name you created), click the Application Role Assignments subtab.
Click Map.
In the Map Application Roles to User dialog:
1. Select crm from the Application Name dropdown list.
2. Select Contains from the Role Name dropdown list, enter ALL_INTEGRATION_POINTS_ALL_DATA (for releases 11 and earlier) or Customer Relationship Management Application Administrator (for releases 12 and later) in the Role Name field, and then click Search.
3. Select ALL_INTEGRATION_POINTS_ALL_DATA (for releases 11 and earlier) or Customer Relationship Management Application Administrator (for releases 12 and later) in the search results, then click Map Roles.
  
  The role is mapped for the user under crm.
Click Map.
Perform the following steps in the Map Application Roles to User dialog.
1. Select hcm from the Application Name dropdown list, and repeat steps 7.b, and 7.c.
2. The role is mapped for the user under hcm.
Click Map.
Perform the following steps in the Map Application Roles to User dialog.
1. Select fscm from the Application Name dropdown list, and repeat steps 7.b, 7.c.
  
  The role is mapped for the user under fscm.
Click Map.
Perform the following steps in the Map Application Roles to User dialog.
1. Select soa-infra from the Application Name dropdown list.
2. Select Contains from the dropdown menu next to Display Name.
3. Enter SOA Operator in the Display Name field, and then click Search.
4. Select the SOA Operator role in the search results, then click Map Roles.
  
  The role is mapped to the user under soa-infra.
On the username tab (CUSTOMER_OIC_INTEG_USER or whatever name you created), click Find Policies at the top-right corner of the page
In the Choose an Application dialog, select fscm and click OK.

The Search Authorization Policies tab is displayed.
Click the New icon under Functional Policies on the Search Authorization Policies page.
On the Untitled tab, enter Policy for manage services catalog in the Name field.
Ensure your username (CUSTOMER_OIC_INTEG_USER or whatever name you created) is listed under Principals. If the use is not listed under Principals, then click + next to Principals.
Perform the following steps in the Search Principal dialog.
1. Select the Users tab.
2. Select Starts With from the User Name dropdown list, enter the user name (CUSTOMER_OIC_INTEG_USER or whatever name you created) in the User Name field, and then click Search.
3. Select the user name in the search results, then click Add Selected.
4. Click Add Principals.
Select All next to Match under Principals.
Click + next to Targets.
In the Search Target dialog, click the Entitlements tab, then select Starts With from the Name dropdown list.
Enter FND_MANAGE_CATALOG_SERVICE_PRIV, then click Search.
Select Manage Webservices catalog in the search results, then click Add Selected.
Ensure Manage Webservices catalog is added onto Selected Targets.
Click Add Targets.

A new Policy for manage services catalog is added to the user.
Click Save on the Untitled tab.
Sign out from Oracle Authorization Policy Manager.

Verify the Status of Location-Based Access Control (LBAC)

Check if you have enabled Location-Based Access Control (LBAC) for Fusion Applications (for the Oracle CX Sales and B2B Service).

If LBAC is enabled, you must allowlist (explicitly allow identified entities access) the Oracle Integration NAT Gateway IP address in your LBAC.

If LBAC is enabled, you must allowlist (explicitly allow identified entities access) the Oracle Integration NAT Gateway IP address in your LBAC. If you do not perform this task, you can receive a 401 Access Denied error or 403 Forbidden error from Oracle Fusion Applications.

If you do not perform this task, you can receive a 401 Access Denied error or 403 Forbidden error from Oracle Fusion Applications.

Upload a Security Certificate

Certificates validate outbound SSL connections. If you make an SSL connection in which the root certificate does not exist in Oracle Integration, an exception is thrown. In that case, you must upload the appropriate certificate. A certificate enables Oracle Integration to connect with external services.

See Upload an SSL Certificate.

Perform Prerequisites to Use the OAuth Authorization Code Credentials Security Policy

You must set up trust between Oracle Fusion Applications and Oracle Identity Cloud Service and create a client application for Oracle Integration if you want to use the OAuth Authorization Code Credentials security policy. Once these tasks are completed, you can successfully configure a connection on the Connections page.

Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service

Get the JWK signing certificates from the Oracle Identity Cloud Service of Oracle Integration.
1. Get the REST API of the Oracle Identity Cloud Service endpoint that gives you the signing certificate endpoint. For example:
```
/admin/v1/SigningCert/jwk
```
  See All REST Endpoints in REST API for Oracle Identity Cloud Service.
2. Copy the endpoint.
3. Get the Oracle Identity Cloud Service URL from the Oracle Cloud Infrastructure Console or from the Oracle Integration About menu.
4. Add that URL to the front of the signing certificate and use a tool (for example, postman) to invoke the REST APIs. For example:
```
https://IDCS_URL.identity.oraclecloud.com/admin/v1/SigningCert/jwk
```
5. Perform a GET call to retrieve the payloads of the certificates. There are two sections in the payload:
  - Oracle Identity Cloud Service certificate
  - Certificate authority (CA) certificate
  Examples of the type of response you receive are provided. See Retrieve the Tenant's Signing Certificate in JWK Format.
6. Copy both certificate sections into separate files. Note that the headers and footers in the files must be in the following exact format to be successfully uploaded to Oracle Fusion Applications:
```
-----BEGIN CERTIFICATE-----
 content_of_certificate
. . .
. . .
-----END CERTIFICATE-----
```
  You can validate the certificate. For example:
```
openssl x509 -in IDCS.cert -noout -text
```
Upload the certificates to the Oracle Fusion Applications Security Console.
1. Log in to Oracle Fusion Applications as a user with the IT Security Manager role.
2. In the navigation pane, select Tools, then Security Console.
3. Select API authentication in the left navigation pane.
4. Click Create Oracle API Authentication Provider, then click Edit in the upper right.
5. In the Trusted Issuer field, enter:
```
https://identity.oraclecloud.com
```
6. In the Token Types section, select JWT.
7. Click Save and Close.
8. Click Inbound API Authentication Public Certificates, then click Add New Certificate.
9. Enter a name in the Certificate Alias field (for example, MY_IDCS_CERT).
10. In the Import Public Certificate field, click Choose File to upload the first certificate file, then click Save.
11. Repeat these steps to upload the second certificate file.
Create an Oracle Identity Cloud Service resource application to represent the Oracle Fusion Applications resource.
1. Log in to Oracle Identity Cloud Service as the Oracle Identity Cloud Service administrator.
2. In the left navigation pane, click Applications, then click Add.
3. Click Confidential Application.
4. On the Details page, provide a name (for example, FA Resource), and click Next.
5. On the Client page, click Next without making changes.
6. On the Resources page, click Configure this application as a resource server now.
7. Optionally update the value in the Access Token Expiration field.
8. Select Is Refresh Token Allowed.
9. In the Primary Audience field, add the Oracle Fusion Applications URL and port. This is the primary recipient where the token is processed.
```
https://FA_URL:443
```
10. In the Scopes section, click Add.
11. In the Scope field, enter /.
12. In the Description field, enter All.
13. Select Requires Consent.
14. Click Add, then click Next.
15. On the Web Tier Policy and Authorization pages, click Next without making any changes.
16. Click Finish to complete resource application creation.
17. Click Activate to activate your client application. The resource server representing the resource is now active.

(Optional) Create a Local User

Note:

The following step is only required if the Oracle Fusion Applications user is not federated with Oracle Identity Cloud Service or whichever identity provider you are using.

Create an Oracle Identity Cloud Service local user. Carefully review the following table to see if you already have a local user.

Scenario	Do I Need to Create a Local User?
You have an Oracle Fusion Applications user federated with the Oracle Identity Cloud Service that is protecting Oracle Integration.	No. You do not need to create the local Oracle Identity Cloud Service Oracle Fusion Applications user. This is because Oracle Identity Cloud Service already has Oracle Fusion Applications users in its repository.
You do not have federation between Oracle Fusion Applications and the Oracle Identity Cloud Service that is protecting Oracle Integration.	Yes. You must create the local Oracle Identity Cloud Service Oracle Fusion Applications user that you plan to use with the OAuth setup in Oracle Integration.

The Oracle Identity Cloud Service administrator must create a nonfederated local username in Oracle Identity Cloud Service that matches the user in Oracle Fusion Applications. If you have already used and invoked Oracle Fusion Applications REST endpoints, you likely already created a user with the necessary roles and accesses to invoke the REST endpoints of Oracle Fusion Applications. This user must be created in Oracle Identity Cloud Service and have a local user password.

Create the Confidential Client Application for Oracle Integration

Sign in as the Oracle Identity Cloud Service administrator to the Oracle Cloud Infrastructure Console. This administrator must have Oracle Identity Cloud Service instance access.
In the left navigation pane, select Applications, then click Add to add a client application.
Select Confidential Application.
The Add Confidential Application wizard is displayed.
On the Details page, enter an application name, and click Next.
On the Client page, click Configure this application as a client now.
In the Authorization section, select Refresh Token and Authorization Code.
In the Redirect URL field, enter your Oracle Integration instance URL and port. For example:
```
https://OIC_URL:443/icsapis/agent/oauth/callback
```
For the OAuth authorization code to work, the redirect URI must be set properly.
Under Resources, click Add Scope to add appropriate scopes.
If the Oracle Fusion Applications instance is federated with the Oracle Identity Cloud Service instance, the Oracle Integration cloud service application is listed among the resources for selection. This enables the client application to access Oracle Integration.
Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service.
Select the resource and click >.
Select the scope, then click Add.
Click Next without making changes on the Resource and Web Tier Policy pages.
On the Authorization page, click Finish.
The Application Added dialog shows the client ID and client secret values.

Copy and save these values. You need this information when creating a connection for the OAuth Authorization Code Credentials security policy on the Connections page.

Note the following details for successfully authenticating your account on the Connections page.

If The...	Then...
Oracle Identity Cloud Service safeguarding Oracle Integration and the Oracle Fusion Applications resource application are the same.	Log in to Oracle Integration using the local Oracle Fusion Applications user created earlier. You must create a connection and click Provide Consent on the Connections page for authentication to succeed.
Oracle Identity Cloud Services safeguarding Oracle Integration and the Oracle Fusion Applications resource application are different.	Log in to Oracle Integration using a general Oracle Integration developer account, create a connection, and click Provide Consent on the Connections page. You need to log in to the Oracle Fusion Applications resource Oracle Identity Cloud Service application using the local Oracle Fusion Applications user account created earlier.

Activate the application.

Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account

After you configure the OAuth Authorization Code Credentials security policy on the Connections page, you must test your connection.

If you are logged in to Oracle Integration with an Oracle Integration user account and click Provide Consent to test the OAuth flow, consent is successful. However, when you test the connection, it fails with an Unauthorized 401 error.

This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.

Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.
Return to the Connections page and retest the connection.
The connection is successful this time.

Enable Echo Suppression Filters

During bidirectional object synchronization, echoes are generated. For example, an event triggered in the Oracle CX Sales and B2B Service is synchronized through Oracle Integration to Oracle Service Cloud (with the Oracle RightNow Adapter), which then triggers an event in Oracle Service Cloud and then back to the Oracle CX Sales and B2B Service, and so on. Oracle Integration-based integrations use echo suppression to prevent unwanted update or create events (the echoes) from returning to the source application.

Filtering is used at the source application together with a LastUpdatedBy attribute in the record payload. In prebuilt integrations, Oracle Integration uses the Oracle CX Sales and B2B Service username created as part of the prebuilt integration setup to invoke every API of the application.

While the filtering is defined in Oracle Integration, it occurs in the event handler framework at activation/subscription time.

The Oracle CX Sales and B2B Service event handler framework evaluates the echo suppression expression after the internal event has been enriched to prevent the echo payload push to Oracle Integration.

Echo suppression expression for account create/update flows is as follows:

<xpathExpr xmlns:ns_0='http://xmlns.oracle.com/adf/svc/types/' xmlns:ns_1='http://xmlns.oracle.com/apps/crmCommon/salesParties/accountService/types/' xmlns:ns_5='http://xmlns.oracle.com/apps/crmCommon/salesParties/accountService/'>$eventPayload/ns_1:result/ns_0:Value/ns_5:LastUpdatedBy != 'CUSTOMER_OIC_INTEG_USER'</xpathExpr>

Echo suppression expression for contact create/update flows is as follows:

<xpathExpr xmlns:ns_0='http://xmlns.oracle.com/adf/svc/types/' xmlns:ns_5='http://xmlns.oracle.com/apps/crmCommon/salesParties/contactService/' xmlns:ns_1='http://xmlns.oracle.com/apps/crmCommon/salesParties/contactService/types/'>$eventPayload/ns_1:result/ns_0:Value/ns_5:LastUpdatedBy != 'CUSTOMER_OIC_INTEG_USER'</xpathExpr>

Integrate Groovy Scripts

The Oracle CX Sales and B2B Service Adapter inbound endpoint WSDL interface supports the use of concrete values for custom business objects in the WSDL in place of xsd:anyType parameters. This feature enables you to use the groovy script editor to create scripts to invoke integrations. The groovy script editor is unable to recognize xsd:anyType parameters.

Perform the following high level steps from the CRM Fusion Home page (that is, the Fuse user interface) to integrate the groovy script.

Note:

If you have existing integrations with inbound endpoints (with custom business objects having xsd:anyType) generated using an Oracle Integration version prior to 16.3.3 and want to use groovy scripts, the integration must be re-edited and all artifacts must be generated again.

Create a sandbox environment in the Oracle CX Sales and B2B Service.
1. In the upper right corner, select Settings > Manage Sandboxes.
2. Create a sandbox.
3. Select Set as Active to activate the sandbox.
On the desktop, click Tools > Application Composer.
Register the Oracle Integration web service.
1. Click Web Services.
2. Click the icon to create a new web service connection.
3. Enter the name and WSDL URL, then click Read WSDL.
4. Complete the other fields on the page, then save and close the page.
Create the object function to invoke the process method of the web service.
1. In the left navigation pane, click Object Workflows.
2. Expand Objects > Custom Objects > CommonObject > common_object_name, then select Server Scripts.
3. From the Actions dropdown list, select Add.
4. Enter a function name and select a return value (for example, void).
5. On the right side of the page, click Show/Hide Function Palette.
6. Click Web Services.
7. With the process function selected, click Insert.
  
  The Edit Script field is partially populated with the code for invoking the process method of the web service.
8. Complete the script to create the object function. For example:
  
  Description of the illustration ics_create_object_func.png
9. Click Validate.
10. Save and close.
Create the action to execute the function and expose the action as a button in the user interface.
1. In the left navigation pane, click Actions and Links.
2. From the Actions dropdown list, select Create.
3. Enter a display label and name.
4. From the Method Name dropdown list, select the method to use.
5. On the right side of the page, select Script from the Source dropdown list.
6. In the left navigation pane, click Pages.
7. Click Desktop Pages.
8. Click Edit Creation Page.
9. In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.
10. Save and close.
11. Click the Home icon at the top of the page.
Execute the action by clicking the button.

Obtain the Oracle CX Sales and B2B Service Service Catalog Service WSDL, Event Catalog URL, or Interface Catalog URL (For Connections Created Prior to 2/18/20)

The steps in this section are only required for existing connections created prior to the initial release of the simplified connections page on 2/18/20. For existing connections, you are prompted to specify a service catalog service WSDL (for accessing and configuring the inbound and outbound adapter to use either business objects or business services) in the OSC Services Catalog WSDL URL field and an optional event catalog URL (for accessing and configuring the inbound adapter to use event subscriptions) in the OSC Events Catalog URL field or interface catalog URL (for accessing and configuring the outbound adapter to use Oracle Fusion Applications REST API resources) in the Interface Catalog URL field.

Note:

For new connections created with the initial release of the simplified connections page on 2/18/20, the preconfiguration details described in this section are not required. All WSDLs and URLs are automatically identified for you based on the Oracle CX Sales and B2B Service host name that you specify in the CX Sales and B2B Service Host field on the Connections page.

You specify the appropriate property values in the Oracle CX Sales and B2B Service Adapter Connection Properties dialog on the Connections page.
Description of ics_osc_connect_props.png follows
Description of the illustration ics_osc_connect_props.png

The following sections describe how to obtain the service catalog service WSDL, event catalog URL, and interface catalog URL:

For Fusion Applications Releases 10 Through 12

Obtain the Oracle Fusion Applications Releases 10 through 12 service catalog service WSDLs, event catalog URLs, and interface catalog URLs through the following methods.

Obtain the Service Catalog Service WSDL For Releases 10 Through 11

WSDL Requirements	Where Do You Get the WSDL?
The URL must be that of a service catalog service WSDL. The service catalog service is a Fusion Application service that returns a list of external services available for integration. It allows clients to retrieve information about all public Fusion Application service endpoints available for that instance. The service catalog service enables clients to retrieve information about all public Oracle Fusion Application service endpoints available for that instance. The information it returns is specific to the particular cloud instance and also reflects the new services that may have been introduced in patches applied to the instance. This service is used to programmatically discover the SOAP services available on the cloud instance and retrieve the necessary metadata to invoke the SOAP services to manage business objects.	The developer creating an Oracle CX Sales and B2B Service connection must work with the Oracle CX Sales and B2B Service administrator to get the concrete WSDL URL for the service catalog service provisioned for the specific SaaS application.

WSDL Requirements

Where Do You Get the WSDL?

The URL must be that of a service catalog service WSDL. The service catalog service is a Fusion Application service that returns a list of external services available for integration. It allows clients to retrieve information about all public Fusion Application service endpoints available for that instance.

The service catalog service enables clients to retrieve information about all public Oracle Fusion Application service endpoints available for that instance. The information it returns is specific to the particular cloud instance and also reflects the new services that may have been introduced in patches applied to the instance. This service is used to programmatically discover the SOAP services available on the cloud instance and retrieve the necessary metadata to invoke the SOAP services to manage business objects.

The developer creating an Oracle CX Sales and B2B Service connection must work with the Oracle CX Sales and B2B Service administrator to get the concrete WSDL URL for the service catalog service provisioned for the specific SaaS application.

This section describes how to derive the external virtual host and port for a tokenized service catalog service WSDL. The topology information in the Topology Registration setup task contains the external virtual host and port for the domains and applications. The following instructions describe the steps for deriving the values using the service catalog service WSDL URL as an example: https://atf_server:port/fndAppCoreServices/ServiceCatalogService.

To access the Review Topology page, the ASM_REVIEW_TOPOLOGY_HIERARCHY_PRIV entitlement must be granted to the user’s job role. The entitlement is granted to the ASM_APPLICATION_DEPLOYER_DUTY duty role, which is inherited by the duty roles ASM_APPLICATION_DEVELOPER_DUTY and ASM_APPLICATION_ADMIN_DUTY.

If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role. Contact your cloud instance security administrator for assistance.

Log in to the cloud instance.
Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.
Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.
Click the Detailed tab in the middle of the window.

The tab shows the list of domains configured in the cloud instance.

Description of the illustration osc_get_wsdl_detals.png

Map the token name for the service path value to the domain name in the Topology Manager:

Token Name in Service Path	Domain Name
atf_server	CommonDomain
crm_server	CRMDomain
fin_server	FinancialDomain
hcm_server	HCMDomain
ic_server	ICDomain
prc_server	ProcurementDomain
prj_server	ProjectsDomain
scm_server	SCMDomain

Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain. In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.

Description of the illustration osc_get_wsdl_detals2.png
Replace the domainName_server:PortNumber with the external virtual host and port identified in the previous step. For example:

https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl

Obtain the Service Catalog Service WSDL For Release 12

To obtain the physical endpoint of your instance, perform the following steps:

Log in to the Fusion Applications home page. For example:
```
https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome
```
Where acme is the system name and fs is a Fusion Applications domain.
Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ServiceCatalogService?WSDL. For example:
```
https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ServiceCatalogService?WSDL
```

Obtain the Event Catalog URL

You must know the customer relationship management (CRM) URL format to access the CRM application user interface. Follow the URL format to determine the event catalog URL. For example, if the CRM URL format is:

https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHome

Then the event catalog URL is:

https://fusxxxx-crm-ext.us.oracle.com/soa-infra

The event catalog URL https://host:port/soa-infra is a partial URL and must only be provided on the Connections page. Do not open this URL with a browser. If you do, you receive a Page not found error. The adapter does not access this URL directly. Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).

To check the public events defined in the catalog, enter the following complete URL in a browser:

https://host:port/soa-infra/PublicEvent/catalog

Obtain the Interface Catalog URL

The interface catalog URL is formatted as follows. Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.

https://host:port_for_the_common_domain/helpPortalApi/otherResources/latest/interfaceCatalogs

For Fusion Applications Releases 13 and Later

Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.

Obtain the Service Catalog Service WSDL

To obtain the physical endpoint of your instance, perform the following steps:

Log in to the Fusion Applications home page. For example:
```
https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome
```
Where acme is the system name and us6 is the data center.
Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ServiceCatalogService?WSDL. For example:
```
https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDL
```

Obtain the Event Catalog URL

Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint. You must switch to the new consolidated endpoint that conforms to the following naming pattern:

https://systemName.fa.dcsn.oraclecloud.com/...

You must switch to the consolidated endpoint immediately after upgrading to Release 13. Newly provisioned instances using Release 13 only have the consolidated endpoint available. In Release 13, multiple domains are consolidated. You must specify the domain in the URL. For example, if specifying the fa domain, the URL looks as follows:

Copy the following URL:
```
https://acme.fa.us6.oraclecloud.com/
```

Append soa-infra to the end of the URL:

https://acme.fa.us6.oraclecloud.com/soa-infra

Obtain the Interface Catalog URL

The interface catalog URL is formatted as follows. Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.

https://host:port_for_the_common_domain/root_context/otherResources/latest/interfaceCatalogs

Where root_context is one of the following root context values:

ERP/SCM pillar:
- fscmRestApi: for ERP/SCM REST services (includes PPM/Procurement).
- fscmService: for ERP/SCM non-REST services, such as SOAP services.
HCM pillar:
- hcmRestApi: for HCM REST services.
- hcmService: for HCM non-REST services, such as SOAP services.
CRM pillar:
- crmRestApi: for CRM REST services.
- crmServices: for CRM non-REST services, such as SOAP services.