cancel
Showing results for 
Search instead for 
Did you mean: 

MDM check list for post go live Activity

Former Member
0 Kudos

IF Any body having MDM check list for post go live .plz tell me wat they are ?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

HI Swarupa

the checklist will be different depending on the type of MDM implementation. Some of the examples are-

1. Use of MDIS and MDSS (backup frequency, archiving of the inbound/outbound folders, maintenace of MDIS and MDSS ini files)

2. Using MDM as UI (Backup of all import and syndication maps, schemas, temlates files used for import, initail data load)

3. Use of Portal (Portal configurations, User mapping, ....)

3. Handover documents for the support team with kind of defects coming and their possible solutions.

hope this helps

Ravi

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Swarupa,

Check the below parameters before Go-Live

Ports

Maps(Bothe Import and Syndication)

Remotesystems

we need to check possible errors while importing and avoid those and create standard template with possible accepted values

syndication maps are properly saved with accepted destination fields

all lookup table with possible values

check the users and their roles properly matched in workflow

validations and assignments with proper reasons

files are moving from Ready to Archive folder is perfect or not

These are main areas we need to concentrate before golive

Hope it helps

Thanks

Yugandhar

Former Member
0 Kudos

Hi Swarupa,

In addition to the points mentioned by above you need to make sure of the following.

The distribution directory path should be maintained in the server .ini files.

The passwords for the workflows and logins used by the servers to connect(DM server, Import Server and Syndication server)should also be maintained correctly.

The Schema files used in imports and syndications should should also be present at the locations defined in the XML shemas section.

Key mappings for look up tables need to be checked. If not maintained could cause exceptions.

The configurations for the maps need to be checked for new or null value handling. (or date format).

If you are automating the process you need to make sure all the required servers are up and funtioning.

Afte MDM 5.5 SP6 we are able to maintian syndicxation times in the console itself. Prior to this batch jobs needed to be created and scheduled. If this is required make sure these jobs timings are also maintained correctly.

Regards,

Aditya.