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.
Configuring the CC Migrate 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 |
Create two Bamboo Tasks in the following order:
Source Code Checkout
Execute Connector Migration Tool
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.
Configure each task as described below
Using the Source Code Checkout Task
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 Suggested ValueLeave blank |
Force Clean Build | Removed the source directory and check it out again prior to each build Suggested ValueChecked |
Click Save
Using the Execute Connector Migration Task
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 Suggested Value${bamboo.Domain} |
Server | The URL<domain name> of the IBM Information Server Engine tier Suggested Value${bamboo.ServerName} |
Username | The username used to connect to IBM Information server Suggested Value${bamboo.DatastageName} |
Password | The password for the username specified above (if you check the Change password box) Suggested Value${bamboo.DatastagePassword} |
Project Name | The name of the IBM Information Server DataStage project containing the job or sequence to execute |
Optional parameters | Optional parameters
Preview mode = list the jobs that needs Connector Migration, but will not modify the jobs |
Unique CCMigrate Log Filename | Unique log file name. Suggested Value
|
Root ISX Directory | It must match the InfoServer Assets location specified in Artifacts tab |
Max Threads | Number of threads uses for identify before and after status Suggested Value8 |
Fail plan when compile error | True = Build plan will fail when it encounters a compilation error False (default) = Build plan will pass, even if there are compilation error |
Click Save
Remote Agent Workaround
Atlassian Bamboo Remote Agents running on Windows (before Bamboo v6.10) exhibit a problem for which you may need to implement a workaround documented here.
Related articles
Filter by label
There are no items with the selected labels at this time.