Originally posted by: SystemAdmin

We use DataStage TX on Windows with Event Server and are implementing an automated build process which stops the Event Server, deletes old files, pulls type tree and map files from Visual Source Safe and then deploys (using the sdeploy command with deploy scripts created in the integration flow designer), then starts the Event Server. Everything in the Windows batch file appears to work properly, including the sdeploy. All the log files display successful deploy result information for each of the 4 systems involved.

When reviewing the end of the CompoundSystem.txt file, an error is displayed: "Mismatch in card count between MMC (E:\DSTX_Env\System\Maps\SabreParseData.mmc) and MSL".
If I turn off the Event Server, open the .msd file using Integration Flow Designer and deploy (using the same deploy scripts used by sdeploy) and then start the Event Server, it starts successfully.

Here is the Deploy_Dev deploy script with the sdeploy command used: code:1:f6ea32d837sdeploy C:\DSTX_Development\Systems\Navigant_Netprofile.msd Navigant_Netprofile_Dev -DEPLOY Deploy_Dev -LOG AscentialDeploy.log -VERBOSE[/code:1:f6ea32d837]
Any ideas as to why the sdeploy doesn't work with the same .msd, deploy scripts and maps used with Integration Flow Designer?
#IBM-Websphere-Transformation-Extender
#IBMSterlingTransformationExtender
#DataExchange

Originally posted by: SystemAdmin

Sounds like it thinks there's a discrepancy between the number of cards in your mmc and what was deployed.

Does your deploy process recompile the maps or simply redeploy the system?
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange

Originally posted by: SystemAdmin

Yes, that was the issue we found. What confuses me is that the sdeploy uses the same .msd file and the same deploy scripts that the Integration Flow Designer does, and everything deploys sucessfully. BUT it fails when the Event Service is started (as shown in the Startup of the CompoundSystem.txt file).

If the .msd file is opened with the Integration Flow Designer, and the deploy scripts are run, it deploys successfully, and also successfully restarts. When the Integration Flow Designer is closed, there is no message warning to save changes to the .msd file, but maybe the IFD makes changes before deploying.
#IBMSterlingTransformationExtender
#IBM-Websphere-Transformation-Extender
#DataExchange