Creating master data by using Supply Side GDS

You need to configure the GDS Persona - Supply Side after the installation.

Perform the following tasks to configure the GDS Persona - Supply Side.

Load GDS data model: You need to load GDS data model to configure the GDS Persona - Supply Side, see Post-installation setup. These steps are to be performed post-installation.; Any configuration changes related to properties, env_settings.ini file requires restart of the server. You should complete the configuration to avoid multiple restarts.
Configure Market Group: Market groups that are defined in 1WorldSync can be used during publishing items. To use these groups, you need to configure the market groups, which are of interest in the Market Group Catalog. The members (trading partners) associated with a market group are also required to be added in the market group definition. This is useful to identify partners to whom items have been published and record their responses (Received, Synchronized, and so on). It is recommended to configure all market groups, which would be used during publishing of items in the Market Group Catalog. If one does not intend to use Market Groups during publishing, this configuration can be skipped.

Troubleshooting

Following are some troubleshooting tips.

mdmce-env.zip

The file is available in the following folder and loaded in the environment where the GDS persona is being configured.

$TOP/mdmui/env-export/mdmenv

LoadGDSDatamodel Script

Some database connection related error can be seen and should be ignored as they are expected. Check the errors while importing the MDM objects.

Example

+++++ Loading look up specs and tables
value of top is : D:/mdm/120Patch/ccd_srcNote: \tmp\19100\WPCenvironmentcatalogcontentimport15902150569300.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Caught Exception in processing: CWPCM0298E:There was an error while executing the batch statement.
Exception in thread "Thread-1673" java.lang.RuntimeException: CWPCM0298E:There was an error while executing the batch statement.
at com.ibm.ccd.connectivity.common.ContentSaveConsumer.run(ContentSaveConsumer.java:68)
at java.lang.Thread.run(Thread.java:811)
Caused by: CWPCM0298E:There was an error while executing the batch statement.
at com.ibm.ccd.common.context.common.DBContext.commitPrepBatch(DBContext.java:838)
at com.ibm.ccd.common.context.common.DBContext.commitBatch(DBContext.java:890)
at com.ibm.ccd.content.common.Item.BOFtoDB(Item.java:2642)
at com.ibm.ccd.content.common.Item.insertAll(Item.java:341)
at com.ibm.ccd.element.common.BaseObject.persist(BaseObject.java:1315)
at com.ibm.ccd.element.common.PersistenceManager.persistObject(PersistenceManager.java:77)
at com.ibm.ccd.element.common.PersistenceManager.persistObjectBasedOnInBatch(PersistenceManager.java:114)
at com.ibm.ccd.element.common.PersistenceManager.persistObject(PersistenceManager.java:144)
at com.ibm.ccd.content.common.Item.toDB(Item.java:2563)
at com.ibm.ccd.content.common.Item.toDB(Item.java:2504)
at com.ibm.ccd.common.script.ScriptOperationsItem.insert(ScriptOperationsItem.java:1192)
at com.ibm.ccd.common.script.ScriptOperationsItem.saveCtgItem(ScriptOperationsItem.java:1125)
at com.ibm.ccd.common.interpreter.operation.generated.GenSaveCtgItemOperation.execute(GenSaveCtgItemOperation.java:74)
at com.ibm.ccd.connectivity.common.ContentSaveConsumer.run(ContentSaveConsumer.java:62)
... 1 more
Caused by: com.ibm.db2.jcc.am.SqlIntegrityConstraintViolationException: Error for batch element #1: DB2 SQL Error: SQLCODE=-803, SQLSTATE=23505, SQLERRMC=2;PIMDBUSR.TCTG_ITM_ITEM, DRIVER=4.19.49
at com.ibm.db2.jcc.am.kd.a(Unknown Source)
at com.ibm.db2.jcc.am.kd.a(Unknown Source)
at com.ibm.db2.jcc.am.kd.a(Unknown Source)
at com.ibm.db2.jcc.t4.bb.a(Unknown Source)
at com.ibm.db2.jcc.t4.bb.a(Unknown Source)
at com.ibm.db2.jcc.t4.p.a(Unknown Source)
at com.ibm.db2.jcc.t4.wb.a(Unknown Source)
at com.ibm.db2.jcc.am.gp.a(Unknown Source)
at com.ibm.db2.jcc.am.gp.d(Unknown Source)
at com.ibm.db2.jcc.am.gp.a(Unknown Source)
at com.ibm.db2.jcc.am.gp.c(Unknown Source)
at com.ibm.db2.jcc.am.gp.executeBatch(Unknown Source)
at org.apache.commons.dbcp2.DelegatingStatement.executeBatch(DelegatingStatement.java:345)
at org.apache.commons.dbcp2.DelegatingStatement.executeBatch(DelegatingStatement.java:345)
at com.ibm.ccd.common.context.common.DBContext.commitPrepBatch(DBContext.java:815)
... 14 more

Data model updates

Verify all the objects present in the environment including Catalog, Collaboration area, and Workflow before beginning with the business flow.

Workflow out script is attached to the workflow steps.
Custom property is attached to the GDS Product catalog.
Custom property is attached to the GDS Product catalog.

IBM MQ-related

If the mq.xml file is not generated in the $TOP/etc/default folder, create a new file by copying the mq.xml.default file and then run the configure configureEnv command in the $TOP/bin folder.

gdsConfig.properties file

The file should be present in the $TOP/mdmui/dynamic/mdmrest folder for GDS to work.

gds.properties file

The file should be present in the $TOP/etc/default folder. After the build is deployed, you should verify the presence of the file and its content.

gdsSupplySideTradeItemFunctions.properties file

The file should be present in the $TOP/etc/default folder. After the build is deployed, you should verify the presence of the file. If the file is not present in the folder, you can create a new file by copying the gdsSupplySideTradeItemFunctions.properties.default file.