Tuesday Mar 26, 2013

Loading XAI Inbound Services in Oracle Service Bus

It is possible to use Oracle Service Bus to process interfaces to the Oracle Utilities Application Framework to support the advanced facilities available in Oracle Service Bus or simply use the proxy capbilities of Oracle Service Bus. This advice applies to Oracle Utilities Application Framework V2.2 and above.

The first step in this process is to import XAI Inbound Services into Oracle Service Bus:

  • When creating an XAI Inbound Service a WSDL is generated for the service and is listed on the XAI Inbound Service Maintenance screen. This should be noted as it will be used in Oracle Service Bus.
  • Logon to the Oracle Service Bus console (a.k.a. Change Center) and start an Edit Session. This will enable the ability to maintain configuration data within Oracle Service Bus.
  • Create or Navigate to a Folder within an Project to want to store the resources within Oracle Service Bus.
  • Create a Resource of type Resources from URL and specify the WSDL URL for the service as well as a Resource Name to be used to identify the resource within Oracle Service Bus and the Resource Type of WSDL. Use the Import feature to import the WSDL definition into Oracle Service Bus.
  • Remember to Activate your Edit session to apply the configuration.

Now that the WSDL is imported within Oracle Service Bus it can be used for various configuratoin activities within Oracle Service Bus including creating a Business Service. To create a Business Service you must do the following:

  • Logon to the Oracle Service Bus console (a.k.a. Change Center) and start an Edit Session. This will enable the ability to maintain configuration data within Oracle Service Bus.
  • Create or Navigate to a Folder within an Project to want to store the Business Service within Oracle Service Bus.
  • Create a Resource of type Business Service and specify the name and documentation for your service. In Service Type, select WSDL Web Service and select the WSDL you imported as the desired WSDL to use.
  • Select the Binding to Submit the configuration to specify the binding in the WSDL to use.
  • In the Transport Configuration screen specify HTTP protocol and the URI's you wish to use for the Business Service. By default the URI in the WSDL can be used but you alter this for your site as well as place a number of URI's in the configuration to support clustering the Business Service. If you use this facility remember to configure the Load Balancing Algorithm to your requirements on the same screen.
  • In the HTTP Transport configuaration screen, you need to specify the Authenticaton to use. You can specify the Basic configuration, by default, but it is recommended to set use the Policies facility in Oracle Service Bus as it seperates the security from the definition implemention. In this case, select None for Authentication. In this case, this tells Oracle Service Bus that security will be supplied externally. 
  • Fill in the rest of the configuration according to your requirements and save the Business Service.
  • Remember to Activate your Edit session to apply the configuration.

The Business Service is almost ready to use. We need to resolve the security settings. The preferred way is to create a credential in Oracle WebLogic using the named credentials as specified in XAI Best Practices (Doc Id: 942074.1) available from My Oracle Support. Once those are created they can be attached to the Business Service using this technique:

  • Logon to the Oracle Service Bus console (a.k.a. Change Center) and start an Edit Session. This will enable the ability to maintain configuration data within Oracle Service Bus.
  • Open the Business Service and navigate to the Policies Tab for the configuration.
  • Select OWSM Policies to indicate you want to use Oracle Web Services Manager policies.
  • Add the oracle/wss_username_token_client_policy to apply to the Business Service. Customers using SSL can use oracle/wss_username_token_over_ssl_client_policy instead.
  • Update the Business Service.
  • At this point you may see a save Conflict. This occurs if the default credential (named basic.credential) does not exist in Oracle WebLogic. You can resolve this by creating the basic.credential or changing the credential used to the one you created earlier. The latter can be resolved by editing the Business Service and navigating to the Security tab and specifying the name of the created credential in the Override Value. The conflict is resolved.
  • Remember to Activate your Edit session to apply the configuration.

The Business Service is now ready to be used within Oracle Service Bus. To verify you can use the Test Console to verify the transaction.

Note: When using the Test Console, it will default transactionType used in XAI Inbound Services to a value that may not be appropriate for your test. Ensure the value is correct before executing your test.

In the next few blog entries I will outline some additional features in Oracle Service Bus you can use with Oracle Utilities Application Framework.

About

Anthony Shorten
Hi, I am Anthony Shorten, I am the Principal Product Manager for the Oracle Utilities Application Framework. I have been working for over 20+ years in the IT Business and am the author of many a technical whitepaper, manual and training material. I am one of the product managers working on strategy and designs for the next generation of the technology used for the Utilities and Tax markets. This blog is provided to announce new features, document tips and techniques and also outline features of the Oracle Utilities Application Framework based products. These products include Oracle Utilities Customer Care and Billing, Oracle Utilities Meter Data Management, Oracle Utilities Mobile Workforce Management and Oracle Enterprise Taxation and Policy Management. I am the product manager for the Management Pack for these products.

Search

Archives
« March 2013 »
SunMonTueWedThuFriSat
     
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
27
28
29
30
31
      
Today