Uddi Registration; Integration Web Service Invocations - IBM BJ0NJML - Service And Asset Management Integration Manual

UDDI Registration

UDDI Registration

Integration Web Service Invocations

256
You can register deployed Web services in a UDDI registry by configuring the
following global properties in the System Properties application:
System Property
mxe.int.uddipuburl
mxe.int.uddiinqurl
mxe.int.uddiname
mxe.int.uddipassword
If you specify values for the UDDI registry publish URL and inquiry URL
properties, the system registers the Web service in the UDDI registry. To bypass
UDDI registration, do not specify any values for these properties.
Only the tModel for the Web Service Definition Language is registered in the
UDDI registry. The businessEntity, businessService, and bindingTemplate are not
registered. The UDDI registration entry contains the URL to the Web Service
Definition Language document.
You can invoke integration Web services by using Dynamic Invocation Interface
(DII) that uses the JAX-RPC API. You can also generate client stub programs by
using a Web services tool of your choice, such as IBM WebSphere Application
®
Server or Microsoft .NET Framework. The Web service tool must reference the
system generated Web Service Definition Language and schema files. The
WebSphere Application Server provides the tool WSDL2Java.
When a Web service is invoked, the response is synchronous. A successful
response returns an HTTP response code of 200.
By default, SOAP faults that are returned do not contain the server side stack
trace, as it represents a potential security risk. However, you can change this
function by changing the following parameter value in the axis2.xml file from
false to true. You can access the axis2.xml file in the global directory/axis2 directory.
parameter name="sendStacktraceDetailsWithFaults"
locked="false">true</parameter>
When invoking any of the integration Web services, the system processes the
message to the business objects. The system then returns a response to the
invoker.
If you have configured the enterprise service to use a JMS queue, the system does
not return any content with the response. As soon as the message is dropped into
the queue, the system returns a response to the invoker and asynchronously
moves the message from the queue to the business objects.
Description
Integration UDDI Registry Publish URL
Integration UDDI Registry Inquiry URL
Integration UDDI Registry User ID
Integration UDDI Registry Password
Integration Guide