Getting Started

The process for developing inbound web services is briefly:

1. Model your web service and provide implementation code

You need to define the classes (WS Inbound) and operations in Rational Software Architect that you will be implementing to provide the functionality you wish to expose as web services.

As with any IBM Cúram Social Program Management process class you need to provide the implementation for the classes and operations you model as per the Cram Modeling Reference Guide.

2. Build your web services and the web services EAR file

The IBM Cúram Social Program Management build system will build and package your web services. Use the server and EAR file build targets as described in the Cram Server Developer's Guide and the deployment guide appropriate to your platform.

3. Provide security data for your web services

By default your web services are not accessible until you: a) Provide security data (see Providing Security Data for Web Services) that defines the service class and operation and which security group(s) can access them; and b) Your clients must then provide credentials appropriate to those security definitions (see Custom SOAP Headers (unless you choose to disable this security functionality; see Custom Credential Processing).

Each of the above steps is explained in more detail in the sections that follow. To better understand the process just outlined the following illustrates the structure of directories and files used.

+ EJBServer
   + build
     + svr
       + gen
         + wsc2                        - where the generator
                                         places ws_inbound.xml
                                         property files
         - <service_name>.wsdl         - where modeled service
                                         WSDL files are generated
   + components
     + custom
       + axis
         + <service_name>
           - ws_inbound.xml            - where you might place a
                                         custom ws_inbound.xml
                                         property file
           - services.xml              - where you might place a
                                         custom services.xml
                                         descriptor file
        + source                       - where optional schema
                                         validation code would go
          + schemas                    - where you might place
                                         optional schema
          + webservice                 - where you must place
                                         custom receiver code