...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
| 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.
| Panel | ||
|---|---|---|
| ||
|
...
Using the CC Migrate Task user interface
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
Info 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
...
Source Code Checkout Settings
Provide the following details:
Input | Mandatory | Type | Description | |
|---|---|---|---|---|
Task description | N | Text field | Description of the Bamboo task | |
Disable this task | N | Checkbox | If checked, this task will be disabled | |
Repository | Y | Selection | The name of the repository | |
Checkout Directory | N | Text field | Alternate sub-directory to which the code will be checked out
|
...
| ||||
Force Clean Build | N | Checkbox | Removed the source directory and check it out again prior to each build
|
...
|
...
...
Execute Connector Migration Settings
Provide the following details:
Input | Mandatory | Type | Description | |
|---|---|---|---|---|
Task description | N | Text field | Description of the Bamboo task | |
Disable this task | N | Checkbox | If checked, this task will be disabled | |
Executable | Y | Selection | The name of the DataStage client capability to be used by this task At least one DataStage client capability needs to be defined | |
InfoServer Authentication | ||||
Domain | Y | Text field | The URL <domain name>:<port number> of the IBM Information Server Services tier
| |
...
| ||||
Server | Y | Text field | The URL<domain name> of the IBM Information Server Engine tier
|
...
| ||||
Username | Y | Text field | The username used to connect to IBM Information server
|
...
| ||||
Password | Y | Text field | The password for the username specified above (if you check the Change password box)
|
...
| |||||
Execute Settings | |||||
Project Name | Y | Text field | The name of the IBM Information Server DataStage project containing the job or sequence to execute | ||
Optional parameters | N | Text field | Optional parameters
| ||
Unique CCMigrate Log Filename | Y | Text field | Unique log file name.
| ||
...
| ||||
Root ISX Directory | Y | Textfield | It must match the InfoServer Assets location specified in Artifacts tab | |
Max Threads | Y | Textfield | Number of threads uses for identify before and after status
|
...
| |||
Fail plan when compile error | N | Checkbox | True = Build plan will fail when it encounter compilation error False (default) = Build plan will pass, even if there are compilation error |
...
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 (Content by label) | ||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...
| hidden | true |
|---|
...