...
| Page Properties | ||||||||
|---|---|---|---|---|---|---|---|---|
| ||||||||
|
The MettleCI Connector Migration Tool plugin is used to automate the changing of
...
Jobs to use Connector Stages instead of the deprecated Plug-in and Operator Stages. It uses the IBM-supplied Connector Migration Tool (AKA 'CCMT') which is provided as part of the installation media for each new version of DataStage.
...
| Info |
|---|
The plugin will update and re-compile all Jobs containing the deprecated Stages. |
Instructions
Artifacts
...
MettleCI provides an intelligent wrapper around the Connector Migration Tool to identify and upgrade the relevant jobs, also reporting issues that cannot be resolved by the Connector Migration Tool itself. You can use the Execute Connector Migration Tool task to invoke the Connector Migration Tool and log its output to the Bamboo log.
Configuring the Connector Migration Source Code Checkout Task
Navigate to the Artefacts configuration tab for your job and add a new definition for InfoServer Assets:
Name | Location | Copy pattern | Operations |
|---|---|---|---|
InfoServer Assets | datastage |
| Share |
...
Tasks
...
Create
...
two Bamboo Tasks in the following order:
Source Code Checkout
Execute Connector Migration Tool
Configure each task as described below
| Info |
|---|
...
Note that you may add additional tasks in between Source Code Checkout and Execute Connector Migration Tool |
...
, however Source Code Checkout must always come before Execute Connector Migration Tool. |
...
Using the Source Code Checkout Task user interface
Navigate to the Tasks configuration tab for the job (this will be the default job if creating a new plan).
Click the name of an existing Export DataStage Asset task or click Add Task and then search 'DataStage' to easily locate the Export DataStage Asset task type, in order to create a new task.
Complete the following settings:
Task description | Description of the Bamboo task |
|---|---|
Disable this task |
...
If checked, this task will be disabled |
Repository |
|---|
...
The name of the repository |
Checkout Directory |
|---|
...
...
Alternate sub-directory to which the code will be checked out |
...
| Info | ||
|---|---|---|
| ||
Leave blank |
. It is recommended that you leave this option empty. |
Force Clean Build |
|---|
...
Removed the source directory and check it out again prior to each build |
...
| Info | ||
|---|---|---|
| ||
Checked |
...
. It is recommended that you check this option. |
Click Save
Using the Execute Connector Migration Task user interface
Navigate to the Tasks configuration tab for the job (this will be the default job if creating a new plan).
Click the name of an existing Export DataStage Asset task or click Add Task and then search 'DataStage' to easily locate the Export DataStage Asset task type, in order to create a new task.
Complete the following settings:
Task description | Description of the Bamboo task |
|---|---|
Disable this task |
...
...
If checked, this task will be disabled |
Executable |
|---|
...
The name of the DataStage client capability to be used by this task At least one DataStage client capability needs to be defined |
...
Domain |
|---|
...
...
The URL <domain name>:<port number> of the IBM Information Server Services tier |
...
| title | Suggested Value |
|---|
. It is recommended you use the value |
Server |
|---|
...
...
The URL<domain name> of the IBM Information Server Engine tier |
...
| title | Suggested Value |
|---|
. It is recommended you use the value |
Username |
|---|
...
...
The username used to connect to IBM Information |
...
| title | Suggested Value |
|---|
server. It is recommended you use the value |
Password |
|---|
...
The password for the username specified above (if you check the Change password box) |
...
| title | Suggested Value |
|---|
. It is recommended you use the value |
...
Execute Settings
Project Name |
|---|
...
The name of the IBM Information Server DataStage project containing the job or sequence to execute | |
Optional parameters |
...
...
Optional parameters
|
...
|
...
|
...
|
Unique CCMigrate Log Filename |
|---|
...
Unique log file name. |
...
| title | Suggested Value |
|---|
It is recommended you use the value |
Root ISX Directory |
|---|
...
It must match the InfoServer Assets location specified in Artifacts tab |
Max Threads |
|---|
...
Number of threads |
...
used to identify before and after status |
...
| title | Suggested Value |
|---|
...
. If you don’t have a reason to choose otherwise it is recommended you use the value |
Fail plan when compile error |
|---|
...
|
...
|
...
|
...
|
...
|
Click Save
| Note |
|---|
Remote Agent WorkaroundAtlassian Bamboo Remote Agents running on Windows |
...
( |
...
before Bamboo |
...
v6.10 |
...
If you need to run dm-ccmigrate-plugin via Remote agent you will need to do the following workaround
Remote Agent Workaround
- Configure Bamboo Remote Agent to run as an application user (via Windows Services)
- Add the following 2 paths to the application user path (not system path)
- %SystemRoot%\system32
- <DataStage Client Installation Path>\ASBNode\apps\proxy\cpp\vc60\MT_dll\bin
Bamboo documentation for this workaround
Service wrapper issue - https://jira.atlassian.com/browse/BAM-16205?_ga=2.64634735.17192666.1547599188-2066070865.1384855247
| Info |
|---|
The above work around to overcome the follow 2 errors respectively
|
| Info |
|---|
The above work around may not solve all the problems that might appear as a consequence of this Bamboo bug. If another similar error code appears (E.g. -1073741819) is recommended to:
|
Related articles
| Filter by label (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| hidden | true |
|---|
...
) exhibit a problem for which you may need to implement a workaround documented here. |
Using the Source Code Checkout Task in a YAML pipeline
| Code Block | ||
|---|---|---|
| ||
<TBC> |
Using the Execute Connector Migration Task in a YAML pipeline
| Code Block | ||
|---|---|---|
| ||
<TBC> |