Configuring GDS feature

You must configure a few GDS parameters in order for IBM® Product Master to be able to exchange product data with a datapool.

1. Stop all the services.
2. If you want to create a new specific company for the GDS Persona Supply Side configuration, run the create_cmp.sh script that is located in the $TOP/bin/db folder. You need to perform Importing data model for the new company.
3. Configure the env_settings.ini file for the GDS configuration. Update the following default properties in the [gds] section as required.

   #Possible value is """"yes"""" or """"no"""". Set this to """"yes"""" only if GDS is to be enabled. Default
     value is """"no"""".
     enabled=yes
     #Company code to load GDS datamodel in.
     company_code=
     #Possible value for gds_app_type is """"Demand"""" or """"Supply""""
     gds_app_type=
     #Possible values Transora,WWREV6
     ACTIVE_DATA_POOL_ID=
     #Messaging related parameters. Self GLN is needed for GDS Demand side only.
     inbound_queue_name=
     outbound_queue_name=
     queue_connection_factory=
     datapool_gln=
     self_gln=

4. Install IBM MQ. For more information, see IBM MQ documentation.
5. Set the following default properties in the [mq] section as required. To enable IBM MQ, the value of the enabled property should be true.

   enabled=true
     #home will default to /opt/mqm if not set
     home=<mq home>
     # if mq security is enabled, value should be true. Defaults to false
     mq_security=false
     username=<user name>
     password=<password>
     # encrypt_password defaults to no. If the user wants the password to be encrypted, it should be set to yes. And value of password parameter above should be removed.
     encrypt_password=no

6. Run the configureEnv.sh located in the $TOP/bin folder. If you cannot override property files by running configureEnv.sh script then, you need to update the properties manually as follows.
   1. Add IBM MQ JARs from the jars-mq.txt file and directory in class path.
   2. Set the value of the enable_gds=true in the common.properties file at the $TOP/etc/default folder .
   3. Set the following properties in the gds.properties file at the $TOP/etc/default folder.
      • company_code
      • gds_app_type - Possible values can be Supply and Demand.
      • Internal_Classificion_Scheme - Possible values can be Internal_Hierarchy and GPC_Hierarchy. The defaults values are set based on the value of the gds_app_type parameter.
        • If the value of the gds_app_type=Supply then Internal_Classification_Scheme=Internal_Hierarchy.
        • If the value of the gds_app_type=Demand then Internal_Classification_Scheme=GPC_Hierarchy.
      • ACTIVE_DATA_POOL_ID - Possible values can be Transora (for 1SYNC) and WWREV6 (for GDSN/SA2).
   4. Update the mq.xml file at the $TOP/etc/default folder.
      If the file is missing create a mq.xml file as follows with correct username and password.

      <?xml version="1.0" encoding="UTF-8"?> 
      	<mq_config> 
      		<mq_security_enabled>true</mq_security_enabled>
      		<mq_userName><username></mq_userName>
      		<mq_password_encrypted/> 
      		<mq_password_plain><password></mq_password_plain>
      	</mq_config> 

   5. Update following properties in the properties.xml file.
      • INBOUND_QUEUE_NAME
      • OUTBOUND_QUEUE_NAME
      • QUEUE_CONNECTION_FACTORY
      • DATAPOOL_GL (Demand side)
      • SELF_GLN (Demand side)
      Supply side path for the properties.xml file:
      $TOP/etc/messaging/xml/supply/transora
      Demand side path for the properties.xml file:
      $TOP/etc/messaging/xml/demand/wwrev6
7. Run the loadGDSDatamodel.sh script located in the $TOP/bin/db folder.
8. Start the services from the $TOP/bin/go folder.
9. In the Admin UI,
   1. Go to Home > My Settings > General Settings. For all the users, set the Locale for Item and Category Data Display to English (United States).
   2. Verify that the Full Admin and GDS Supply Editor roles are available in the Role console and assign the appropriate role to the user.
   3. Add appropriate values according to your requirements to the following default static selections in the Selection console:
      • Product_GPC - Selection with all the data present in the GPC Hierarchy.
      • Product_IC - Selection with all the data present in the Internal Hierarchy.
      • Product_TMH - Selection with all the data present in the Target Market Hierarchy.

      Note:

      • Do not select the TA as an available option for the Target market as this is a root category for the Target Market Hierarchy and is not the actual Target market.
      • Select the leaf categories present under the GPC Hierarchy and Internal Hierarchy while creating the respective selections.
      • To populate the TPC_IP selection, see the step h.
   4. Go to Product Manager > Reports > Reports console. Run the following report after selecting the appropriate input parameters:
      • Update GPC Lookup - Updates GPC_Category_Selection_List_Lookup table
      • Update IC Lookup - Updates Internal_Category_Selection_List_Lookup table
      • Update IP Lookup - Updates IP_Category_Selection_List_Lookup table
      • Update TMH Lookup - Updates Target_Market_Selection_List_Lookup table

        To run the reports, you must open the report and provide input parameter (selection name) in the report.

        Following is the order of execution of reports and respective input parameters:

        1. Update GPC Lookup report and Product_GPC input parameter
        2. Update IC Lookup report and Product_IC input parameter
        3. Update TMH Lookup report and Product_TMH input parameter
   5. Verify the following Lookup table updates after report execution:
      • GPC_Category_Selection_List_Lookup
      • Internal_Category_Selection_List_Lookup
      • Target_Market_Selection_List_Lookup
   6. Create an item (with information provider details) under the Trading Partner Catalog under IP Hierarchy in any category.
   7. Update the static TPC_IP selection through the Selection console by selecting the Information provider provided in the previous step.

      1. Run the Update IP Lookup report by providing static TPC_IP selection as an input.

      2. You must verify that the IP_Category_Selection_List_Lookup content is updated after the report execution.

   8. Add post-processing script with the name as TradeItemValidation under the catalog attributes in the GDS Product Catalog.
      1. Select the Post Processing and click Add.
      2. Add the following in the Catalog Script Editor and click Save.

         //script_execution_mode=java_api="japi://com.ibm.gds.extensions.postprocessing.ValidationsPostProcessing.class"

      3. Select the new script from the list in the Catalog attribute page.
         Note: After each execution of the loadGDSDatamodel.sh script, you need to add or select this script.
10. Create gds.properties file by using the gds.properties.default file located in the $TOP/etc/default folder.
11. Create gdsConfig.properties file by using the gdsConfig.properties.default file located in the $TOP/mdmui/dynamic/mdmrest folder.