6 ODT Silent Utility

This topic describes an overview of the operations of ODT Silent Utility.

Prerequisites

Refer to the topic unresolvable-reference.html#GUID-EF80B6A9-5087-4BBE-BDAB-0E92119A232F for detailed information.

Utility Run on Windows/Unix

After copying the installer sources and library folder to the local system, make sure to uncheck the read-only check box in source properties and apply the same to all the subfolders.

The figure below shows the source folder in the local system:

Figure 6-1 Source Folder of SilentODTUtility

Description of "Figure 6-1 Source Folder of SilentODTUtility"

Configuration of SilentODTUtility

All Configuration files can be found inside/resource folder of the utility.

1. SilentOdt.properties

   Table 6-1 SilentOdt.properties

   Field	Description
   ODT Data Source Detail Credentials
   OdtJdbcUrl	JDBC jdbc:oracle:thin:@10.184.xx.xx:1521:FCDEMO (should be encrypted using utility)
   OdtDbUser	DB User name (should be encrypted using utility)
   OdtDbPassword	DP Password (should be encrypted using utility)
   Logger Properties
   Logreqd	Y/N, Default set to N. If the value is set to Y the logger will be enabled for the generation of the log. If the value is set to N logger will be disabled.
   Logpath	Provide the path where the Logger files will be generated.
   Level	Provide the Logger Level. This can be either DEBUG/INFO/WARNING/SEVERE. Provide as DEBUG for writing detailed log. Default value would be set to INFO.
   System Properties
   JAVA_HOME	Maintain the Java installed location.
   WEBLOGIC_HOME	Maintain the oracle Weblogic installed location.
   WAS_HOME	Maintain the IBM Websphere installed location.

   JAVA_HOME, WEBLOGIC_HOME, WAS_HOME are optional and can be used for generating template Ant scripts.
2. OdtOperations.properties
   Configure the Operations files as per requirement. The following operations are supported in the silent utility of ODT:

   1. LOGIN
   2. SETRELEASE: Setting Release and Environment Details
   3. BULKGENERATION: Bulk Generation of RADXML units
   4. REFRESH: Bulk refresh of RADXML
   5. SXML_REFRESH: Bulk refresh of Service XMLs
   6. SXML_UPDATER: Bulk Updater of service XMLs based on the changes in RADXMLs
   7. SXML_BULKGENERATION: Bulk Generation of web service artifacts.
   8. REST_GENERATION: Bulk Generation of Rest Service Artifacts

   Execution of Operation will be as per the sequence maintained in OdtOperations.properties.
   Example:

   1. Operation = LOGIN
   2. Operation= SETRELEASE
   3. Operation= REST_GENERATION

   If the sequence of operations is as above, then LOGIN, SETRELEASE, and REST_GENERATION Operations would be processed in the respective sequence.

   Note:

   LOGIN and SETRELEASE are mandatory operations to be performed.

   1. LOGIN
      Login should always be the first operation to be configured as part of any execution.

      Figure 6-2 LOGIN Operation

      
      

      
      Description of "Figure 6-2 LOGIN Operation"

      
      

      Table 6-2 Login to Tool

      Field	Description
      Operation	LOGIN
      User Id	ODT User Id which is created in the ODT Application.
      Password	ODT Password which is created in the ODT Application (should be encrypted using Utility).

   2. SETRELEASE
      This operation is used for setting Release and Environment Preferences for SilentODTUtility. Connection to the FLEXCUBE schema would be established based on data maintained in ODT or through the data in env_config.xml as explained in an earlier section.

      Figure 6-3 SETRELEASE Operation

      
      

      
      Description of "Figure 6-3 SETRELEASE Operation"

      
      

      Table 6-3 Release and Environment Details for User

      Field	Description
      Operation	SETRELEASE
      relCode	ODT Release Code which is created in the ODT Application.
      envCode	ODT Environment Code which is created in the ODT Application.
      langCode	Lang code for the above-mentioned release code.

   3. REST_GENERATION
      Web service artifacts can be generated through this operation.

      Table 6-4 REST_GENERATION

      Field	Description
      radxmlListFile	Prepare text file which contains absolute path of all RADXMLs which are used for those services.
      srcPath	Provide source folder path which is an option (Tool will create radxmlListFile by itself from the srcPath. Note that if srcPath is provided, radxmlListFile need not be provided.
      destpath	Provide the path where the files will be generated.
      gen	Provide the type of files to be Generated (separated by comma). Options are REST.

      Table 6-5 Service XML Component Generator

      Input	Output
      operation	REST in destination path
      radxmlListFile	REST in destination path
      srcPath	REST in destination path
      fileType	REST in destination path
      destpath	REST in destination path
      gen	REST in destination path

Generation of Rest service Artifacts through SilentOdtUtility

To generate Rest service artifacts for a service, configure the property files of the utility as explained in the previous section.

Following operations needs to be configured in OdtOperations.properties in the respective sequence:

1. LOGIN
2. SETRELEASE
3. REST_GENERATION

Provide the following values for gen parameter of REST_GENERATION. To generate Rest service Artifacts, the user has to double click on the batch file silentOdt.bat/sh present in the ODT source.

Figure 6-4 SilentODT Sources Folder

Description of "Figure 6-4 SilentODT Sources Folder"

Figure 6-5 SilentODT Command Prompt

Description of "Figure 6-5 SilentODT Command Prompt"

After the successful built operation, The Rest artifacts files will be generated in the destination directory specified.