2.1 Generate Service XML

This topic provides the systematic instructions to generate Service XML.

1. Log in to Development Workbench for Universal Banking.
   The Development Workbench for Universal Banking Home Page is displayed.

   Figure 2-1 Development Workbench for Universal Banking

   
   

   
   Description of "Figure 2-1 Development Workbench for Universal Banking"

   
   
2. Click the Services node in the Browser menu in the Landing page of ODT.
   The Services screen is displayed.

   Figure 2-2 Services Screen

   
   

   
   Description of "Figure 2-2 Services Screen"

   
   
3. Specify the details in the Services screen while creating a new service in ODT.
   For more information on fields, refer to the field description table.

   Table 2-2 Services - Field Description

   Field	Description
   Action	Specify the Action from the drop-down list. The list displays the following values: New Load Select the Action as New for a new Service development. Select the Action as Load to load the corresponding Service xml using browser option in Save Xml path.
   Load Screen XML	Use Browse option to load XML.
   Service Name	If the action is selected as New, service name has to be selected from service LOV(Service LOV will fetch values from GWTM_SERVICES_MASTER For new service, service name needs to be added in GWTM_SERVICES_MASTER of business schema).
   Service Description	On selection of service name, service description will be populated in Service Description field.
   Module	If the action is selected as New, Module has to be selected from Module LOV. (Module LOV will fetch values from SMTB_MODULES of Business schema). Module Name need not always be from the LOV. Note that Artifacts would be generated based on the Module Name specified. Hence provide source Folder module names (Example: Core for CS) in this field.

4. Select the Service Name from the service LOV, if the action is selected as New.
   The Service Name window populates.

   Figure 2-3 Service Name

   
   

   
   Description of "Figure 2-3 Service Name"

   
   
5. Select the Module from the Module LOV, if the action is selected as New.
   Module LOV will fetch values from SMTB_MODULES of Business schema. Module Name need not always be from the LOV. Note that Artifacts would be generated based on the Module Name specified. Hence provide source folder module names (Example: Core for CS) in this field. On selection of module, module code and module description will be populated in module description field.
   The Module Code window populates.

   Figure 2-4 Services_Module Code

   
   

   
   Description of "Figure 2-4 Services_Module Code"

   
   
6. Save XML Path: Save the xml path if the action is selected as New. It is optional and if provided, then the generated units will be saved in the path mentioned.
   Note that the value in the Save Xml Path will be used only if the Save Format is Client Path and if the User has given CURRENT_DIRECTORY in the User Preferences Work Directory.
   The label description of the field will change depending on the action .If the action is Load, ODT attaches the Browse button to it so that user can browse the Service xml and load it.

   Figure 2-5 Services_Save Xml Path

   
   

   
   Description of "Figure 2-5 Services_Save Xml Path"

   
   
7. Attach the Function ID which are part of this service. You can also remove the same from service if not required.
8. Select the Function ID from Function Id LOV to add the same for that service. Function Id LOV will populate data from SMTB_MENU.
   Make sure that FC_FUNCTION_ID values are selected for Function Id so that physical radxml file for the same function Id exists. Example: Select UTDUH and not UTGUH.
   The Function Name-Module window populates.

   Figure 2-6 Function Name-Module

   
   

   
   Description of "Figure 2-6 Function Name-Module"

   
   
9. On selection of Function Id, this field value Extensible/Non-Extensible would be populated.

   Figure 2-7 Screen to populate Function Id

   
   

   
   Description of "Figure 2-7 Screen to populate Function Id"

   
   
10. Type XSD name will be defaulted along with operations for an Extensible Function Id. For Non-Extensible Function Id, Type XSD name has to be explicitly mentioned in the field.
11. Select the Function ID checkbox and click Operations.
    Operation Codes will be defined in each radxml which has to be defaulted in the Service XML as well.
    The Operation Details pop-up screen is displayed.

    Figure 2-8 Services_Operation Details

    
    

    
    Description of "Figure 2-8 Services_Operation Details"

    
    
12. In the Operation Details screen, click the Browse button to it so that the user can browse the Function id RAD XML and load it to populate operations.
    The Upload window populates.

    Figure 2-9 Services_Operation Details_Upload

    
    

    
    Description of "Figure 2-9 Services_Operation Details_Upload"

    
    
13. Click the Default operations in the Operation Details Screen. Operation Code and Type Xsd Names will be defaulted from loaded RADXML.
    The Services_Operation Details_Default Operations screen is displayed.

    Figure 2-10 Services_Operation Details_Default Operations

    
    

    
    Description of "Figure 2-10 Services_Operation Details_Default Operations"

    
    
14. Save the Service XML. ODT saves all the activities carried out by the developer in an xml file hereby referred to as SXML. Persistence of the WEBSERVICE is achieved through SXML and RADXML.

    If some changes are required on the webservice in a future release, the same SXML can be loaded and changes can be done on this SXML. ODT can segregate the changes done on different releases and saves the SXML accordingly. SXML will adhere to follow the below mentioned naming convention as Service Name + .sxml.

    Example: FCISUnitholder.sxml