ferrofunding.blogg.se - Project naming tool

#PROJECT NAMING TOOL FULL#
#PROJECT NAMING TOOL PASSWORD#
#PROJECT NAMING TOOL WINDOWS#

To access an InfoSphere DataStage server that is remote from the domain server, specify the project name in full as server:/ project. In the Project field, enter the name of the project.

#PROJECT NAMING TOOL PASSWORD#

In the Password field, enter your InfoSphere DataStage password.ĭ. In the User name field, enter your InfoSphere DataStage user name.Ĭ. The host name that you specify here is the same one that you specify when you start the Designer client, for example, mymachine:9080).ī. You can specify an optional port by separating it from the host name with a colon. In the Host field, enter the host name of the services tier. In the Log on window, complete these fields:Ī. You must have sufficient user privileges to create and modify the jobs that you are migrating.ġ.Ĝhoose Start > Programs > IBM InfoSphere Information Server > Connector Migration Tool.Ģ. You use the same project connection details to connect to the Connector Migration Tool as you use to connect to the InfoSphere™ DataStage® and QualityStage Designer or InfoSphere DataStage and QualityStage Director Client. Use the Connector Migration Tool to view which jobs and stages are eligible for migration and then migrate them to use connectors rather than plug-in and operator stages. Note: Throughout this documentation, the term "job" refers to parallel shared containers and server shared containers, as well as IBM® InfoSphere™ DataStage® jobs.

Produce a report of jobs and their stages and stage types.

You can review the results and then refine the migration as necessary before you run the actual migration.

Run a practice migration, where the actual migration does not take place but the possible results of the migration are placed in the log file.

Specify a list of stage type names to limit the jobs that are considered for migration.

Specify a list of shared container names to be considered for migration.

Specify a list of job names to be considered for migration.

Using the command line, you can perform these additional tasks: The Connector Migration Tool command line options provide the same functionality as the user interface, as well as a few additional options. The job is migrated and placed in the same folder as the original job, and the log file CCMigration.log, which records the results of the migration, is created in the current directory. Either way, your original job is never lost. You can make a backup copy of the job and then migrate the backup, or you can make a backup copy of the job and then migrate the original job.

The tool gives you a chance to make a backup of a job before you migrate it. To refine the list of jobs to evaluate, you can specify that only jobs that contain specific plug-in and operator stages be listed. You select the jobs that you want to migrate, and beside each job name, the tool displays an icon that indicates whether or not the job can be fully migrated, partially migrated, or not migrated at all. The user interface leads you through the process of evaluating which jobs, shared containers, and stages to migrate. If you start the tool from the command line, additional options that are not provided in the user interface are available.

#PROJECT NAMING TOOL WINDOWS#

To run the Connector Migration Tool, start it from the Microsoft Windows Programs menu or from the command line. To take advantage of the additional functionality that connectors offer, use the Connector Migration Tool to migrate jobs to use connectors instead of plug-in and operator stages.