2 Maintain Silent config file

This topic describes the process to maintain Silent config file.

Maintain Silent config fileFor the config file maintenance, the below file properties are mandatory.

Table 2-1 Config file Maintenance

Field Description
Env.properties

Individual Fix or Installer needs this property.
SilentEAR FCIS App ear/GW – WS, Rest, GWEJB RESTEJB, GW MDB GWHTTP

It is used to Build Application or Gateway EAR.
SilentDBCompilation

It is used For DB Compilation.
FCIS and Gateway Application Properties FCIS and Gateway Application properties can be generated using Installer.

  1. Individual Fix installer will validate whether the following properties are available or not. The first eight properties are not required for the existing installer to run.
    Env.properties is located in the path, <INSTALLER_PATH>//SOURCE/logs/env.properties.
    • SINGLE_FIX_SCHEMA_NAMES
    • BUILD_PROPERTY_PATH
    • SYMMETRIC_KEY
    • USERNAME
    • PASSWORD
    • PORT
    • SERVICENAME
    • IP
    • JAVA_HOME
    • APPSERVER_HOME
    • ORACLE_HOME
  2. On Env.properties screen, enter the following details.
    Refer to the table for Env.properties.

    Table 2-2 Env.properties

    Field Description
    SINGLE_FIX_SCHEMA_NAMES

    It specifies the schema names with Tilde (~) separator.

    BUILD_PROPERTY_PATH

    It specifies the property file used for DB compilation or EAR build.
    SYMMETRIC_KEY

    Specify the symmetric key, which can be used to decrypt the encrypted property.
    USERNAME

    It is the schema name with encrypted format.
    PASSWORD

    It is the schema password with encrypted format.
    PORT

    It specifies the port number, that schema needs to connect.
    SERVICENAME

    It is the schema service name with encrypted format.
    IP

    It is the IP or Host name with encrypted format.
    JAVA_HOME

    It is the Java Home path.
    APPSERVER_HOME

    It denotes the Application server home path.
    ORACLE_HOME

    It specifies the Oracle DB home path.

    Individual fix installer uses property number 4,5,6,7,8 and connects the schema to update the Applied fix status.

    Same schema details will be passed to existing installer to update the bug status in case of SINGLE_FIX_SOURCE=Y.

    PROPERTIES OF INDIVIDUAL FIX INSTALLER

    The below properties are automatically added by Individual Fix installer while applying the fix.
    SINGLE_FIX_SOURCE

    This value can be Y or N. For individual Fix, the value should be Y.

    SINGLE_FIX_BUG_TYPE

    The value of this property will be Value A or Value D. The Value D is for DB bug and Value A is for any Java /JS bug.

    BUG_TABLE_NAME

    The value is CSTB_APPLIED_POINT_FIXES. It is the name of point fix tracker table.

    BUG_NUMBER

    The number that denotes which bug is being applied.
    SOURCE_PATH

    It is the path where the source is located and it is taken for DB compilation.

    Same env.properties file and its schema details should be maintained for all the bug.
  3. On Silent DB Compilation, enter the following details.
    Refer to the table for Silent DB Compilation.

    Table 2-3 Silent DB Compilation

    Field Description
    Silent EAR

    Individual Fix installer internally calls the Silent EAR building for FCIS Application EAR preparation.

    Sample file is available in <INSTALLER_PATH>SOURCE\config\Silent\ silentConfigBuild.properties.

    For Application EAR building

    The property APPLICATION_TYPE should be FCIS.

    Schema details should be encrypted.

    In PROPERTY_FILE_PATH, the property should specify the fcubs.properties file path.

    The individual fix Installer will validate whether the below properties are maintained in fcubs.properties,

    APPLICATION_NAME, APPLICATION_SERVER, APPLICATION_WORK_AREA, DEBUG, SSL_ENABLED, BRANCH_CENTRALIZED, REQUEST_TIME_OUT, CONNECTION_TIME_OUT, INIT_DATASOURCE, SIGNATURE_PATH, EXCEL_PATH

    Whenever JAVA fixes is applied using the Individual fix installer, the consolidated fixes will be copied into Latest Rolled up sources then the EAR building will use the rolled up path.
    For GATEWAY Application EAR building

    The APPLICATION_TYPE must be Gateway.

    For GATEWAY Application EAR building This section displays the Gateway Application Type EAR building.
    • Gateway EJB
    • Gateway Webservices (SOAP)
    • REST EJB
    • REST Web Services
    Gateway EJB

    In PROPERTY_FILE_PATH, the property should contain GW_EJB_Prop.properties location.

    The GATEWAY_APPLICATION_TYPE must be Gateway EJB.

    The below listed properties are mandatory in GW_EJB_Prop.properties,

    XSD_PATH,FCUBS_ENVELOPE_XSD,MAX_CLOB_LEN,DB_TIMEOUT,LOGGER_PATH,FCIS_MSG_SCHEMA_CON_POOLNAME,FCIS_MSG_SCHEMA_CON_POSS_REQD,DISTRIBUTED_INSTALLATION,GW.LOGGER.FPATH,RTT_PLUGIN,MSG_IN_LOG_REQ,MSG_OUT_LOG_REQ,SYMMETRIC_KEY
    Gateway Webservices (SOAP)

    In PROPERTY_FILE_PATH, the property should contain GW_WS_Prop.properties location.

    The GATEWAY_APPLICATION_TYPE must be Gateway WebServices.

    WEBSERVICE_TYPE This section displays the WEBSERVICE_TYPE of Gateway Webservices.
    • INDIVIDUAL
    • INTEGRATED
    INDIVIDUAL

    In this, the WEBSERVICE_TYPE must be Individual.

    The INDIVIDUAL_WEBSERVICE_SELECTED should contain the service name with Tilde (~) separator. If the value is empty, then MODULES_REQD EAR will be generated.

    The below listed properties are mandatory in GW_WS_Prop.properties:

    NDIVIDUAL_WEBSERVICE_SELECTED,EJB_JNDI_NAME,EJB_CALL_TYPE,EJB_CTX_FACTORY,EJB_SERVER_URL,EJB_SECURITY_PRINCIPAL,EJB_SECURITY_CREDENTIALS,LOGGER_PATH,GW.LOGGER.FPATH,XSD_PATH,RTT_PLUGIN,MSG_IN_LOG_REQ,MSG_OUT_LOG_REQ,DISTRIBUTED_INSTALLATION,SYMMETRIC_KEY,FCIS_MSG_SCHEMA_CON_POOLNAME,FCIS_MSG_SCHEMA_CON_POSS_REQD,MAX_CLOB_LEN,DB_TIMEOUT
    INTEGRATED

    In this, the WEBSERVICE_TYPE must be Integrated.

    MODULES_REQD should contain ALL or specific Module(UT/SM etc).

    The below listed properties are mandatory in GW_WS_Prop.properties,

    "EJB_JNDI_NAME","EJB_CALL_TYPE","EJB_CTX_FACTORY","EJB_SERVER_URL","EJB_SECURITY_PRINCIPAL","EJB_SECURITY_CREDENTIALS","LOGGER_PATH","GW.LOGGER.FPATH","XSD_PATH","RTT_PLUGIN","MSG_IN_LOG_REQ","MSG_OUT_LOG_REQ","DISTRIBUTED_INSTALLATION","SYMMETRIC_KEY","FCIS_MSG_SCHEMA_CON_POOLNAME","FCIS_MSG_SCHEMA_CON_POSS_REQD","MAX_CLOB_LEN","DB_TIMEOUT"
    REST EJB

    In PROPERTY_FILE_PATH, the property should contain GW_RESTEJB_Prop.propertieslocation.

    The GATEWAY_APPLICATION_TYPE must be RESTEJB.

    The below listed properties are mandatory in GW_RESTEJB_Prop.properties,

    FCUBS_SMS_POOL_NAME,LOGGER_PATH,GW.LOGGER.FPATH,APPLICATION_SERVER,SYMMETRIC_KEY,REST_MSG_SCHEMA_CON_POOLNAME,MSG_IN_LOG_REQ,MSG_OUT_LOG_REQ,DEPLOYMENT_TYPE,OPSS_ENABLED
    REST Web Services

    In PROPERTY_FILE_PATH, the property should contain GW_REST_Prop.propertieslocation.

    The GATEWAY_APPLICATION_TYPE must be RESTWS.

    WEBSERVICE_TYPE This section displays the WEBSERVICE_TYPE of REST Web Services.
    • INDIVIDUAL
    • INTEGRATED
    INDIVIDUAL

    In this, the WEBSERVICE_TYPE must be Individual.

    INDIVIDUAL_WEBSERVICE_SELECTED should contains the service name with Tilde (~) separator. if the value is empty, then MODULES_REQD EAR will be generated.

    The below listed properties are mandatory in GW_REST_Prop.properties,

    INDIVIDUAL_WEBSERVICE_SELECTED,FCUBS_SMS_POOL_NAME,LOGGER_PATH,GW.LOGGER.FPATH,APPLICATION_SERVER,SYMMETRIC_KEY,REST_MSG_SCHEMA_CON_POOLNAME,DEPLOYMENT_TYPE,OPSS_ENABLED,REST_EJB_CTX_FACTORY,REST_EJB_PROV_URL,REST_EJB_SECURITY_PRINCIPAL,REST_EJB_SECURITY_CREDENTIALS,REST_EJB_JNDI_NAME,DEPLOYMENT_TYPE,DISTRIBUTED_INSTALLATION
    INTEGRATED

    In this, the WEBSERVICE_TYPE must be Integrated.

    MODULES_REQD should contains ALL or specific Module(UT/SM etc.,)

    The below listed properties are mandatory in GW_REST_Prop.properties,

    FCUBS_SMS_POOL_NAME,LOGGER_PATH,GW.LOGGER.FPATH,APPLICATION_SERVER,SYMMETRIC_KEY,REST_MSG_SCHEMA_CON_POOLNAME,DEPLOYMENT_TYPE,OPSS_ENABLED,REST_EJB_CTX_FACTORY,REST_EJB_PROV_URL,REST_EJB_SECURITY_PRINCIPAL,REST_EJB_SECURITY_CREDENTIALS,REST_EJB_JNDI_NAME,DEPLOYMENT_TYPE,DISTRIBUTED_INSTALLATION
    Silent DB Compilation

    Individual Fix installer internally calls the Silent DB compilation for any DB related fixes.

    Sample file is available in the path, <INSTALLER_PATH>SOURCE\config\Silent\ silentConfigDatabase.properties.

    Using the Installer UI, we can compile only one schema at a time. But using the Individual Fix/ silent installer DB compilation, one can compile the DB units in multiple schemas.

    Schema details need to be pre-configured in configuration file and based on the configuration order, it will execute the action.

    The NUMBER_OF_SCHEMA_EXECUTION property should contain the counts of schema need to be configured for DB compilation.

    For example, if the NUMBER_OF_SCHEMA_EXECUTION is 2, it indicates that the total of two schema details need to be maintained in configuration.

    For Schema 1 Configuration

    SCHEMA1_PASSWORD_INPUT=N

    SCHEMA1_USERNAME=MyTDumkOf3yX7Ujqg/ParA==

    SCHEMA1_PASSWORD=MyTDumkOf3yX7Ujqg/ParA==

    SCHEMA1_SERVICENAME=zlzzfnT7NMbIUF+PLBAzCw==

    SCHEMA1_CONNECTSTRING=zlzzfnT7NMbIUF+PLBAzCw==

    SCHEMA1_IP=/LGVQXLN5/IuSe/nt1+jubXHhlrCOFHP2J/v73SmAeM=

    SCHEMA1_PORT=1521 SCHEMA1_PARALLEL_THREAD_COUNT=

    SCHEMA1_LOAD_STATIC_DATA_REQUIRED=Y

    SCHEMA1_DDL_OBJECT_COMPILATION_REQUIRED=Y

    SCHEMA1_FCIS_SCHEMA=SMS

    SCHEMA1_DESTINATION_DIRECTORY=D:/FCIS/Output/SMS
    For Schema 2 Configuration

    SCHEMA2_PASSWORD_INPUT=N

    SCHEMA2_USERNAME=XtE/PhiEOiCjH5xsk1LO+A==

    SCHEMA2_PASSWORD=XtE/PhiEOiCjH5xsk1LO+A==

    SCHEMA2_SERVICENAME=zlzzfnT7NMbIUF+PLBAzCw==

    SCHEMA2_CONNECTSTRING=zlzzfnT7NMbIUF+PLBAzCw==

    SCHEMA2_IP=/LGVQXLN5/IuSe/nt1+jubXHhlrCOFHP2J/v73SmAeM=

    SCHEMA2_PORT=1521 SCHEMA2_PARALLEL_THREAD_COUNT=

    SCHEMA2_LOAD_STATIC_DATA_REQUIRED=Y

    SCHEMA2_DDL_OBJECT_COMPILATION_REQUIRED=Y

    SCHEMA2_FCIS_SCHEMA=LOB

    SCHEMA2_DESTINATION_DIRECTORY=D:/FCIS/Output/DISTB

    The above example specified only two schema, but the user can specify N number of schemas.