It’s essential for each finish product to fulfill/excel Buyer expectations. For a profitable supply, it isn’t nearly doing that issues however about the way in which it’s accomplished by following/implementing the specified requirements.
This submit explains the next finest practices to be thought-about with IDMC CDI ETL throughout the under phases.,
- Native Datatypes verify between Database desk DDLs vs IDMC CDI Mapping Supply/Goal/Lookup objects.
- If any consistency seen in IDMC mappings with Native Datatype/Precision/Scale, guarantee to edit Metadata to maintain them in sync between DDL and CDI mappings.
- In CDI, workflow parameter values with the intention to be consumed by the taskflows, a Dummy Mapping activity must be created the place the listing of Parameters/Variables have to be outlined for additional consumption by duties throughout the taskflows (Ex. Command activity/E-mail activity and so forth)
- Make certain to restrict the # of Dummy Mapping duties throughout this course of
- Finest observe is to create 1 Dummy Mapping activity for a folder to seize all of the Parameters/Variables required for that complete folder.
- For Variables whose worth must be persistent for the following taskflow run, be certain that the Variable worth is mapped to the Dummy Mapping activity by way of an Task activity. This Dummy mapping activity can be used on the START & END of the taskflow to make sure the general taskflow processing is enabled for Incremental Information processing.
- If some Audit classes are anticipated to run concurrently inside different taskflows guarantee enabling the property “Permit the mapping activity to be executed concurrently”.
- Keep away from utilizing the SUSPEND TASKFLOW possibility because it requires guide intervention throughout JOB RESTARTs. Additionally this property might trigger points throughout Job RESTARTs.
- Guarantee appropriate parameter illustration utilizing Single Greenback/Double Greenback. Incorrect illustration will trigger the parameters not READ by CDI throughout Job runs.
- Whereas working with Flatfiles in CDI mappings, at all times allow the property “Retain present fields at runtime”.
- If a sequence generator is probably going for use in a number of classes/workflows, higher to make it as REUSBALE/SHARED Sequence.
- Use Sequential File connector kind for mappings utilizing Mainframe VSAM Sources/Normalizer.
- If a session is configured to have STOP ON ERRORS >0, make sure the LINK situations for the following activity to be “PreviousTask.TaskStatus – STARTS WITH ANY OF 1, 2” inside CDI taskflows.
- For mapping activity failure flows, set the LINK situations for the following activity to be “PreviousTask.Fault.Element.ErrorOutputDetail.TaskStatus – STARTS WITH ANY OF 1, 2” inside CDI taskflows.
- Partitions will not be supported with Sources below Question mode. Guarantee a number of classes are created and run in parallel as a workaround.
- At the moment parameterization of Schema/Desk not doable for Mainframe DB2. Use ODBC kind connection to entry DB2 with Schema/Desk parameterization.
- Use Verbose knowledge Session log config provided that actually required and that too in decrease env solely.
- Make sure the Classes choose the parameter values correctly throughout job execution
- This may be verified by altering the parameter names, values to incorrect values and decide if the job fails throughout execution. If the job fails, it implies that the parameters are READ appropriately by the CDI classes.
- Make sure the Taskflow identify and API identify at all times match. If completely different the job will face points throughout execution by way of runAJobCli utility from the command immediate.
- CDI doesn’t retailer logs past 1000 mapping duties run/3 days on Cloud (it does retailer in Safe Agent). To retain Cloud job run stats, create Audit tables and use Information Market utility to get the Audit data (Quantity processes, Begin/Finish time and so forth) loaded to the Audit tables by scheduling this job at common intervals (Hourly or Day by day).
- As a way to guarantee no points with Generic Restartability throughout Operations, guarantee a Dummy task activity is launched every time the code incorporates Customized error dealing with stream.
- As a way to facilitate SKIP FAILED TASK and RESUME FROM NEXT TASK operations, guarantee each LINK situation has an extra situation appended “Mapping activity. Fault.Element.ErrorOutputDetail.TaskStatus=1”
- If mapping activity log file names are to be suffixed with Concurrent run workflow occasion identify, guarantee it’s accomplished throughout the Parameter file. IDMC mapping activity config stage just isn’t succesful as a result of parameters concatenation points.
- Guarantee to repeat mapping activity log recordsdata in Safe agent server after job run since IDMC doesn’t honour “Save Session log for these runs” property set on the mapping activity stage when session log file identify is parameterized.
- Guarantee Session Log File Listing doesn’t include / (Slash) when used together with parameters (ex., $PMSessionLogDir/ABC) below Session Log Listing Path. When used this might append each run log to the identical log file.
- Concurrent runs can’t be carried out on taskflows from CDI Information Integration UI. Use Paramset utility to add concurrent paramsets and use runAJobCli utility to run taskflows with a number of concurrent run situations from the command immediate.
Along with coding finest practices, following these Improvement and Operations finest practices will assist keep away from rework and save efforts thereby reaching buyer satisfaction on Supply.
