This topic describes the configuration needed for using inbound web services.
Once an Inbound Web Service is defined it is not automatically available to the Web Service Clients to access the system. The Deployment Status and the Active flag (set to true) indicate whether a Web Service is available or not. The last step is to deploy the Inbound Web Services to the J2EE Web Application Server. This deployment phase has a number of steps that are automatically performed when a deployment is initiated:
The Web Service files are generated and policies are attached.
The WSDL is generated with appropriate annotations and enumerations.
The necessary java stub code to implement the Web Service in the J2EE Web Application Server is generated and compiled.
The Web Services are built into a valid Web Application Archive (WAR) file.
Optionally, the newly created Web Services WAR file is deployed to the J2EE Web Application Server. This can also be done manually for clustered deployments, if desired.
There are two methods available for deploying inbound web services:
Deployment at the command line using the iwsdeploy[.sh] command as outlined in the Server Administration Guide. This method is recommended for native installations and production implementations.
Deployment using the Inbound Web Service Deployment portal. This method is recommended for development and non-production environments.
Copyright © 2000, 2015, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.19.2015 16:18:51 [F1_1424305131000]