The following topics provide overview information about inbound web services (IWS).
An inbound web service supports the configuration of one or more operation per web service. Each operation defines the schema-based object to invoke to perform the desired function. An operation may refer to a Business Service, a Business Object, or a Service Script. If the IWS supports multiple operations, each operation can refer to the same or a completely different schema-based object from other operations within the IWS. In addition, each operation may define a transaction type, which is essentially an action that is supported by the schema-based object.
By default, Inbound Web Services uses the Schema Name to dictate the Request and Response for the service. The API can be overridden with custom formats by specifying Request and Response Schemas with the appropriate Request and Response XSL to transform into the relevant schema formats.
When preparing to deploy inbound web services, the security aspects of the service must be decided. There are three options available:
Attach a security policy to the IWS via a Web Service Annotation. The product supplies the security policy Username Token Policy that may be used. This attaches a policy file (UsernameToken.xml) to the Inbound Web Service at deployment time.
Attach security policies to the Inbound Web Service via the J2EE Web Application Server. This allows for multiple policies to be attached as support by the J2EE Web Application Server.
A combination of the internal and external security policies.
An Inbound Web Service must be deployed to the J2EE Web Application Server in order for it to be available to the Web Service Clients to access the system. Refer to Deploying Web Services for more information.
Copyright © 2007, 2016, Oracle and/or its affiliates. All rights reserved. Documentation build: 2.5.2016 10:21:45 [T1_1454696505000]