6 Configuration of SilentODTUtility
This topic provides an overview of the configuration process of Silent Open Development Tool Utility.
All Configuration files can be found inside the resource folder of the utility.
For example, In Weblogic 12c <Oracle_Home>\oracle_common\modules\com.sun.xml.bind.jaxb-jxc.jar
Note:
Copy jaxb-xjc.jar to the lib folder. This can be obtained from application server libraries.Also make sure ojdbc6.jar is available under lib folder.
SilentOdt.properties
The sample property file has been given below. Refer to the details mentioned for
each property in the below table. Some of them are encrypted using
ODTPassEncryption.bat
(ODTPassEncryption.sh for UNIX). Use 16 characters length
of the symmetric key for encryption (Preferably Alphanumeric) which will be prompted
for input from the user when the encryption utility is launched. The same symmetric
key must be mentioned in the property file as well.
Figure 6-1 File attachment- SilentOdt.properties
Table 6-1 Open Development Tool Data Source Detail Credentials
| Open Development Tool Data Source Detail Credentials | Description |
|---|---|
| OdtJdbcUrl | Encrypted JDBC URL, Sample JDBC URL (before encrypting) jdbc:oracle:thin:@10.184.xx.xx:1521:FCDEMO |
| OdtDbUser | DB User Name |
| OdtDbPassword | Encrypted Password. |
| SymmetricKey | The key is used when encrypting the JDBC URL and
password. This should have exactly 16 characters.
Note: User must use the same key for both JDBC URL and password encryption. |
Table 6-2 Logger Properties
| Logger Properties | Description |
|---|---|
| Logreqd | Y/N. Default set to N. |
| Logpath | Provide the path where the Logger files will be generated. |
| Level | Provide the Logger Level. This can be either SEVERE/WARNING/INFO/CONFIG/FINE/FINER/FINEST. Provide as FINEST for writing detailed log. The default value would be set to INFO. |
Table 6-3 System Properties
| System Properties | Description |
|---|---|
| JAVA_HOME | Maintain the Java(JDK) installed location. |
| WEBLOGIC_HOME | Maintain the Oracle WebLogic installed location. |
| WAS_HOME | Maintain the IBM Websphere installed location. |
ODTOperations.properties
Configure the Operations file as per requirement. The following operations are supported in the Silent Utility of Open Development Tool:
- LOGIN
- SETRELEASE: Setting Release and Environment Details
- BULKGENERATION: Bulk Generation of Radxml units
- REFRESH: Bulk refresh of RADXML
- SXML_REFRESH: Bulk refresh of Service XMLs
- SXML_UPDATER: Bulk Updater of service Xmls based on the changes in RADXML’s
- SXML_BULKGENERATION: Bulk Generation of web service artifacts
For example,
- Operation = LOGIN
- Operation= SETRELEASE
- Operation= REFRESH
Note:
LOGIN and SETRELEASE are mandatory operations to be performed.- LOGINLOGIN should always be the first operation to be configured as part of any execution.
Table 6-4 Login to Tool
Field Description Operation LOGIN User Id Open Development Tool User Id which is created in the Open Development Tool Application. Password Open Development Tool Password which is created in the Open Development Tool Application. Encrypted using ODTPassEncryption.bat. - SETRELEASEThis operation can be used for setting Release and Environment Preferences for SilentODTUtility. Connection to the Oracle FLEXCUBE Universal Banking schema would be established based on data maintained in Open Development Tool or through the data in env_config.xml as explained in an earlier section.
Table 6-5 Release and Environment Details for User
Field Description Operation SETRELEASE relCode Open Development Tool Release Code which is created in the Open Development Tool Application. envCode Open Development Tool Environment Code which is created in the Open Development Tool Application. langCode Lang code for the above-mentioned release code. - BULKGENERATIONFor generating all RADXML artifacts for release in bulk this feature can be used.
Table 6-6 BULKGENERATION
Field Description radxmlListFile Prepare text file which contains absolute path of all RADXML's. Provide the same file path. srcPath Source path refers to the path where all RADXML's are presented. List File would be generated by the tool in this case. Note that only either radxmlListFile or srcPath should be present. If both are present, then the radxmlListFile parameter would be considered for Bulk Generation. fileType - EXTENSIBLE: artifacts generated only for extensible screens.
- NON_EXTENSIBLE: artifacts generated only for non-extensible screens.
- BOTH: artifacts for all files would be generated.
destpath Provide the path where the files will be generated. gen Provide the type of files to be generated. For example, UIXML, SYS_JS, MAIN_SPC, MAIN_SQL,KERNEL_SPC, KERNEL_SQL Figure 6-4 SilentODT Bulk Generation Properties
Table 6-7 Bulk Generation Utility
Input Output radxmlListFile UIXML,SYS_JS,MAIN_SPC,MAIN_SQL,KERNEL_SPC,KERNEL_SQL, CLUSTER_SPC,CLUSTER_SQL,CUSTOM_SPC,CUSTOM_SQL, UPLOAD_SPC,UPLOAD_SQL,UPLOAD_TRIGGER,UPLOAD_TABLE_DDL, XSD_FILES,MENU_DETAILS,LABEL_DETAILS,AMEND_DETAILS, SUMMARY_DETAILS,SCREEN_DETAILS,LOV_DETAILS, BLOCK_PK_COLS,CALL_FORM_DETAILS,BLOCK_DETAILS, DATASCR_DETAILS,FUNCTION_CALL_FORMS,GATEWAY_DETAILS, NOTIFICATION_DETAILS,FUNCTION_PARAMETERS NOTIFICATION_TRIGGER,PURGE_DETAILS,ARCHIVE_TBL_DEF in destpath. srcPath fileType gen destpath - REFRESHRefresh Functionality allows developers to upgrade the existing RADXML to its later version keeping the sub-version-specific changes intact. Three kinds of refresh can be done using the Tool. (Refer to the Development Workbench - Source Upgrade)
- Child Refresh
- Screen Child Refresh
- Source Refresh
Table 6-8 REFRESH
Field Description Refresh Type Provide the refresh type (CHILD_REFRESH/SCRCHILD_REFRESH/SOURCE_REFRESH). srcFileList A text file containing the list of all source RADXMLs. i.e. RADXMLs have to be refreshed. baseFileList A text file containing the list of all base RADXMLs. srcRelType Provide the release type of source RADXMLs list(KERNEL/CLUSTER/CUSTOM). baseRelType Provide the release type of base RADXMLs list (KERNEL/CLUSTER/CUSTOM). destpath Provide the path where the files will be generated. Table 6-9 Refresh Utility
Input Output refreshType Refreshed Radxml’s in destpath. srcFileList Refreshed Radxml’s in destpath. baseFileList Refreshed Radxml’s in destpath. srcRelType Refreshed Radxml’s in destpath. baseRelType Refreshed Radxml’s in destpath. destpath Refreshed Radxml’s in destpath. - Service XML Bulk GenerationWeb service artifacts can be generated through this operation.
Table 6-10 Service XML Bulk Generation
Field Description sxmlListFile Prepare text file which contains absolute path of all Service XML. radxmlListFile Prepare a text file that contains the absolute path of all RADXML which are used for those services. xsdListFile Prepare a text file that contains the absolute path of all XSDs which are used for those services. Non-extensibility/Common XSDs are copied from this path. srcPath Provide source folder path which is an option (tool will create radxmlListFile and xsdListFile by itself from the srcPath). Note that if srcPath is provided, radxmlListFile and xsdListFile need not be provided. gen Provide type of files to be generated (separated by comma). Options are IMPL_FILE, CONFIG_FILES,WSDL_FILE,XSD_FILES,GW_WS_PROP_FILES,ANT_BUILD. nonExtServicesReqd Y/N, Specifies whether NonExtensible Operations has to include in the generated components. destpath Provide the path where the files will be generated. validateXsds Y/N, Default set to Y. If the value is set to Y all XSD will be validated by the tool. Figure 6-6 SilentODT Service XML Bulk Generation Properties
Table 6-11 Service XML Component Generator
Input Output sxmlListFile IMPL_FILE,CONFIG_FILES,WSDL_FILE,XSD_FILES,GW_WS_PROP_FILES,ANT_BUILD in destpath radxmlListFile xsdListFile srcPath nonExtServicesReqd destpath validateXsds - Service XML UpdaterThis feature can be used to update the Service XMLs with the latest data from RADXMLs. The following details will be updated:
- Any addition, deletion, or modification of operation codes in function Id would be updated in Service XML.
- If any function Id is removed from the service (specified in RADXML); then the same would be removed from Service XML. Note that if any new function Id is attached to the service (in RADXML); then the same will not be updated in the Service XML. This has to add manually in the Service XML through the Open Development Tool user interface.
Table 6-12 Service XML Updater
Field Description Operation SXML_UPDATE sxmlListFile Prepare a text file that contains the absolute path of all Service XML. Provide the same file path. radxmlListFile Prepare a text file that contains the absolute path of all RADXMLs which are used for those services. Provide the same file path. srcPath Provide source folder path. This field is optional (tool will create radxmlListFile and sxmlListFile by itself from the srcPath). Note that if srcPath is provided, radxmlListFile and sxmlListFile need not be provided. destpath Provide the path where the files will be generated. confirmStage SINGLE_STAGE_UPDATE (Default Value should not be modified by the developer) Figure 6-7 SilentODT Service XML Updater Properties
Table 6-13 Service XML Updater
Input Output xsdListFile Updated Service XML’s in destpath. sxmlListFile Updated Service XML’s in destpath. radxmlListFile Updated Service XML’s in destpath. srcPath Updated Service XML’s in destpath. destpath Updated Service XML’s in destpath. confirmStage Updated Service XML’s in destpath. - Service XML RefreshRefresh Functionality allows us to upgrade the existing service XML to its later version keeping the sub-version-specific changes intact.
Table 6-14 Service XML Refresh
Field Description srcFileList Prepare a text file that contains the absolute path of all Service XML, the same file should be provided i.e. service XML which has to be refreshed. baseFileList Prepare a text file that contains the absolute path of all base service XMLs. Provide the same file path. For instance, for a custom development team; all the latest Kernel files have to be mentioned in baseFileList while the custom Service XMLs to be refreshed has to be mentioned in the srcFileList. srcRelType Provide the release type of Source RADXMLs list (KERNEL/CLUSTER/CUSTOM). baseRelType Provide the release type of base RADXMLs list (KERNEL/CLUSTER/CUSTOM). baseRelType should be at least one level below srcRelType for SOURCE Refresh. For Instance, for a custom development team, srcRelType would be CUSTOM and baseRelType can be either KERNEL/CLUSTER depending on the base source type. destpath Provide the path where the files will be generated. Figure 6-8 SilentODT Service XML Refresh Properties
Table 6-15 Service XML Refresh
Input Output operation Refreshed Service XML’s in destpath. srcFileList Refreshed Service XML’s in destpath. baseFileList Refreshed Service XML’s in destpath. srcRelType Refreshed Service XML’s in destpath. baseRelType Refreshed Service XML’s in destpath. destpath Refreshed Service XML’s in destpath.
GW_CONFIG.properties
These properties file parameters are used for the generation gateway web service
properties files. This configuration file is optional. Provide only if Gateway Web
service property files (GW_WS_PROP_FILES) is being generated
as part of Service XML Bulk generation operation.
Table 6-16 GW_CONFIG.properties
| Field | Description |
|---|---|
| EJB_APP_NAME | Provide the Name of the deployed EJB Application. |
| EJB_APP_SERVER | Provide Application server name in which ear deployed. |
| EJB_JNDI_NAME | EJB JNDI Name is the reference name of the EJB by which the EJB has been deployed. |
| EJB_SERVER_URL | Application server IP Address & port where the EJB application is deployed. |
| EJB_SERVER_USERNAME | User Name of the application server where the EJB application is deployed. |
| EJB_SERVER_PASSWORD | Password of the application server where the EJB application is deployed. |
| GW_WS_LOGGER_PROP_FILE_PATH | Provide the Location of Logger Property File
path in the server where web service is to be deployed. Provide
path including the file name. For example,
|
| GW_WS_LOGGER_FILE_PATH | Provide the location where debug files will be
written. For example,
|
| GW_WS_PROP_FILE_PATH | Path where property file is placed in the
server. This will be referred to in
web.xml of the web service property
file. For example,
|
| XSD_PATH | XSD Path |
