Providing Web Service Customizations

Providing customizations at build-time impacts the security and behavior of your web service at runtime. With the default configuration the web services EAR file build will:

• Assign the appropriate IBM Cúram Social Program Management message receiver for struct and domain types, for argument and operation return values, or for W3C Documents, based on how you set the WS_Is_XML_Document property in Rational Software Architect for the "WS Inbound" (stereotype: <<wsinbound>>) class.
• Expect the web service client to pass a custom SOAP header with authentication credentials in order to invoke the web service.

To change the above default behaviors you will require a custom receiver (see Customizing Receiver Runtime Functionality for more information). Additionally, customizations may be necessary for:

• Implementing Web Services Security (Apache Rampart) (see Secure Web Services for more information);
• Providing external, non- IBM Cúram Social Program Management functionality such as the Axis2 Admin application and Apache Axis2 Monitor (see Including the Axis2 SOAP Monitor in Your Web Services WAR File for more information);
• Providing other custom parameters for the deployment descriptor (services.xml); e.g. doclitBare, mustUnderstand, etc. See the Apache Axis2 documentation for more information (Apache Axis2 Configuration Guide).

In order to be able to effectively customize your web services you should be aware of how IBM Cúram Social Program Management processes web services at build time, which is explained in the following sections.