Configuring Reference Implementation JRH90I34 for Testing the JAX-WS Web Services Consumer Scenario

After you set up the prerequisites, you must perform these tasks before you can use the P954001 test program to run the getAddressBook operation of the JAX-WS web service RI_AddressBookManager using the JAX-WS consumer business service JRH90I34.

Open the JRH90I34 business service project in JDeveloper 11g from OMW.
Create and save a deployment profile for the JRH90I34 project.
See "Creating a Deployment Profile for the Business Service Consumer Project" in the JD Edwards EnterpriseOne Tools Business Services Development Guide
Start the integrated WebLogic server.
Deploy the updated JRH90I34 project to the integrated WebLogic server.
See "Deploying the Business Service to the Integrated WebLogic Server" in the JD Edwards EnterpriseOne Tools Business Services Development Guide
Setup and activate an OCM record for the enterprise server to point to the business services server.
The EnterpriseOne Web client user must have authority to work with the OCM application.
- On the EnterpriseOne Web client, type GH9011 in the Fast Path.
- Expand System Administration Tools, right click on Object Configuration Manager and click Versions.
- Select version ZJDE0003 for the Object Configuration Manager version.
- Select the appropriate data source.
  If you are using the local H4A, business functions will run locally in activeconsole, so use the local data source.
  If you are using a production environment, business functions will run on the enterprise server, so use the server data source.
- Click Add to add a new OCM record, and enter the following information:
  - Environment Name: Your Test environment name.
  - Service Name: BSSV
  - User/Role: EnterpriseOne user ID, Role ID, or *PUBLIC.
  - Server: BSSV server name.
    If the consumer business service is running locally on the JDeveloper 11g integrated WebLogic server, use the machine name where JDeveloper 11g is installed.
  - Port: JDENET listening port on the business service server.
    The port name should be the same as the serviceNameListen in the jdeinterop.ini file.
- Save the OCM record.
- Activate the OCM record.
- Test the connectivity with the Business Services server by selecting the OCM record, and then selecting Ping BSSV Server from the Row menu.
  Ensure the connection is successful.
If you are using a production environment, restart the Enterprise server to load the new OCM entry. If you are using a local EnterpriseOne development client, log out and then log in again.
Add a system-level service property record for the JRH90134 project.
Open the Business Service Property Program (P951000).
On Work with Service Property, click Add and enter the following information on the Add BSSV Property form:
- Key: JRH90I30_APP_SERVER_OAS_OR_WAS_OR_WLS
- Value: JAXWS
- Level: System
See "Adding a Business Service Property Record" in the JD Edwards EnterpriseOne Tools Business Services Development Guide
Add a softcoding record for the JRH90I34 project.
Open the Web Service Soft Coding Records program (P954000) from the EnterpriseOne Web client.
On Work with Soft Coding, click Add, and enter the following information on the Add Web Service Soft Coding Record form:
- User / Role: Enter the name of the user ID for testing.
- Environment Name: Enter the name of the test environment.
- Soft Coding Key: JRH90I34.
- Soft Coding Value: Enter the following xml.
```
<scwls>
<endpoint>http://dngorajesvm4:7101/context-root-JPR01000/RI_AddressBookManagerPort?WSDL</endpoint>
</scwls>
```
  Note: The endpoint points to the URL where the target JAX-WS web service is running. In the sample soft coding xml specified above, the endpoint is pointing to the target RI_AddressBookManager web service running locally on the JDeveloper 11g integrated WebLogic server. The web service running locally is not secured, so it is not required to specify user name and password fields in softcoding xml.
  If the target JAX-WS web service is secure and requires the WS-Security Header with user name and password credentials to be passed in the SOAP header, enter the masked user name and password values in the Enter Mask Fields section on the Update Web Service Soft Coding Record form and use the following xml in the Soft Coding Value field:
```
<scwls>
<endpoint>https://dnvmw8r201:9484/DV900/RI_AddressBookManager?WSDL</endpoint>
<username>JDE</username>
<password>_||_password_||_</password>
</scwls>
```
  Note:
  The endpoint points to the RI_AddressBookManager JAX-WS web service running on a standalone WebLogic server.
  The password field in the softcoding XML is the Mask field in the Mask Fields grid and the actual value of the password is specified in the Mask For example the value for the user could be JDE, and the password could be JDE.
  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\system12.1.2.0.40.66.68\DefaultDomain\bin\startWebLogic.cmd