This chapter contains the following topics:
Section 8.1, "Understanding JD Edwards EnterpriseOne as a Web Service Consumer"
Section 8.2, "Setting Up OCM for Business Functions Calling Business Services"
Section 8.3, "Developing a Business Service for Consuming an External Web Service"
Section 8.4, "Testing a Business Service That Consumes an External Web Service"
Section 8.6, "Creating a Web Service Proxy Using JDeveloper11g with a JAX-RPC Client"
Important:
Oracle reserves the right to reorganize the business services foundation packages (jar files) for tools release upgrades. If you are planning to upgrade your system, test your custom objects and modify them as appropriate to ensure your code will continue to work as intended. You cannot upgrade custom business service objects after you install a tools release upgrade.JD Edwards EnterpriseOne can call and process external web services. Being a native consumer of web services enables JD Edwards EnterpriseOne to integrate with other Oracle products and third-party systems and products, such as order promising. To enable JD Edwards EnterpriseOne as a web services consumer, you create a business service that uses a web service proxy to call an external web service. A method in that business service can be called by a JD Edwards EnterpriseOne business function. The business service resides on the business services server and is written in the Java programming language. The business service contains a web service proxy that you generate using JDeveloper. The business function resides in your enterprise server and is written in the C programming language. The business function calls the business service method.
The business function, which resides in your enterprise server, uses an API to call the business service method, which resides on the business services server. JDENet is the communication mechanism between the servers.
You can configure your system to use either one port or multiple ports to listen for and receive JDENet messages from the Enterprise Server. For single port communication, an Object Configuration Manager (OCM) mapping tells the enterprise server the business services server name and port for sending the JDENet messages.
See Setting Up OCM for Business Functions Calling Business Services.
For multiple port communication, you use a clustered business services server to listen for and receive multiple JDENet messages from the Enterprise Server.
These APIs are available for a business function to call a business service method:
jdeCallBusinessService
jdeCallBusinessServiceNoResponse
jdeFreeBSSVPayloadReturn
jdeGetBusinessServiceErrorText
Two APIs are available for calling a business service method from a business function:
jdeCallBusinessService
This API makes a synchronous call to the business services server passing in an XML document that represents the value object for the called business service method. The call waits until the business service method finishes before processing.
jdeCallBusinessServiceNoResponse
This API makes an asynchronous call to the business services server passing in an XML document that represents the value object for the called business service method. The API returns immediately after sending the message without waiting for a response.
For both of these APIs, the caller must allocate the bssvPayloadInput structure. In addition, the caller must free the bssvPayloadReturn structure with the provided API.
This example code provides a typical C business function call to a business service method:
* jdeCallBusinessService (lpBhvrCom,
* lpVoid,
* _J("oracle.e1.sbf.JXXXXX")
* _J("bssv_method_name_to_call")
* TRUE,
* bssvPayload,
* &bssvPayloadReturn);
*
* /* caller must free the space allocated for the return payload when
* finished with it */
* jdeFreeBSSVPayloadReturn (&bssvPayloadReturn);
*
Both APIs take the same set of parameters, which is shown in this example code:
* lpBhvrCom - BSFN structure pointer. * lpVoidInfo - holds error info returned from BSFN. * bssvName - fully qualified name of business service to be called * bssvMethod - method within business service to be called * autocommitTransaction - type of transaction the business service should use * on the business services server. * True if auto commit - False for manual commit. * bssvPayloadInput - string representation of an XML document that represents * the value object for the business service. Populated * with input values to pass to the business service. * bssvPayloadReturn - string representation of XML document representing the * value object returned from the business service call * populated with both return values and original input * values. The caller must free the space allocated for * the return payload by calling the * jdeFreeBSSVPayloadReturn API.
Both APIs have the same return values, which are shown in this example code:
* CallBSSVNoError 100L * CallBSSVServiceDoesNotExist 101L * CallBSSVMethodDoesNotExist 102L * CallBSSVInvalidMethodSignature 103L * CallBSSVNoDefaultConstructor 104L * CallBSSVErrorUnMarshal 105L * CallBSSVErrorMarshal 106L * CallBSSVConnectionException 107L * CallBSSVInvalidPacketNum 108L * CallBSSVInvaldUserName 109L * CallBSSVInvalidEnv 110L * CallBSSVInvalidRole 111L * CallBSSVInvalidToken 112L * CallBSSVAuthenticationFailure 113L * CallBSSVNoErrorWithMessages 114L * CallBSSVInvalidParamError 201L * CallBSSVSystemConfigurationError 202L * CallBSSVSystemNetworkFailedError 203L * CallBSSVSystemInternalServerError 204L
See Also:
JD Edwards EnterpriseOne Tools API Reference Guide on the My Oracle Support Web site.
You can use any one or more Xerces APIs in combination with other XML generation and editing APIs to generate the XML payload for calls to a business service. You can use any of these Xerces APIs, which have been added to the Xerces wrapper:
Xerces APIs for working with MathNumeric data types:
XRCS_createElementFromMathNumeric
XRCS_setMathNumericElementValue
XRCS_getMathNumericFromElement
Xerces APIs for working with JDEDATE data types:
XRCS_createElementFromJDEDate
XRCS_setJDEDateElementValue
XRCS_getJDEDateFromElement
Xerces APIs for working with JDEUTIME data types:
XRCS_createElementFromJDEUTIME
XRCS_setJDEUTIMEElementValue
XRCS_getJDEUTIMEFromElement
Xerces APIs for parsing/serialization ignoring encoding tags:
XRCS_serializeDocumentToXMLStringNoEncoding
XRCS_parseXMLStringRemoveEncoding
See Also:
JD Edwards EnterpriseOne Tools API Reference Guide on the My Oracle Support Web site.
This section provides an overview of setting up OCM for business functions calling business services and discusses how to:
Configure OCM for business functions calling business services.
Ping the business services server.
Typically, a system administrator configures OCM so that your enterprise server can find the business services server. After OCM is configured with the business services server information, you can ping the business services server from OCM to ensure that the business services server is running and listening for messages.
| Form Name | FormID | Navigation | Usage |
|---|---|---|---|
| Machine Search and Select | W986110D | Expand the System Administration Tools folder on the EnterpriseOne Life Cycle Tools / All My Roles menu, and then select Environment / Service Configuration from the Environment Management folder. | Select the appropriate machine name and data source combination. |
| Work with Service Configurations | W986110J | On Machine Search and Select, select the machine name and data source combination and then click Select. | Find and select an existing configuration for the business services server and server port, or access the Service Configuration Revisions form to add a new configuration record. Also ping the business services server to determine whether the business services server is available. |
| Service Configuration Revisions | W986110K | On Work with Service Configurations, click Add. | Add a new configuration in OCM with the location of the business services server. |
Access the Service Configuration Revisions form and complete the following fields:
A name that uniquely identifies the environment.
A name that identifies the type of server. For example, BSSV identifies the business services server.
A specific JD Edwards EnterpriseOne user name, role name, or *PUBLIC to whom the record applies.
The name of the local host where the business services server is running.
The port number of the business services server. This is the JDENet listening port.
Access the Work with Service Configurations form.
In the grid area, highlight the server.
From the Row menu, select Change Status to activate the configuration.
From the Row menu, select Ping Server.
You receive a Ping message indicating whether the Ping test was successful or failed.
This section provides an overview of how to develop a business service for consuming an external web service and discusses how to:
Identify an external web service.
Create a business service object.
Create a web service proxy prior to JDeveloper 11g.
Create a web service proxy for a web service deployed in WebLogic Server using JDeveloper 11g with JAX-RPC.
Create a value object class.
Create a business service class.
Generate a sample XML document.
You create a business service that consumes an external web service in the same way that you create a business service that provides a web service for public consumption. But instead of using a published business service as the web service, the business service is used to consume the web service. As part of the process, you create a web service proxy and an XML document. This business service is called by a business function. The following tasks provide a scenario for creating a JD Edwards EnterpriseOne business service that consumes an external web service.
Important:
If you are using JD Edwards EnterpriseOne Tools Release 9.2 with JD Edwards EnterpriseOne Applications Release 9.2, JDeveloper 12c is installed on your system. With JDeveloper 12c, you can create only JAX-WS business services.If you are using JDeveloper 12c, do not use JDK 1.7 specific APIs in any of the published business services code.
If you are using JD Edwards EnterpriseOne Tools Release 9.2 with JD Edwards Enterprise One Applications Release 9.0 or 91, JDeveloper 11g is installed on your system. With JDeveloper 11g, you can create JAX-WS and JAX-RPC business services.
Before you create a business service to consume an external web service, you need to identify the external web service and its location. The external web service definition determines the data to be sent to the web service and the result that is received.
Using Object Management Workbench (OMW), create the object that will contain the business service being developed. Start JDeveloper from OMW to work with this project.
A web service proxy is a collection of classes generated by JDeveloper and is used to call external web services. JDeveloper uses the target WSDL to create all necessary classes. A JD Edwards EnterpriseOne business service method uses the web service proxy to call the external web service. You use JDeveloper to create a web service proxy in the business service project that you created using OMW.
When you create a new business service proxy project in JDeveloper to consume a web service running on the WebLogic Server (WLS), JDeveloper includes certain XML files in the proxy project. When you check in the business service proxy project through OMW, the XML files in the proxy project must also be checked in as part of the project.
To be able to check in XML files along with the business service consumer projects through OMW, ensure that the UDC H95/CA includes records for XML files as business services artifacts that can be checked in.
Ensure that any new business service proxy project created in JDeveloper to consume a web service is checked in through OMW with the JDeveloper install path specified as the JDeveloper install path.
After JDeveloper creates the web service proxy, you must rename the package folder, and then rebuild the code to ensure that no errors occurred.
For more information about creating a web service proxy, see one of the following:
After you create the web service proxy, you create the value object class. You create the value object class based on data objects in the JD Edwards EnterpriseOne business function that will be used to call this business service. Then, you must write the code to map between data types in the value object class and the data types required by the external web service.
You design your business service method so that it gets the data that will be passed to the web service from either the business services server or the enterprise server. When you design your business service method, you need to consider the amount of data being passed. The more data that is passed to the business service method, the larger the memory requirements are on the enterprise server. Consuming memory on the enterprise server can significantly impact other users of the enterprise server. Creating the value object that is passed to the business service method requires careful consideration. Here are some questions you might consider:
Is it better to assemble the data from the business services server instead of the enterprise server?
Can key information be passed instead of constructing the entire data set on the C (enterprise server) side?
Is one approach clearly better than the other based on the requirements?
Depending on your business service design, data is either received in the business service value object, or the business service retrieves the data from a table or business function call. Either way, data type conversions occur within the business service method. Everything that is specific to the web service being called, including data type conversions, should be contained within the business service method that wraps the web service call.
After you create the web service proxy and the value object class, you create a business service class. This business service is a wrapper for the web service proxy. The business service wrapper is necessary because:
Only internal business services that match the JD Edwards EnterpriseOne business service methodology can be called from the enterprise server.
Most likely some conversion between the JD Edwards EnterpriseOne data types and the data types required by the web service provider will be required.
To create a business service class:
Add classes to the business service object.
Create the business service class.
Name the business service class.
Create a transaction, if necessary (IConnection object).
Declare a business service public method.
Add business service logic:
Map from the value object to the format needed by the external web service.
Create a call to the web service proxy.
Use business service properties.
Use softcoding.
Handle errors.
Format data.
After you create the business service for calling an external web service, you can create a JD Edwards EnterpriseOne business function that calls this business service. You can also create or use an existing JD Edwards EnterpriseOne application to call the business function.
You use the XML Template utility to create a sample XML document. The sample XML document is based on the value object of the business service method that is calling an external web service. This XML document provides a model for creating the XML payload in the JD Edwards EnterpriseOne business function. The XML document represents the structure of the data that is sent from the business function. The XML Template utility is provided in JDeveloper, and you access the utility by selecting a value object Java file in the JDeveloper Application Navigator pane.
To invoke the XML Template utility that generates a sample XML document:
Start JDeveloper from OMW.
In the JDeveloper navigator pane, right-click the value object of the business service method that you want to call.
Select Generate XML Document Template from the context menu.
The XML Template utility creates a new XML file in the same directory as the value object. The XML file has the same name as the value object, with an extension of XML instead of Java.
Click the refresh icon in the JDeveloper navigator pane.
Open the sample XML document by double-clicking the new XML file.
If you are using JDeveloper 12c to create a business service that consumes an external web service, you use the JDeveloper 12c integrated WebLogic Server to test the web service.
If you are using JDeveloper 11g or JDeveloper 12c to create a business service that consumes an external web service, you can use the JDeveloper integrated WebLogic Server to test the web service.
See the following sections in this guide to deploy and test the business service consumer project:
Creating a Deployment Profile for the Business Service Consumer Project
Deploying the Business Service Consumer Project to the Integrated WebLogic Server
You can test the business service using one of these methods:
Create a test business service.
Use the development business services server.
Guidelines for using these methods are provided in Appendix B: Testing a Business Service That Calls an External Web Service.
See Also:
You use OMW to create a new business service object, and then open the business service object in JDeveloper from OMW. Before you create the business service, ensure that the target JAX-WS web service for which the JAX-WS-based EnterpriseOne client business service is being developed is up and running and its WSDL URL is accessible.
A JAX-WS based EnterpriseOne Consumer business service reference implementation, JRH90I34, is provided for you to use as a model for creating a custom JAX-WS based consumer business service.
Note:
If you are using JD Edwards EnterpriseOne Tools Release 9.2 with JD Edwards Enterprise One Applications Release 9.0 or 9.1, and you plan to generate a web service based on the JAX-WS standard, it is important to consider your current consumption of the service. While the services function in the same manner, whether deployed as JAX-RPC or JAX-WS, there are some important caveats:The service wsdl for a service generated as JAX-WS differs from the same service wsdl generated as JAX-RPC.
If you currently interact with these services from an external system you may need to make changes to those systems before switching to JAX-WS.
For prepackaged integrations that use internal consumer services, you may need to maintain a JAX-RPC based deployment for them to function correctly.
See the specific EnterpriseOne applications guide for your integration to view the supported BSSV deployment options.
See the technical paper, "Understanding the Impact of JAX-WS", on My Oracle Support (Doc ID 1488986.1) https://support.oracle.com/rs?type=doc&id=1488986.1 for additional information about the implications of the JAX-WS build option.
You use the JDeveloper wizard to create a custom JAX-WS web service consumer.
To select JAX-WS as the standard for creating the JAX-WS based business service consumer project:
In JDeveloper, right-click on the appropriate business service consumer project and select Project Properties.
The Project Properties window for the selected published business service appears.
In the left-hand side tree structure, select Libraries and Classpath.
The Libraries and Classpath page appears on the right-hand side of the window.
In the Classpath Entries area, select JAX-WS Web Services.
Move the JAX-WS Web Services entry to the top of the page by clicking the Move Up button
Clicking the Move Up button moves the entry one level at a time; you may need to click the Move Up button multiple times to move the JAX-WS Services entry to the top of the page.
Click OK.
On JDeveloper, save the changes that you made to the Libraries and Classpath property of the selected published business service.
To create a JAX-WS Web Service Proxy:
In JDeveloper, right-click on the appropriate business service client project and select New to open the New Gallery Window.
On the New Gallery window, select the All Technologies tab.
In the left-hand tree structure, expand the Business Tier category and select Web Services.
Select Web Service Proxy from the list of items that appears in the right-hand pane.
Click OK.
This action opens the Create Web Service Proxy Wizard.
On the Welcome page click Next to open the Select Web Service Description page.
On Select Web Service Description, do the following:
In the WSDL Document URL field, enter the WSDL URL of the targeted JAX-WS based web service.
The WSDL URL is that of the targeted business service that is running on the JDeveloper 11g integrated WebLogic server.
Select the Copy WSDL Into Project option
Note:
If you are using JDeveloper 12c to create a JAX-WS based consumer web-service, a customization file must be used to prevent the WSIMPORT tool from flattening the web service input arguments.Create a customization file like this:
<?xml version='1.0' encoding='UTF-8'?>
<jaxws:bindings xmlns:xsd="http://www.w3.org/2001/XMLSchema"xmlns:jaxb="http://java.sun.com
/xml/ns/jaxb" xmlns:jaxws="http://java.sun.com/xml/ns/jaxws"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
wsdlLocation='your WSDL location/URL'>
<jaxws:enableWrapperStyle>false</jaxws:enableWrapperStyle>
</jaxws:bindings>
On the Select Web Service Description page, select the Customization Files option, and then select Add File.
Browse to the customization file you created and add the customization file to the client creation process.
Click Next to open the Specify Default Mapping Options page.
On specify Default Mapping Options, do the following:
Enter the business service project name package in the Package Name field; for example, oracle.e1.bssv.JRH90I34.proxy
Enter the business service proxy type in the Root Package for Generated Types field; for example, oracle.e1.bssv.JRH90I34.proxy.types
Click Next to open the Port Endpoints page.
On Port Endpoints, do the following:
Verify the system-entered endpoint URL of the targeted JAX-WS based web service.
Click Next to open the Asynchronous Methods page.
On Asynchronous Methods, select the Don't generate any asynchronous methods option.
On the Policy page, click Next to open the Defined Handlers page.
This page is optional. In this task, a JAX-WS client is being created for the web service running locally, which does not have any security configured. However, if you are creating a JAX_WS client for a web service that is secured with an OWSM policy, select the appropriate policy from the list that appears in the Security tab.
On Defined Handlers, accept the system entered information and then click Next to open the Finish page.
On Finish, click the Finish button to complete the creation of the JAX-WS business service client proxy.
After the proxy is successfully generated, expand the JAX-WS business service client project in JDeveloper. A folder named Proxy contains the classes required by the proxy to invoke the target web service. This folder also contains a types folder that has all of the classes that are used by proxy to invoke the operations of the target web service.
Next step is to create the *Processor.java class to invoke the target JAX-WS web service. In the client RI JRH90I34, refer to the RI_JAXWS_ABWebServiceProcessor.java to see how the Processor class has been coded to invoke the target JAX-WS web service. The RI_JAXWS_ABWebServiceProcessor.java has been coded in such a way so that the same JAX-WS client works against a target RI_AddressBookManager JAX-WS web service running on Jdeveloper 11g's Integrated WLS, Standalone WLS or WAS.
Note the following points regarding the code in the RI_JAXWS_ABWebServiceProcessor.java class:
Fetch the endpoint URL of the target web service from the softcoding record.
If the web service is secure, also retrieve user name and password credentials from the softcoding record
If the target web service is secured with WS-Security and it requires username and password credentials to be passed to the SOAP header from the client, do the following
Create a class that implements the SOAPHandler interface to create the WS-Security Header with the username and password credentials retrieved from the softcoding record.
Create a class that implements the HandlerResolver interface, which ensures that the class that implements the SOAP Handler interface is called.
Create an instance of the SOAPHandler class in the client Processor class, and set the username and password credentials retrieved from the softcoding record in this instance.
Create an instance of the HandlerResolver class in the client Processor class, add the instance of the SOAPHandler class to this instance.
Add the instance of the HandlerResolver class to the instance of the target web service.
Set the endpoint URL, user name, and password credentials retrieved from the softcoding record in the RequestContext object of the target web service.
Note:
In the RI-JAXWS_ABWebServiceProcessor.java class, the HeaderHandler class implements the SOAPHandler interface and is used to create the WS-Security Header with the user name and password credentials retrieved from the softcoding record. The HeaderHandlerResolver class implements the HandlerResolver interface and is used to call the HeaderHandler class.After you create the business service consumer project, you deploy it to the integrated WebLogic server. Before you can deploy the business service consumer project to the Integrated WebLogic server, you create a deployment profile. You use JDeveloper to create a deployment profile for the business service consumer project.
To create a deployment profile:
On JDeveloper, right-click on the appropriate business service consumer project and select Project Properties.
On Project Properties, do the following:
Select the deployment property.
Select Use Project Settings as the Deployment option.
Select the business service consumer project in the Development Profiles area.
Click Edit.
This action opens the Edit WAR Deployment Profile Properties window.
On Edit WAR Deployment Profile Properties, in the tree structure, select File Groups, and then click the New button.
On the File Groups page, create a new file group by doing the following:
Type WEB-INF in the File Group Name field.
Select the Packaging option as the Type of file group.
Click OK.
The WEB-INF file group appears in the tree structure, and the WEB-INF page opens in the right-side pane.
On WEB-INF, do the following:
Type WEB-INF in the Target Directory in the Archive field.
Type WEB-INF in the File Group Name field.
Click OK.
In the tree structure WEB-IN file Group, select Contributors.
In the Contributors pane, do the following:
Select the Project Output Directory option.
Select the Project Dependencies option
In the Order of Contributors field, add the path for the Consumer WEBXML folder; such as, <E1_Install_Path>\system\classes\ConsumerWEBXML.
In the tree structure WEB/INF file group, select Filters.
In the Filters pane, select the Filters tab and do the following:,
Select web.xml.
Clear check marks from of the other folders that are under the main folder, Merged Contents of This File Group's Contributors.
Click OK.
In the tree structure pane, expand the WEB-INF/lib file group and select Contributors.
In the Contributors pane, select the SBFProjects in the Libraries Selected for Deployment area, and click OK.
In the tree structure pane WEB-INF/lib file group, select Filters.
In the Filters pane, select the Files tab and ensure that all of the EnterpriseOne tools foundation jar files are selected, and then click OK.
In the tree structure pane, expand the WEB-INF/classes file group and select Contributors.
In the Contributors pane, do the following:
Select the Project Output Directory option.
Select the Project Dependencies option.
In the Order of Contributors area, add the SBF path; such as, <E1_Install_Path>\<PathCode>\ini\sbf.
Click OK.
In the tree structure pane WEB-INF/classes file group, select Filters.
In the Filters pane, select the Files tab and do the following:
Verify that all of the preconfigured EnterpriseOne files (.ini, .properties, .xml, .ora) are selected.
Expand the oracle folder and verify that only the targeted business service consumer project is selected.
Click OK.
In the tree structure pane, select the Library Dependencies group file.
In the Library Dependencies pane, ensure that all of the libraries under the Libraries Selected for Deployment area are selected and click OK
In the tree structure pane, expand the Platform group file.
In the Platform pane, do the following:
Select Weblogic 12.1.x (for JDeveloper 12c) or Weblogic 10.3 (for JDeveloper 11g) from the Default Platform drop-down list.
Select IntegratedWebLogicServer from the Target Connection drop-down list.
Click OK to open the Deployment window.
On the Deployment window, click OK.
On JDeveloper, save the changes to the targeted business service consumer project.
After you create the deployment profile, deploy the targeted business service consumer project to the integrated WebLogic server.
To deploy the business service consumer project to the Integrated WebLogic server:
Start the Integrated WebLogic server.
On JDeveloper, right-click on the appropriate business service consumer project, select Deploy, and then select the targeted business service consumer project to deploy to the integrated WebLogic server.
Ensure deployment of the business service consumer project is successful by verifying the Deployment Finished message that appears in the Deployment-Log window in the Deployment tab in JDeveloper.
You test your custom business service consumer project in the JDeveloper 11g integrated WebLogic server. The following list identifies additional tasks that you perform before testing your custom business service consumer project.
The target web service for which the business service consumer project is created is up and running.
The business service consumer project is successfully deployed and running in the JDeveloper 11g integrated WebLogic server.
Create a business function that calls your custom business service consumer project.
Add an OCM record for the Enterprise server to point to the business service server on which your custom business service consumer project is running.
Add a SYSTEM level service property.
Create a soft coding record.
Restart the Business Services server.
After you perform the additional tasks, restart the business services server where the business service consumer project is running. If the business service consumer project is running locally on the JDeveloper 11g integrated WebLogic server, then restart the integrated WebLogic Server.
Log into an EnterpriseOne Web client, and run the test reference implementation AddressBook application, P954001.
Note:
You can use reference implementation JRH90I34 (for JAX-WS) or JRH90I33 (for JAX-RPC) as a model for testing your web service proxy. The reference implementation provides set up information for the additional tasks that is specific for the reference implementation.See "Reference Implementation for Testing the Business Services Server as a JAX-WS Web Service Consumer" in the JD Edwards EnterpriseOne Tools Interoperability Reference Implementations Guide for more information about Reference Implementation JRH90I34.
See "Downloading and Deploying the JDeveloper 11g Reference Implementation Business Service for WebLogic Server" in the JD Edwards EnterpriseOne Tools Interoperability Reference Implementations Guide for information about Reference Implementation JRH90I33.
Note:
If the target web-service (JAX-WS consumer JRH90I34 is deployed to the integrated WLS of JDeveloper 12c) is secured with SSL, then in the Integrated WLS start script (startWebLogic.cmd), add the following argument to the JAVA_OPTION jvm arguments to ignore host name verification.-Dweblogic.security.SSL.ignoreHostnameVerification=true
The following is an example:
set JAVA_OPTIONS=%JAVA_OPTIONS% -Dweblogic.security.SSL. ignoreHostnameVerification=true
typically the start script startWebLogic.cmd is at this location:
C:\Users\<user_name>\AppData\Roaming\JDeveloper \<system>\DefaultDomain\bin\startWebLogic.cmd
If you have any issues while testing the consumer business service scenario, configure the following logs:
BSSV log.
Use the jdelog.properties file in <E1_Install_Path>\ini\sbf folder if the JAX-WS consumer reference implementation is running locally on the JDeveloper 11g integrated WebLogic server.
Jde and JdeDebug logs in local or for the COK on the Enterprise server, depending where business function B953002 is running.
IntegratedWeblogicServer log, which is located at:
C:\Documents and Settings\USER_PROFILE\Application Data\JDeveloper\<system>\DefaultDomain\servers\DefaultServer\logs
You can create a proxy that consumes a web service that is deployed in the WebLogic server. This section explains how to create the proxy in the development environment.
To select JAX-RPC as the standard for a business service consumer project:
In JDeveloper, right-click on the appropriate business service consumer project and select Project Properties.
The Project Properties window for the selected business service consumer project appears.
In the left-hand side tree structure, select Libraries and Classpath.
The Libraries and Classpath page appears on the right-hand side of the window.
In the Classpath Entries area, select JAX-RPC Web Logic Client and JAX-RPC 11 Web Services.
Move the JAX-RPC Web Logic Client and JAX-RPC 11 Web Services entries to the top of the page by clicking the Move Up button
Clicking the Move Up button moves the entry one level at a time; you may need to click the Move Up button multiple times to move the entries to the top of the page.
Click OK.
On JDeveloper, save the changes that you made to the Libraries and Classpath property of the selected business service consumer project.
To create a web service proxy:
From OMW, open JDeveloper 11g.
Under the BSSV package (created for the proxy project), create a subfolder named Proxy.
For example, Oracle uses the following package structure for reference implementations:
oracle.e1.bssv.JRH90I33.proxy
Select the OMW project and then open the project properties.
Add the proxy path that corresponds to the package structure in the java source path.
For example, the following structure might be added to the java source path:
c:\e812\DV812\Java\source\oracle\e1\bssv\ JRH90I33\proxy
Select the BSSV package for which you want to create a proxy, and then click File, and then click New.
On New Gallery, select All Technologies from the drop-down menu.
Expand the Business Tier category, and then select Web Services.
In the Items pane, select Web Services Proxy, and then click OK.
The Create Web Service Proxy wizard opens.
On the Welcome page, click Next.
If you receive a prompt to select a web service option, select JAX-RPC, and then click OK.
Enter the web service URL address.
On the Specify Default Mapping Option page, enter the package name or select the name using the Browse button.
For example, to use the JRH90I33 reference implementation, select oracle.e1.bssv. JRH90I33.proxy.
Click Next.
Select the name of the service that you want to call, and then click Next.
Verify that the default options are selected on the remaining pages, and then click Finish.
Select the newly created proxy folder.
This folder is the destination folder for the files that are created.
The proxy files are created.
You can compile and build the project you have created.
To rearrange and rename packages:
Locate the folder path "proxy\oracle\e1\bssv\JRH90I33\proxy" in the project folder.
After you copy the files, ensure that you cross check that the package name and the folder structure match.
Select the newly created projects in which you place your newly created proxy files in OMW.
Select the value object java files that have been generated under the proxy folder.
Rename the value object files package name and place it in the appropriate folder.
You can use the JDeveloper refactor option to change the package name and place the files in the corresponding folder.
For example, select jpr01000.bssv.e1.oracle.RI_Address and click Refractor. Then, change the package name to:
oracle.e1.bssv.JRH90I33.proxy.valueobject.oracle.e1.bssv.jpr01000.valueobject.RI_Address
Check for all references and change the package structure as appropriate.
Compile the project and rebuild the code to ensure no error has occurred.
Note:
To test your business service, see Testing the Business Service Consumer Project