1. Developing SOA Applications with Oracle SOA Suite
  2. Using Binding Components
  3. Getting Started with Binding Components
  4. Creating Tokens for Use in the Binding URLs of External References

Creating Tokens for Use in the Binding URLs of External References

You can create tokens in Oracle JDeveloper for the HTTP protocol, host, and port values in the binding URLs of external references. The values that you assign to the tokens are then substituted in place of the hardcoded HTTP host and port values in the location attribute of the binding.ws element of the composite.xml file.

For example, the following code shows the location attribute with hardcoded values for protocol (http), host (host.us.example), and port (80). 

<binding.ws
port="http://www.globalcompany.example.com/ns/CreditAuthorizationService#wsdl.
endpoint(CreditAuthorizationService/CreditAuthorizationPort)"
location="http://host.us.example:80/apps/FusionOrderDemoShared/services/
creditAuthorization/CreditAuthorizationService.wsdl">

The following example shows the location attribute after the creation of tokens. 

<binding.ws
port="http://www.globalcompany.example.com/ns/CreditAuthorizationService#wsdl.
endpoint(CreditAuthorizationService/CreditAuthorizationPort)"
location="${protocol}://${host1}:${port1}/apps/FusionOrderDemoShared/services/
creditAuthorization/CreditAuthorizationService.wsdl">

Note:

  • You can only use tokens in the location attribute of the binding.ws element of the composite.xml file.

  • You cannot use tokens for the protocol, host, and port values in other files, such as WSDL files, schema files, and so on.

  • Oracle JDeveloper only updates token files on the local file system that include the token values. If you use a local token file at design time, you must move the tokens to the SOA server at runtime. For information about creating tokens during runtime, see Administering Oracle SOA Suite and Oracle Business Process Management Suite.