Consuming Oracle Service Bus Proxy Services in Oracle JDeveloper with WSIL

Oracle Service Bus makes its WSDL-based proxy services available through the Web
Services Inspection Language (WSIL), letting you consume Oracle Service Bus WSDL
proxy services in Oracle JDeveloper for service orchestration in Oracle SOA Suite.
The Oracle Service Bus WSIL servlet automatically registers WSDL-based proxy
services deployed in the Oracle Service Bus run-time environment. By creating a WSIL
connection in JDeveloper, you can access those proxy services through different URL
patterns that map to different hierarchy levels, such as project, folder, and individual
service. For example, when you connect to the Oracle Service Bus WSIL servlet with a
project-level URL, you can see all the child folders and WSDL-based proxy services in
that project in Oracle JDeveloper.
The following procedure guides you through the process of creating a WSIL
connection in JDeveloper and generating Web service references out of Oracle Service

Bus WSDL proxy services for use in SOA applications

.

1. In Oracle JDeveloper, open or create a SOA application.
2. Create a new WSIL connection.
In the Resource Palette, click the New icon and choose New Connection > WSIL.
In the Create WSIL Connection window:
■ Enter the connection name.
See Section 2.1.1, "Resource Naming Restrictions" for naming guidance.
■ Enter the credentials for one of the following Oracle Service Bus roles:
IntegrationAdmin, IntegrationDeployer, IntegrationOperator, or
IntegrationMonitor.
■ Enter the URL to the Oracle Service Bus WSIL in one of the following formats:
– Domain (gets all projects, folders, and WSDL proxy services) –
http://host:port/sbinspection.wsil
– Project (gets all child folders and WSDL proxy services) –
http://host:port/sbinspection.wsil?refpath=project_name
– Folder (in a project, gets the folder, all child folders, and WSDL proxy
services) – http://host:port/sbinspection.wsil?refpath=project_name/folder_
path. For example:
http://localhost:7021/sbinspection.wsil?refpath=MortgageBroker/ProxyS
ervices
– Proxy Service (gets an individual WSDL proxy service) –
http://host:port/sbinspection.wsil?refpath=project_name/folder_path/wsdl_
proxy_service. For example:
http://localhost:7021/sbinspection.wsil?refpath=MortgageBroker/ProxyS
ervices/loanGateway1
In a cluster, the WSIL servlet is deployed on Managed Servers and not the
Admin Server. Use a Managed Server host name and port in the URL.
Working with Proxy Service Message Flows
2-16 Oracle Fusion Middleware Developer's Guide for Oracle Service Bus
When finished, click OK. The WSIL connection is displayed in the Resource
Palette in the hierarchy determined by the URL you entered.
3. To use an Oracle Service Bus WSDL proxy service in your SOA application, create
a Web service reference to it.
In the Component Palette, create a new Web service. In the Create Web Service
window, click the WSDL URL browse icon.
In the SOA Resource Browser, select Resource Palette, and select the Oracle
Service Bus WSDL proxy service in the WSIL connection created in the previous
step.
When you create the Web service reference to an Oracle Service Bus WSDL proxy
service, you can use it as an external reference in your SOA application.
The Oracle Service Bus WSIL servlet leverages the SBResource servlet. If the

SBResource is undeployed, the WSIL connection is not available

.