Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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.

The plugin will update and re-compile all Jobs containing the deprecated Stages. 


Instructions

Artifacts


Go to Artifacts tab, and add a new definition for InfoServer Assets


NameLocationCopy patternOperations
InfoServer Assetsdatastage**/*Share


Tasks


Create 2 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.





InputMandatoryTypeDescription
Task descriptionNText fieldDescription of the Bamboo task
Disable this taskNCheckboxIf checked, this task will be disabled
RepositoryYSelectionThe name of the repository
Checkout DirectoryNText field

Alternate sub-directory to which the code will be checked out

Suggested Value

Leave blank

Force Clean BuildNCheckbox

Removed the source directory and check it out again prior to each build

Suggested Value

Checked


InputMandatoryTypeDescription
Task descriptionNText fieldDescription of the Bamboo task
Disable this taskNCheckboxIf checked, this task will be disabled
ExecutableYSelection

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
DomainYText field

The URL <domain name>:<port number> of the IBM Information Server Services tier

Suggested Value

${bamboo.Domain}

ServerYText field

The URL<domain name> of the IBM Information Server Engine tier

Suggested Value

${bamboo.ServerName}

UsernameYText field

The username used to connect to IBM Information server 

Suggested Value

${bamboo.DatastageName}

PasswordYText field

The password for the username specified above (if you check the Change password box)

Suggested Value

${bamboo.DatastagePassword}

Execute Settings

Project NameYText fieldThe name of the IBM Information Server DataStage project containing the job or sequence to execute
Optional parametersNText field

Optional parameters

  • -R to run the process in preview mode

Preview mode = list the jobs that needs Connector Migration, but will not modify the jobs

Unique CCMigrate Log Filename

YText field

Unique log file name.

Suggested Value

${bamboo.buildKey}.log

Root ISX DirectoryYTextfield

It must match the InfoServer Assets location specified in Artifacts tab


Max ThreadsYTextfield

Number of threads uses for identify before and after status

Suggested Value

8

Fail plan when compile errorNCheckbox

True = Build plan will fail when it encounter compilation error

False (default) = Build plan will pass, even if there are compilation error


Due to a known bug with Bamboo Remote Agent running on Windows. (If running Bamboo 6.10 or higher, the following no longer applies as the Bamboo Bug has been fixed)

If you need to run dm-ccmigrate-plugin via Remote agent you will need to do the following workaround

Remote Agent Workaround

  1. Configure Bamboo Remote Agent to run as an application user (via Windows Services)
  2. 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

https://confluence.atlassian.com/bamkb/bamboo-or-remote-agent-does-not-pick-up-the-path-environment-variable-correctly-when-running-as-a-windows-service-323982768.html

Service wrapper issue - https://jira.atlassian.com/browse/BAM-16205?_ga=2.64634735.17192666.1547599188-2066070865.1384855247


The above work around to overcome the follow 2 errors respectively

  • 'chcp' is not recognized as an internal or external command, operable program or batch file.
  • the Return Code -1073741515

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:

  • Copy the value of the system Path environment variable and append it to the local user Path environment variable that is configured to run the Bamboo remote agent service.


Filter by label

There are no items with the selected labels at this time.

  • No labels