text
stringlengths 65
20k
|
|---|
q.On the Web Tier Policy page, click Next without making any changes.r.On the Authorization page, click Next without making any changes.s.Click Finish to complete resource application creation.t.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.1.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. |
r.On the Authorization page, click Next without making any changes.s.Click Finish to complete resource application creation.t.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.1.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. |
s.Click Finish to complete resource application creation.t.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.1.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. |
t.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.1.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 1.Sign in as the Oracle Identity Cloud Service administrator to the Oracle Cloud Infrastructure Console. |
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.1.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 1.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. |
(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.1.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 1.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.2.In the left navigation pane, select Applications , then click Add to add a client application. |
1.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 1.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.2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed. |
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 1.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.2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next . |
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 1.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.2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now . |
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 1.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.2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code . |
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 1.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.2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code .7.In the Redirect URL field, enter your Oracle Integration instance URL and port. |
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 1.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.2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code .7.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. |
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 1.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.2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code .7.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.8.Under Resources , click Add Scope to add appropriate scopes. |
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 1.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.2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code .7.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.8.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. |
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 1.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.2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code .7.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.8.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. |
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 1.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.2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code .7.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.8.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.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service . |
This user must be created in Oracle Identity Cloud Service and have a local user password.Create the Confidential Client Application for Oracle Integration 1.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.2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code .7.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.8.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.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >. |
Create the Confidential Client Application for Oracle Integration 1.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.2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code .7.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.8.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.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >.11.Select the scope, then click Add. |
This administrator must have Oracle Identity Cloud Service instance access.2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code .7.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.8.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.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >.11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages. |
2.In the left navigation pane, select Applications , then click Add to add a client application.3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code .7.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.8.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.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >.11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish . |
3.Select Confidential Application .Chapter 2 Prerequisites for Creating a Connection 2-19The Add Confidential Application wizard is displayed.4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code .7.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.8.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.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >.11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values. |
4.On the Details page, enter an application name, and click Next .5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code .7.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.8.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.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >.11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.14.Copy and save these values. |
5.On the Client page, click Configure this application as a client now .6.In the Authorization section, select Refresh Token and Authorization Code .7.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.8.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.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >.11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.14.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. |
6.In the Authorization section, select Refresh Token and Authorization Code .7.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.8.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.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >.11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.14.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. |
7.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.8.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.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >.11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.14.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. |
For example: https:// OIC_URL :443/icsapis/agent/oauth/callback For the OAuth authorization code to work, the redirect URI must be set properly.8.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.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >.11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.14.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. |
8.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.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >.11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.14.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. |
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.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >.11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.14.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. |
This enables the client application to access Oracle Integration.9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >.11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.14.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.15.Activate the application. |
9.Search for the Oracle Fusion Applications resource application created in Set Up Trust Between Oracle Fusion Applications and Oracle Identity Cloud Service .10.Select the resource and click >.11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.14.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.15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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. |
10.Select the resource and click >.11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.14.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.15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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. |
11.Select the scope, then click Add.12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.14.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.15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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. |
12.Click Next without making changes on the Resource and Web Tier Policy pages.13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.14.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.15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications. |
13.On the Authorization page, click Finish .The Application Added dialog shows the client ID and client secret values.14.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.15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection. |
The Application Added dialog shows the client ID and client secret values.14.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.15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.Return to the Connections page and retest the connection.The connection is successful this time. |
14.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.15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.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. |
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.15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.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. |
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.15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.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. |
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.15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.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. |
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.15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.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. |
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.15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.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. |
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.15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.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. |
15.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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters. |
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.Chapter 2 Prerequisites for Creating a Connection 2-20If 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.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.This feature enables you to use the groovy script editor to create scripts to invoke integrations. |
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.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.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. |
This error occurs because the Oracle Integration user account with which you logged in is not part of Oracle Fusion Applications.1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.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. |
1.Log out of Oracle Integration and log back in with a user account that exists in Oracle Fusion Applications.2.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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.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. |
2.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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service. |
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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes . |
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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox. |
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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox.c.Select Set as Active to activate the sandbox. |
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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox.c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer . |
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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox.c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service. |
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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox.c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service.a.Click Web Services . |
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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox.c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service.a.Click Web Services .b.Click the icon to create a new web service connection. |
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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox.c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service.a.Click Web Services .b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL . |
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:anyTypeChapter 2 Prerequisites for Creating a Connection 2-21parameters.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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox.c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service.a.Click Web Services .b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page. |
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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox.c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service.a.Click Web Services .b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service. |
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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox.c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service.a.Click Web Services .b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows . |
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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox.c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service.a.Click Web Services .b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts . |
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.1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox.c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service.a.Click Web Services .b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add. |
1.Create a sandbox environment in the Oracle CX Sales and B2B Service.a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox.c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service.a.Click Web Services .b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void). |
a.In the upper right corner, select Settings > Manage Sandboxes .b.Create a sandbox.c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service.a.Click Web Services .b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette . |
b.Create a sandbox.c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service.a.Click Web Services .b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services . |
c.Select Set as Active to activate the sandbox.2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service.a.Click Web Services .b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services .g.With the process function selected, click Insert . |
2.On the desktop, click Tools > Application Composer .3.Register the Oracle Integration web service.a.Click Web Services .b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services .g.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. |
3.Register the Oracle Integration web service.a.Click Web Services .b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services .g.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.h.Complete the script to create the object function. |
a.Click Web Services .b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services .g.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.h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate . |
b.Click the icon to create a new web service connection.c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services .g.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.h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close. |
c.Enter the name and WSDL URL, then click Read WSDL .d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services .g.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.h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface. |
d.Complete the other fields on the page, then save and close the page.4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services .g.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.h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links . |
4.Create the object function to invoke the process method of the web service.a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services .g.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.h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create . |
a.In the left navigation pane, click Object Workflows .b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services .g.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.h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create .c.Enter a display label and name. |
b.Expand Objects > Custom Objects > CommonObject > common_object_name , then select Server Scripts .c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services .g.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.h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create .c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use. |
c.From the Actions dropdown list, select Add.d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services .g.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.h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create .c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list. |
d.Enter a function name and select a return value (for example, void).e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services .g.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.h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create .c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages . |
e.On the right side of the page, click Show/Hide Function Palette .f.Click Web Services .g.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.h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create .c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages .g.Click Desktop Pages . |
f.Click Web Services .g.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.h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create .c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages .g.Click Desktop Pages .h.Click Edit Creation Page . |
g.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.h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create .c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages .g.Click Desktop Pages .h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section. |
The Edit Script field is partially populated with the code for invoking the process method of the web service.h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create .c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages .g.Click Desktop Pages .h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close. |
h.Complete the script to create the object function.For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create .c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages .g.Click Desktop Pages .h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close.k.Click the Home icon at the top of the page. |
For example: Chapter 2 Prerequisites for Creating a Connection 2-22 i.Click Validate .j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create .c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages .g.Click Desktop Pages .h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close.k.Click the Home icon at the top of the page.6.Execute the action by clicking the button. |
j.Save and close.5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create .c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages .g.Click Desktop Pages .h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close.k.Click the Home icon at the top of the page.6.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 . |
5.Create the action to execute the function and expose the action as a button in the user interface.a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create .c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages .g.Click Desktop Pages .h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close.k.Click the Home icon at the top of the page.6.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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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. |
a.In the left navigation pane, click Actions and Links .b.From the Actions dropdown list, select Create .c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages .g.Click Desktop Pages .h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close.k.Click the Home icon at the top of the page.6.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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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 . |
b.From the Actions dropdown list, select Create .c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages .g.Click Desktop Pages .h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close.k.Click the Home icon at the top of the page.6.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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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. |
c.Enter a display label and name.d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages .g.Click Desktop Pages .h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close.k.Click the Home icon at the top of the page.6.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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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. |
d.From the Method Name dropdown list, select the method to use.e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages .g.Click Desktop Pages .h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close.k.Click the Home icon at the top of the page.6.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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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.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 For Fusion Applications Releases 13 and Later 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. |
e.On the right side of the page, select Script from the Source dropdown list.f.In the left navigation pane, click Pages .g.Click Desktop Pages .h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close.k.Click the Home icon at the top of the page.6.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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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.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 For Fusion Applications Releases 13 and Later 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 Obtain the Service Catalog Service WSDL for Release 12 Obtain the Event Catalog URL Obtain the Interface Catalog URLChapter 2 Prerequisites for Creating a Connection 2-24Obtain the Service Catalog Service WSDL For Releases 10 Through 11 WSDL Requirements Where Do You Get the WSDL? |
f.In the left navigation pane, click Pages .g.Click Desktop Pages .h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close.k.Click the Home icon at the top of the page.6.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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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.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 For Fusion Applications Releases 13 and Later 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 Obtain the Service Catalog Service WSDL for Release 12 Obtain the Event Catalog URL Obtain the Interface Catalog URLChapter 2 Prerequisites for Creating a Connection 2-24Obtain 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. |
g.Click Desktop Pages .h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close.k.Click the Home icon at the top of the page.6.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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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.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 For Fusion Applications Releases 13 and Later 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 Obtain the Service Catalog Service WSDL for Release 12 Obtain the Event Catalog URL Obtain the Interface Catalog URLChapter 2 Prerequisites for Creating a Connection 2-24Obtain 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. |
h.Click Edit Creation Page .i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close.k.Click the Home icon at the top of the page.6.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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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.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 For Fusion Applications Releases 13 and Later 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 Obtain the Service Catalog Service WSDL for Release 12 Obtain the Event Catalog URL Obtain the Interface Catalog URLChapter 2 Prerequisites for Creating a Connection 2-24Obtain 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. |
i.In the Configure Detail Form: Buttons and Actions section, move the button you created to the Selected Buttons section.j.Save and close.k.Click the Home icon at the top of the page.6.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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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.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 For Fusion Applications Releases 13 and Later 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 Obtain the Service Catalog Service WSDL for Release 12 Obtain the Event Catalog URL Obtain the Interface Catalog URLChapter 2 Prerequisites for Creating a Connection 2-24Obtain 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. |
j.Save and close.k.Click the Home icon at the top of the page.6.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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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.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 For Fusion Applications Releases 13 and Later 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 Obtain the Service Catalog Service WSDL for Release 12 Obtain the Event Catalog URL Obtain the Interface Catalog URLChapter 2 Prerequisites for Creating a Connection 2-24Obtain 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. |
k.Click the Home icon at the top of the page.6.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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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.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 For Fusion Applications Releases 13 and Later 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 Obtain the Service Catalog Service WSDL for Release 12 Obtain the Event Catalog URL Obtain the Interface Catalog URLChapter 2 Prerequisites for Creating a Connection 2-24Obtain 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. |
6.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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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.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 For Fusion Applications Releases 13 and Later 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 Obtain the Service Catalog Service WSDL for Release 12 Obtain the Event Catalog URL Obtain the Interface Catalog URLChapter 2 Prerequisites for Creating a Connection 2-24Obtain 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.This section describes how to derive the external virtual host and port for a tokenized service catalog service WSDL. |
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 theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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.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 For Fusion Applications Releases 13 and Later 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 Obtain the Service Catalog Service WSDL for Release 12 Obtain the Event Catalog URL Obtain the Interface Catalog URLChapter 2 Prerequisites for Creating a Connection 2-24Obtain 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.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. |
For existing connections, you are prompted to specify a service catalog service WSDL (for accessing and configuring theChapter 2 Prerequisites for Creating a Connection 2-23inbound 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.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 For Fusion Applications Releases 13 and Later 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 Obtain the Service Catalog Service WSDL for Release 12 Obtain the Event Catalog URL Obtain the Interface Catalog URLChapter 2 Prerequisites for Creating a Connection 2-24Obtain 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.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 . |
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.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 For Fusion Applications Releases 13 and Later 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 Obtain the Service Catalog Service WSDL for Release 12 Obtain the Event Catalog URL Obtain the Interface Catalog URLChapter 2 Prerequisites for Creating a Connection 2-24Obtain 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.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 users job role. |
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.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 For Fusion Applications Releases 13 and Later 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 Obtain the Service Catalog Service WSDL for Release 12 Obtain the Event Catalog URL Obtain the Interface Catalog URLChapter 2 Prerequisites for Creating a Connection 2-24Obtain 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.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 users 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. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.