text
stringlengths 65
20k
|
|---|
The application is added as a confidential application.2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality. |
2.Complete the Details section, and go to the Client section.3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user. |
3.On the Client page, select Configure this application as a client now , and complete the following: a.Select Client Credentials from the Allowed Grant Types list.b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use. |
b.Select Specific in the Authorized Resources area of the Token Issuance Policy section.c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use.Validate the client application. |
c.Click Add Scope under the Resources section.d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use.Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload. |
d.Find the Oracle Utilities application.e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use.Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response. |
e.Add the scope containing access to either REST or SOAP APIs or both REST and SOAP APIs, and click >.Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use.Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs. |
Chapter 2 Authentication Support 2-12 f.Save your changes.4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use.Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service. |
4.Click through the remaining wizard pages without making changes and save the application.5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use.Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided. |
5.Activate the application for use.The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use.Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security . |
The next step is to create an application user in the appropriate Oracle Utilities Cloud Service (such as Oracle Utilities Meter Solution Cloud Service).Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use.Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail. |
Access the appropriate Oracle Utilities Cloud Service application, and navigate to the User portal.1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use.Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications. |
1.Create a new user corresponding to the OAuth Client created above: a.Enter the OAuth client ID as the users login ID.b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use.Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime. |
b.Select OAuth Client from the User Type drop-down list.c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use.Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper. |
c.Assign User Groups that provide the integration with access to the appropriate functionality.d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use.Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration. |
d.Assign To Do Roles and appropriate Access Security to the created user.The OAuth Client credentials are now ready to use.Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime. |
The OAuth Client credentials are now ready to use.Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time. |
Validate the client application.1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper. |
1.Fetch the access client to make a request to Oracle Identity Cloud Service with the client ID and client secret of the client in the payload.##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime. |
##Syntax curl -i -H 'Authorization: Basic <base64Encoded_clientid:secret>' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' -- request POST https://<IDCS-Service-Instance>.identity.oraclecloud.com/ oauth2/v1/token -d 'grant_type=client_credentials&scope=<App_Scope>' ###where #### <base64-clientid-secret> - Base 64 encode clientId:ClientSecret #### <app_scope> - Scope added while creating application in client configuration section ##Example curl -i -H 'Authorization: Basic OGQyM...ZDA0Mjcz' -H 'Content-Type: application/x-www-form-urlencoded;charset=UTF-8' --request POST https://<idcs_host>/oauth2/v1/token -d 'grant_type=client_credentials&scope=https://<Resource_APP_Audience>/ rest/*' 2.Capture the access_token from the response.{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values. |
{ "access_token": "eyJ4NXQjG...dfsdfsFgets2ed", "token_type": "Bearer",Chapter 2 Authentication Support 2-13 "expires_in": 3600 } 3.Use the access_token in the authorization header to invoke the Oracle Utilities Application APIs.curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke. |
curl --location --request GET 'https:// <Utilities_Application_API_ENDPOINT>' \ --header 'Authorization: Bearer eyJ4NXQjG...dfsdfsFgets2ed' 4.To update the access token when it is expired, make the same request to Oracle Identity Cloud Service.Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties . |
Authentication Types The Oracle Utilities Adapter supports the following types of authentication: Username password token Basic Authentication OAuth Client Credentials (two-legged flow) OAuth Resource Owner Password Credentials (two-legged flow) Additional information about these security policies is provided.See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema. |
See Configure Connection Security .Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane. |
Mapper Connectivity Properties Support The following section describes Oracle Utilities Adapter mapper connectivity property capabilities in more detail.Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping. |
Note: This support is only available for non-OUAF Applications.Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier. |
Set the Oracle Utilities Adapter Connectivity Properties in the Mapper Support for Dynamic REST Endpoints Set the Oracle Utilities Adapter Connectivity Properties in the Mapper You can set Oracle Utilities Adapter connectivity properties in the mapper to propagate additional information to the target endpoint during runtime.Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request. |
Connectivity properties (invoke request) You can set the following property for invoke requests in the mapper.Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration. |
Property Description ConnectionId The connection identifier value is passed to the mapping to fetch the respective connection details using the lookup for invoking a dynamic non-OUAF application during runtime.Chapter 2 Mapper Connectivity Properties Support 2-14 Support for Dynamic REST Endpoints The Oracle Utilities Adapter enables you to dynamically change the (invoke) outbound endpoint configuration.This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime. |
This feature is useful in the following scenarios: A REST endpoint must be invoked dynamically at runtime.An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default. |
An endpoint is not known at design time.To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request. |
To change the endpoint configuration at runtime, you must map the properties under ConnectivityProperties in the mapper.For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service. |
For example, the following steps describe how to configure an integration to invoke a REST endpoint determined at runtime: 1.Create multiple connections with the Oracle Utilities Adapter and configure each environment detail for non-OUAF applications that can be invoked during the runtime.2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration. |
2.Create a lookup having a key-value pair and configure the connection identifier values of the above created connections as identifier values.3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration. |
3.Create an integration adding any connection of the non-OUAF application on the invoke.4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears. |
4.In the target pane of the mapper, expand Plugin under ConnectivityProperties .These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details. |
These elements are made available automatically through a static schema that is added to the user-provided schema.5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details.4.Select the One-way service on the Request page. |
5.Using the source schema in the source pane, create a mapping to ConnectionId in the target pane.Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details.4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page. |
Alternatively, you can also provide a static mapping.The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details.4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously. |
The Oracle Utilities Adapter uses the ConnectionId provided by this mapping to determine the connection identifier configured in the lookup and fetch the connection details corresponding to this connection identifier.The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details.4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default. |
The respective REST endpoint is determined to which to route this request and the credentials to authenticate the request.6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details.4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support. |
6.Activate and invoke the integration.The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details.4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox. |
The Oracle Utilities Adapter now invokes the endpoint URI determined at runtime.Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details.4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support. |
Asynchronous Trigger Support in Orchestrated Integrations The web services you create have a request-response message exchange pattern (MEP) by default.In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details.4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled. |
In a request-response MEP in which the web service client invokes a method of the web service, the web service returns a response to the request.The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details.4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter. |
The Oracle Utilities Adapter allows you to configure a web service to use a one-way message exchange pattern in which the web service client only sends a request message, but does not receive a response from the web service.This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details.4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate. |
This is supported in the trigger (inbound) direction for both REST and SOAP endpoints.Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-15In the trigger direction, you must configure the Adapter Endpoint Configuration Wizard as follows: 1.Create an app-driven orchestrated integration.2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details.4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required). |
2.Add an Oracle Utilities Adapter as a trigger connection in the integration.The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details.4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration. |
The Adapter Endpoint Configuration Wizard appears.3.Configure the Basic Info page details.4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate . |
3.Configure the Basic Info page details.4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible. |
4.Select the One-way service on the Request page.5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server. |
5.Ensure that you configure the page as follows on the Response page.This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server. |
This ensures that the integration runs asynchronously.The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent. |
The Response Type is enabled as Request-Response by default.Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 . |
Disable the Request-Response checkout for one-way support.Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page. |
Once you disable the Request-Response checkbox, the Response page is not editable except for the Request-Response checkbox.No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted. |
No fault is accepted for one-way support.Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server. |
Therefore, the Send Faults selection is disabled.6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task. |
6.Click Next to access the Summary Page, then click Done .Chapter 2 Asynchronous Trigger Support in Orchestrated Integrations 2-163 Create an Oracle Utilities Adapter Connection A connection is based on an adapter.You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked. |
You define connections to the specific cloud applications that you want to integrate.Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server. |
Topics: Prerequisites for Creating a Connection Create a Connection Upload an SSL Certificate Prerequisites for Creating a Connection Before you set up the Oracle Utilities Adapter: Upload a trusted public certificate (if required).Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server. |
Typically, the certificate is included with Oracle Integration.See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application. |
See Upload an SSL Certificate .Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values. |
Make sure the Oracle Utilities server is running and accessible.Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create a Connection Before you can build an integration, you have to create the connections to the applications with which you want to share data. |
Know the host name address and port number of the Oracle Utilities server.Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create 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 . |
Know the user name and password used to access the Oracle Utilities server.Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create 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 .2.Click Create . |
Download the connectivity agent.See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create 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 .2.Click Create .Note: You can also create a connection in the integration canvas of: An orchestrated integration (See Define Inbound Triggers and Outbound Invokes.) |
See Download and Run the Connectivity Agent Installer in Using Integrations in Oracle Integration Generation 2 .OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create 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 .2.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.) |
OAuth Security Policies If you are using one of the OAuth security policies, you must already have registered your client application to complete the necessary fields on the Connections page.The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create 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 .2.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. |
The Basic Authentication and No Security Policy security policies are exempted.Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create 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 .2.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 . |
Before a client application can request access to resources on a resource server, the client application must first register with the authorization server associated with the resource server.The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create 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 .2.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. |
The registration is typically a one-time task.Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create 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 .2.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. |
Once registered, the registration remains valid, unless the client application registration is revoked.At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create 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 .2.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. |
At registration time, the client application is assigned a client ID and a client secret (password) by the authorization server.The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create 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 .2.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 ). |
The client ID and secret are unique to the client application on that authorization server.If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create 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 .2.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). |
If a client application registers with multiple authorization servers (for example, Facebook, Twitter, and Google), each authorization server issues its own unique client ID to the client application.@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create 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 .2.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. |
@ref: http://tutorials.jenkov.com/oauth2/authorization.html For OAuth configuration, read the provider documentation carefully and provide the relevant values.3-1Create 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 .2.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). |
3-1Create 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 .2.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. |
To create a connection in Oracle Integration: 1.In the left navigation pane, click Home > Integrations > Connections .2.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. |
2.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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter. |
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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section. |
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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section.2.Enter the SOAP-based catalog or REST web service catalog URL exposed by an OUAF application in the Catalog URL field and click OK. |
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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section.2.Enter the SOAP-based catalog or REST web service catalog URL exposed by an OUAF application in the Catalog URL field and click OK.The configured REST web service catalog should return only a list of REST inbound/ outbound services: Inbound services consist of REST Integrated Web Services (IWS). |
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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section.2.Enter the SOAP-based catalog or REST web service catalog URL exposed by an OUAF application in the Catalog URL field and click OK.The configured REST web service catalog should return only a list of REST inbound/ outbound services: Inbound services consist of REST Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender. |
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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section.2.Enter the SOAP-based catalog or REST web service catalog URL exposed by an OUAF application in the Catalog URL field and click OK.The configured REST web service catalog should return only a list of REST inbound/ outbound services: Inbound services consist of REST Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.The configured SOAP-based catalog should return only a list of SOAP inbound/outbound services: Inbound services consist of SOAP Integrated Web Services (IWS). |
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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section.2.Enter the SOAP-based catalog or REST web service catalog URL exposed by an OUAF application in the Catalog URL field and click OK.The configured REST web service catalog should return only a list of REST inbound/ outbound services: Inbound services consist of REST Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.The configured SOAP-based catalog should return only a list of SOAP inbound/outbound services: Inbound services consist of SOAP Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender. |
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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section.2.Enter the SOAP-based catalog or REST web service catalog URL exposed by an OUAF application in the Catalog URL field and click OK.The configured REST web service catalog should return only a list of REST inbound/ outbound services: Inbound services consist of REST Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.The configured SOAP-based catalog should return only a list of SOAP inbound/outbound services: Inbound services consist of SOAP Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.Configure Connection Security Configure security for your Oracle Utilities Adapter connection by selecting the security policy. |
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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section.2.Enter the SOAP-based catalog or REST web service catalog URL exposed by an OUAF application in the Catalog URL field and click OK.The configured REST web service catalog should return only a list of REST inbound/ outbound services: Inbound services consist of REST Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.The configured SOAP-based catalog should return only a list of SOAP inbound/outbound services: Inbound services consist of SOAP Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.Configure Connection Security Configure security for your Oracle Utilities Adapter connection by selecting the security policy.1.Go to the Security section. |
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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section.2.Enter the SOAP-based catalog or REST web service catalog URL exposed by an OUAF application in the Catalog URL field and click OK.The configured REST web service catalog should return only a list of REST inbound/ outbound services: Inbound services consist of REST Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.The configured SOAP-based catalog should return only a list of SOAP inbound/outbound services: Inbound services consist of SOAP Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.Configure Connection Security Configure security for your Oracle Utilities Adapter connection by selecting the security policy.1.Go to the Security section.2.Select a security policy, and then complete the fields. |
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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section.2.Enter the SOAP-based catalog or REST web service catalog URL exposed by an OUAF application in the Catalog URL field and click OK.The configured REST web service catalog should return only a list of REST inbound/ outbound services: Inbound services consist of REST Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.The configured SOAP-based catalog should return only a list of SOAP inbound/outbound services: Inbound services consist of SOAP Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.Configure Connection Security Configure security for your Oracle Utilities Adapter connection by selecting the security policy.1.Go to the Security section.2.Select a security policy, and then complete the fields.You must already have created your client application to complete the necessary fields. |
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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section.2.Enter the SOAP-based catalog or REST web service catalog URL exposed by an OUAF application in the Catalog URL field and click OK.The configured REST web service catalog should return only a list of REST inbound/ outbound services: Inbound services consist of REST Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.The configured SOAP-based catalog should return only a list of SOAP inbound/outbound services: Inbound services consist of SOAP Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.Configure Connection Security Configure security for your Oracle Utilities Adapter connection by selecting the security policy.1.Go to the Security section.2.Select a security policy, and then complete the fields.You must already have created your client application to complete the necessary fields.The following security policy restrictions apply when configuring a Utilities Adapter connection with the trigger and invoke role on the Connections page: If you select Basic Authentication, it can be used as a trigger and an invoke. |
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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section.2.Enter the SOAP-based catalog or REST web service catalog URL exposed by an OUAF application in the Catalog URL field and click OK.The configured REST web service catalog should return only a list of REST inbound/ outbound services: Inbound services consist of REST Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.The configured SOAP-based catalog should return only a list of SOAP inbound/outbound services: Inbound services consist of SOAP Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.Configure Connection Security Configure security for your Oracle Utilities Adapter connection by selecting the security policy.1.Go to the Security section.2.Select a security policy, and then complete the fields.You must already have created your client application to complete the necessary fields.The following security policy restrictions apply when configuring a Utilities Adapter connection with the trigger and invoke role on the Connections page: If you select Basic Authentication, it can be used as a trigger and an invoke.Agent configuration is not applicable on a connection with the trigger role. |
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.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section.2.Enter the SOAP-based catalog or REST web service catalog URL exposed by an OUAF application in the Catalog URL field and click OK.The configured REST web service catalog should return only a list of REST inbound/ outbound services: Inbound services consist of REST Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.The configured SOAP-based catalog should return only a list of SOAP inbound/outbound services: Inbound services consist of SOAP Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.Configure Connection Security Configure security for your Oracle Utilities Adapter connection by selecting the security policy.1.Go to the Security section.2.Select a security policy, and then complete the fields.You must already have created your client application to complete the necessary fields.The following security policy restrictions apply when configuring a Utilities Adapter connection with the trigger and invoke role on the Connections page: If you select Basic Authentication, it can be used as a trigger and an invoke.Agent configuration is not applicable on a connection with the trigger role.If you select OAuth Resource Owner security policy, it can only be used as an invoke. |
You're now ready to configure the connection details, such as connection properties, security policies, connection login credentials, and (for certain connections) agent group.Chapter 3 Create a Connection 3-2Configure Connection Properties You can consume the SOAP-based catalog or REST web service catalog provided by OUAF in the Oracle Utilities Adapter.1.Go to the Connection Properties section.2.Enter the SOAP-based catalog or REST web service catalog URL exposed by an OUAF application in the Catalog URL field and click OK.The configured REST web service catalog should return only a list of REST inbound/ outbound services: Inbound services consist of REST Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.The configured SOAP-based catalog should return only a list of SOAP inbound/outbound services: Inbound services consist of SOAP Integrated Web Services (IWS).Outbound services consist of the external system: the outbound message type for a real-time HTTP or JSON sender.Configure Connection Security Configure security for your Oracle Utilities Adapter connection by selecting the security policy.1.Go to the Security section.2.Select a security policy, and then complete the fields.You must already have created your client application to complete the necessary fields.The following security policy restrictions apply when configuring a Utilities Adapter connection with the trigger and invoke role on the Connections page: If you select Basic Authentication, it can be used as a trigger and an invoke.Agent configuration is not applicable on a connection with the trigger role.If you select OAuth Resource Owner security policy, it can only be used as an invoke.Dragging the connection to the trigger area causes an exception error to be displayed. |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.