text
stringlengths 65
20k
|
|---|
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.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role. |
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.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance. |
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.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance. |
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.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading. |
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.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window. |
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.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window. |
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.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud 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.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain. |
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.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively. |
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.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step. |
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.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService? |
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.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page. |
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.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain. |
The entitlement is granted to the ASM_APPLICATION_DEPLOYER_DUTY duty role, which is inherited by the duty roles ASM_APPLICATION_DEVELOPER_DUTY and ASM_APPLICATION_ADMIN_DUTY.If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL . |
If the menu items and tasks described in the following procedure are not available in your cloud instance, your user account is missing the required role.Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface. |
Contact your cloud instance security administrator for assistance.1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL. |
1.Log in to the cloud instance.2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page. |
2.Click the Navigator icon in the global area in the top part of the window, then chose Setup and Maintenance under the Tools heading.3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser. |
3.Select Review Topology under the Topology Registration section in the Tasks regional area on the left side of the window.4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser.If you do, you receive a Page not found error. |
4.Click the Detailed tab in the middle of the window.The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser.If you do, you receive a Page not found error.The adapter does not access this URL directly. |
The tab shows the list of domains configured in the cloud instance.Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser.If you do, you receive a Page not found error.The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog). |
Chapter 2 Prerequisites for Creating a Connection 2-25 5.Map the token name for the service path value to the domain name in the Topology Manager: Token Name in Service Path Domain Name atf_server CommonDomain crm_server CRMDomain fin_server FinancialDomain hcm_server HCMDomain ic_server ICDomain prc_server ProcurementDomain prj_server ProjectsDomain scm_server SCMDomain 6.Expand the domain name and select any external virtual host and port for the J2EE applications that are deployed on the domain.In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser.If you do, you receive a Page not found error.The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows. |
In the sample window, the values for this particular instance are fs-your-cloud-hostname and 443, respectively.Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser.If you do, you receive a Page not found error.The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL. |
Chapter 2 Prerequisites for Creating a Connection 2-26 7.Replace the domainName _server :PortNumber with the external virtual host and port identified in the previous step.For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser.If you do, you receive a Page not found error.The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods. |
For example: https://fs-your-cloud-hostname:port/fndAppCoreServices/ServiceCatalogService?wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser.If you do, you receive a Page not found error.The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page. |
wsdl Obtain the Service Catalog Service WSDL For Release 12 To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser.If you do, you receive a Page not found error.The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center. |
For example: https://acme.fs.us2.oraclecloud.com/homePage/faces/FuseWelcome Where acme is the system name and fs is a Fusion Applications domain.2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser.If you do, you receive a Page not found error.The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL . |
2.Copy https://acme.fs.us2.oraclecloud.com/ and append fndAppCoreServices/ ServiceCatalogService?WSDL .For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser.If you do, you receive a Page not found error.The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint. |
For example: https://acme.fs.us2.oraclecloud.com/fndAppCoreServices/ ServiceCatalogService?WSDL Obtain the Event Catalog URL You must know the customer relationship management (CRM) URL format to access the CRM application user interface.Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser.If you do, you receive a Page not found error.The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13. |
Follow the URL format to determine the event catalog URL.For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser.If you do, you receive a Page not found error.The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available. |
For example, if the CRM URL format is: https://fusxxxx-crm-ext.us.oracle.com/customer/faces/CrmFusionHomeChapter 2 Prerequisites for Creating a Connection 2-27Then the event catalog URL is: https://fusxxxx-crm-ext.us.oracle.com/soa-infra The event catalog URL https:// host:port/soa-infra is a partial URL and must only be provided on the Connections page.Do not open this URL with a browser.If you do, you receive a Page not found error.The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated. |
Do not open this URL with a browser.If you do, you receive a Page not found error.The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated.You must specify the domain in the URL. |
If you do, you receive a Page not found error.The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated.You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows. |
The adapter does not access this URL directly.Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated.You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL. |
Instead, it automatically appends the required resource path to make the URL fully valid (when it needs to access the event catalog).To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated.You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement). |
To check the public events defined in the catalog, enter the following complete URL in a browser: https:// host:port/soa-infra/PublicEvent/catalog Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated.You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services. |
Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated.You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services. |
https:// host:port_for_the_common_domain /helpPortalApi/otherResources/latest/ interfaceCatalogs For Fusion Applications Releases 13 and Later Obtain the Oracle Fusion Applications Release 13 service catalog service WSDL, event catalog URL, or interface catalog URL through the following methods.Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated.You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services. |
Obtain the Service Catalog Service WSDL Obtain the Event Catalog URL Obtain the Interface Catalog URL Obtain the Service Catalog Service WSDL To obtain the physical endpoint of your instance, perform the following steps: 1.Log in to the Fusion Applications home page.For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated.You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services. |
For example: https://acme.fa.us6.oraclecloud.com/fscmUI/faces/FuseWelcome Where acme is the system name and us6 is the data center.2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated.You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services. |
2.Copy https://acme.fa.us6.oraclecloud.com/ and append it with fscmService/ ServiceCatalogService?WSDL .For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated.You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data. |
For example: https://acme.fa.us6.oraclecloud.com/fscmService/ServiceCatalogService?WSDLChapter 2 Prerequisites for Creating a Connection 2-28Obtain the Event Catalog URL Starting in Release 13, you access all Fusion Applications URLs using a consolidated endpoint.You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated.You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create . |
You must switch to the new consolidated endpoint that conforms to the following naming pattern: https:// systemName .fa.dcsn.oraclecloud.com/... You must switch to the consolidated endpoint immediately after upgrading to Release 13.Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated.You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.) |
Newly provisioned instances using Release 13 only have the consolidated endpoint available.In Release 13, multiple domains are consolidated.You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.) |
In Release 13, multiple domains are consolidated.You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection. |
You must specify the domain in the URL.For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search . |
For example, if specifying the fa domain, the URL looks as follows: 1.Copy the following URL: https://acme.fa.us6.oraclecloud.com/ 2.Append soa-infra to the end of the URL: https://acme.fa.us6.oraclecloud.com/soa-infra Obtain the Interface Catalog URL The interface catalog URL is formatted as follows.Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection. |
Obtain the host name in the same way as you obtained the host for the service catalog service WSDL.https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations. |
https:// host:port_for_the_common_domain /root_context /otherResources/latest/ interfaceCatalogs Where root_context is one of the following root context values: ERP/SCM pillar: fscmRestApi : for ERP/SCM REST services (includes PPM/Procurement).fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field. |
fscmService : for ERP/SCM non-REST services, such as SOAP services.HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ). |
HCM pillar: hcmRestApi : for HCM REST services.hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags). |
hcmService : for HCM non-REST services, such as SOAP services.CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page. |
CRM pillar: crmRestApi : for CRM REST services.crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both). |
crmServices : for CRM non-REST services, such as SOAP services.Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection. |
Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data.To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page. |
To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .Chapter 2 Create a Connection 2-292.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select. |
Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.)A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke . |
A basic routing integration (See Add a Trigger (Source) Connection.)3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error. |
3.In the Create Connection Select Adapter dialog, select the adapter to use for this connection.To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection. |
To find the adapter, scroll through the list, or enter a partial or full name in the Search field and click Search .4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create . |
4.In the Create Connection dialog, enter the information that describes this connection.a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created. |
a.Enter a meaningful name to help others find your connection when they begin to create their own integrations.The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group. |
The name you enter is automatically added in capital letters to the Identifier field.If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests. |
If you modify the identifier name, don't include blank spaces (for example, SALES OPPORTUNITY ).b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section. |
b.Enter optional keywords (tags).You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration. |
You can search on the connection keywords on the Connections page.c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed. |
c.Select the role (direction) in which to use this connection (trigger, invoke, or both).Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name. |
Only the roles supported by the adapter are displayed for selection.When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL. |
When you select a role, only the connection properties and security policies appropriate to that role are displayed on the Connections page.If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed. |
If you select an adapter that supports both invoke and trigger, but select only one of those roles, you'll get an error when you try to drag the adapter into the section you didn't select.For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration. |
For example, let's say you configure a connection for the Oracle Service Cloud (RightNow) Adapter as only an invoke .Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) . |
Dragging the adapter to a trigger section in the integration produces an error.d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token. |
d.Enter an optional description of the connection.5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section. |
5.Click Create .Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy to use. |
Your connection is created.You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter. |
You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username. |
Configure Connection Properties Enter connection information so your application can process requests.1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation. |
1.Go to the Connection Properties section.The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request. |
The fields that are displayed are based on your version of Oracle Integration.2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service . |
2.For new connections created with the initial release of the simplified connections page on 2/18/20, the Oracle CX Sales and B2B Service Host field is displayed.Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm. |
Enter the Oracle CX Sales and B2B Service host name.For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service . |
For example: https:// customer_chosen_domain_name .fa.DC.oraclecloud.comChapter 2 Create a Connection 2-30Note: The Oracle CX Sales and B2B Service host name can easily be derived from the Oracle CX Sales and B2B Service login URL.For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code. |
For example: https:// customer_chosen_domain_name.fa.DC.oraclecloud.com/fscmUI/faces/ FuseWelcome 3.For existing connections created prior to the initial release of the simplified connections page on 2/18/20, the URL fields are displayed.Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent. |
Specify the URLs to use in this integration.OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token. |
OSC Services Catalog WSDL URL OSC Events Catalog URL (optional) Interface Catalog URL (optional) For information about obtaining the URL, see 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) .Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token. |
Configure Connection Security Configure security for your Oracle CX Sales and B2B Service Adapter connection by selecting the security policy and security token.1.Go to the Security section.2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance. |
1.Go to the Security section.2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need. |
2.Select the security policy to use.Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need.Scopes limit access for the OAuth token. |
Element Description Username Password Token You receive the username and password to enter when subscribing to Oracle CX Sales and B2B Service Adapter.Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need.Scopes limit access for the OAuth token.They do not grant any additional permission beyond that which the user already possesses. |
Username : Enter the username.Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need.Scopes limit access for the OAuth token.They do not grant any additional permission beyond that which the user already possesses.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service. |
Password : Enter the password.Chapter 2 Create a Connection 2-31Element Description OAuth Authorization Code Credentials Client ID: Enter the client identifier (ID) issued during OAuth client application creation.The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need.Scopes limit access for the OAuth token.They do not grant any additional permission beyond that which the user already possesses.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service.Client Authentication : You can optionally configure OAuth flows with client authentication. |
The client ID identifies the client (the software requesting an access token) making the request.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need.Scopes limit access for the OAuth token.They do not grant any additional permission beyond that which the user already possesses.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service.Client Authentication : You can optionally configure OAuth flows with client authentication.This is similar to the Postman user interface feature for configuring client authentication. |
See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need.Scopes limit access for the OAuth token.They do not grant any additional permission beyond that which the user already possesses.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service.Client Authentication : You can optionally configure OAuth flows with client authentication.This is similar to the Postman user interface feature for configuring client authentication.Send client credentials as basic auth header: Pass the client ID and client secret in the header as basic authentication. |
Client Secret : Enter the client secret issued during OAuth client application creation, then enter it a second time to confirm.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need.Scopes limit access for the OAuth token.They do not grant any additional permission beyond that which the user already possesses.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service.Client Authentication : You can optionally configure OAuth flows with client authentication.This is similar to the Postman user interface feature for configuring client authentication.Send client credentials as basic auth header: Pass the client ID and client secret in the header as basic authentication.Send client credentials in body : Pass the client ID and client secret in the body as form fields. |
See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service .Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need.Scopes limit access for the OAuth token.They do not grant any additional permission beyond that which the user already possesses.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service.Client Authentication : You can optionally configure OAuth flows with client authentication.This is similar to the Postman user interface feature for configuring client authentication.Send client credentials as basic auth header: Pass the client ID and client secret in the header as basic authentication.Send client credentials in body : Pass the client ID and client secret in the body as form fields.When configuration is complete, perform the following steps: a.Click Provide Consent to test the OAuth flow. |
Authorization Code URI : Enter the URI from which to request the authorization code.This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need.Scopes limit access for the OAuth token.They do not grant any additional permission beyond that which the user already possesses.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service.Client Authentication : You can optionally configure OAuth flows with client authentication.This is similar to the Postman user interface feature for configuring client authentication.Send client credentials as basic auth header: Pass the client ID and client secret in the header as basic authentication.Send client credentials in body : Pass the client ID and client secret in the body as form fields.When configuration is complete, perform the following steps: a.Click Provide Consent to test the OAuth flow.b.If the Oracle Identity Cloud Service Oracle Integration and Oracle Fusion Applications users are different, log in to the respective instance when prompted.Chapter 2 Create a Connection 2-32Element Description Note: You are not prompted to log in if these users are the same. |
This endpoint is used to initiate the OAuth authentication and authorization process during which a user is directed to the OAuth server to provide credentials, to review granted permissions, and to provide consent.Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need.Scopes limit access for the OAuth token.They do not grant any additional permission beyond that which the user already possesses.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service.Client Authentication : You can optionally configure OAuth flows with client authentication.This is similar to the Postman user interface feature for configuring client authentication.Send client credentials as basic auth header: Pass the client ID and client secret in the header as basic authentication.Send client credentials in body : Pass the client ID and client secret in the body as form fields.When configuration is complete, perform the following steps: a.Click Provide Consent to test the OAuth flow.b.If the Oracle Identity Cloud Service Oracle Integration and Oracle Fusion Applications users are different, log in to the respective instance when prompted.Chapter 2 Create a Connection 2-32Element Description Note: You are not prompted to log in if these users are the same.c.Return to the Connections page and click Test. |
Access Token URI : Enter the URI to use for the access token.A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need.Scopes limit access for the OAuth token.They do not grant any additional permission beyond that which the user already possesses.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service.Client Authentication : You can optionally configure OAuth flows with client authentication.This is similar to the Postman user interface feature for configuring client authentication.Send client credentials as basic auth header: Pass the client ID and client secret in the header as basic authentication.Send client credentials in body : Pass the client ID and client secret in the body as form fields.When configuration is complete, perform the following steps: a.Click Provide Consent to test the OAuth flow.b.If the Oracle Identity Cloud Service Oracle Integration and Oracle Fusion Applications users are different, log in to the respective instance when prompted.Chapter 2 Create a Connection 2-32Element Description Note: You are not prompted to log in if these users are the same.c.Return to the Connections page and click Test.Note: If you receive an Unauthorized 401 error when testing your connection with a nonfederated user account, you may be logged in with the wrong user account. |
A request must be sent to this URI for obtaining an access token.Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need.Scopes limit access for the OAuth token.They do not grant any additional permission beyond that which the user already possesses.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service.Client Authentication : You can optionally configure OAuth flows with client authentication.This is similar to the Postman user interface feature for configuring client authentication.Send client credentials as basic auth header: Pass the client ID and client secret in the header as basic authentication.Send client credentials in body : Pass the client ID and client secret in the body as form fields.When configuration is complete, perform the following steps: a.Click Provide Consent to test the OAuth flow.b.If the Oracle Identity Cloud Service Oracle Integration and Oracle Fusion Applications users are different, log in to the respective instance when prompted.Chapter 2 Create a Connection 2-32Element Description Note: You are not prompted to log in if these users are the same.c.Return to the Connections page and click Test.Note: If you receive an Unauthorized 401 error when testing your connection with a nonfederated user account, you may be logged in with the wrong user account.See Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account . |
Scope: Enter the scopes specified during OAuth client application creation: The URL that corresponds to the federated Oracle Fusion Application instance.offline_access Scopes enable you to specify the type of access you need.Scopes limit access for the OAuth token.They do not grant any additional permission beyond that which the user already possesses.See Set Up the OAuth Authorization Code Credentials Security Policy with Oracle Identity Cloud Service.Client Authentication : You can optionally configure OAuth flows with client authentication.This is similar to the Postman user interface feature for configuring client authentication.Send client credentials as basic auth header: Pass the client ID and client secret in the header as basic authentication.Send client credentials in body : Pass the client ID and client secret in the body as form fields.When configuration is complete, perform the following steps: a.Click Provide Consent to test the OAuth flow.b.If the Oracle Identity Cloud Service Oracle Integration and Oracle Fusion Applications users are different, log in to the respective instance when prompted.Chapter 2 Create a Connection 2-32Element Description Note: You are not prompted to log in if these users are the same.c.Return to the Connections page and click Test.Note: If you receive an Unauthorized 401 error when testing your connection with a nonfederated user account, you may be logged in with the wrong user account.See Avoid Potential Errors When Testing Your Connection with a Nonfederated User Account .Test the Connection Test your connection to ensure that it's configured successfully. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.