Maximo Migration Manager Overview

Migration Manager Overview

Migration Manager Application

The Migration Manager utility is used emigrate configuration content material from one product atmosphere to some other.

You arrange the configuration content material that you need emigrate within the type of bundle definitions and applications. As a part of your implementation of a migration procedure, you utilize the Migration Manager utility to outline and create the bundle definitions, after which distribute and deploy the applications.

For instance, you’ll be able to migrate configuration from a construction atmosphere to a take a look at atmosphere. After checking out, you’ll be able to migrate the configuration to a manufacturing atmosphere. The construction atmosphere is the supply and the take a look at and manufacturing environments are goals. You can use this way throughout the preliminary configuration of the product or whenever you need to modify your configuration of the product.

The Migration Manager utility has the next tabs:

• The Migration Manager utility has the next tabs:

• List: To seek the Migration Manager utility for bundle definitions.

• Package Definition: To outline, save, approve, and turn on bundle definitions.

• Package Definition Structure: To view the hierarchical construction of a bundle definition.

• Distribution: To distribute a bundle from a supply to a goal atmosphere.

• Package: To create, distribute, and deploy bodily applications.

• Messages: To view detailed messages concerning the advent or deployment of bodily applications.

List Tab

You use the List tab to go looking the database for a particular document or crew of data that meet your standards. You use the clear out fields positioned above the List desk window to go into elementary seek standards.

The List tab has an Search Toolbar with the next hyperlinks:

Advanced Search: Select from an inventory of the next choices:

More Search Fields

Enter Where Clause

View Search Tips

Save Query: Select from an inventory of the next choices:

Save Current Query

View/Manage Queries

Package Definition Tab

You use the Package Definition tab within the Migration Manager to create bundle definitions, which can be templates for person applications. A bundle definition organizes the content material to be migrated, and will have to be created earlier than different migration actions happen.

Header

The header space identifies the bundle definition and offers standing knowledge.

Migration Groups segment

Each row within the Migration Groups segment incorporates the next attributes:

Migration Group – Name of the migration crew.

Description – Description of the migration crew

In this segment, you’ll be able to upload migration teams to or delete migration teams from a bundle definition.

You too can set prerequisites for migration gadgets inside a migration crew in a snapshot bundle definition by means of clicking Set Where Clause.

To view dependent migration teams, click on View Details to the left of the Migration Group row.

Dependencies segment

The Dependencies segment lists the teams that the present migration crew depends on. The dependencies are the relationships between the underlying migration gadgets within the database. In this segment, you’ll be able to see whether or not a suite of configuration information in a migration crew is dependent upon some other set of configuration information in a unique migration crew.

Compiled Sources segment

In the Compiled Sources segment, you’ll be able to upload or delete details about compiled assets to or from a bundle definition.

Each row on this segment incorporates the next attributes:

File Name – Name of the compiled supply document.

Description – Description of the compiled supply.

Package Definition

Migration Groups and Compiled Sources

Package definitions can include migration teams and compiled assets.

Migration teams

A migration crew is a number of comparable migration gadgets. A migration object is a gaggle of comparable trade gadgets (database tables).

You use the Migration Groups utility to outline and mixture configuration gadgets, which simplifies the advent of bundle definitions.

Compiled assets

You can come with references to compiled assets in a bundle definition. A compiled supply is any document this is outdoor the product database, however is a part of the Enterprise Archive (EAR) document. Compiled assets can come with many varieties of information, corresponding to elegance information, archive information, symbol information, and houses information. Compiled assets are most often in folders of the product set up, however will also be at the native shopper pc or on a mapped community force

If you wish to have emigrate a couple of compiled supply information, mix them right into a unmarried EAR document to simplify the migration procedure.

Header Area of the Migration Manager Tabs

The Package Definition, Package Definition Structure, Distribution, Package, and Message tabs all have a header space to spot the bundle definition and supply standing knowledge.

The header space has the next fields:

Package Definition Name – The title of the bundle definition.

Source – The title of the product supply atmosphere the place you explained the bundle. This title is a mix of the database host title, the database identifier, and the database schema title. The supply title lets you establish the place the knowledge comes from. The supply title could also be used within the title of a bundle to be sure that each bundle title is exclusive.

Type – The form of bundle definition. A bundle definition is usually a snapshot or a transformation. You specify the sort while you create a bundle definition.

Batch Size – Specifies the collection of data to be retrieved at a time when a bundle is created. The default worth is 100.

Change Role – Specifies a delegated position. Only adjustments made by means of customers on this position are captured by means of the Migration Manager utility when a transformation bundle is created.

Status – An indicator of the migration actions that may be carried out at the bundle definition. The standing may also be WAPPR (looking ahead to approval), APPR (authorized), or LOCKED.

Active – If decided on, signifies that you’ll be able to create a bundle from the bundle definition. For a transformation bundle definition, this take a look at field signifies that the development listeners are registered and that the Migration Manager utility is shooting trade knowledge. An energetic bundle definition can’t be changed. A bundle definition will have to be energetic earlier than it may be used emigrate information.

Change By – The person who final modified the bundle definition.

Change Date – The date that the bundle definition was once final modified.

Package Definition Structure

Package Definition Structure Tab

You use the Package Definition Structure tab to view a hierarchical illustration of the content material that may be within the decided on bundle definition. The hierarchy displays the next knowledge:

– The migration teams within the bundle definition

– The migration gadgets and gadgets buildings in each and every migration crew

– The trade gadgets inside each and every object construction

– Any compiled assets within the bundle definition

Hierarchy segment

The hierarchy segment displays the details about the bundle definition in nested ranges. The root access of the hierarchy is the title of the present bundle definition.

The root access will have the next entries:

Migration Groups – The migration teams within the bundle definition and the migration gadgets in the ones teams. This stage can even have a Dependencies access, which displays the migration teams {that a} specific migration crew is dependent upon.

Package Metadata – The metadata that describes the bundle definition.

Compiled Sources – The compiled supply information which are incorporated within the bundle definition. Each access displays absolutely the trail and document title.

Distribution Tab

You use the Distribution tab to affiliate goals with a bundle definition and to modify or delete those associations.

Distributions segment

Each row within the Distributions segment has the next attributes:

Target Name – Name of our environment to which the bundle in keeping with the bundle definition may also be disbursed.

Description – Description of the objective atmosphere.

Type – The form of goal, both DATABASE or FILE, relying on whether or not the objective is a far flung database or a document on a document machine.

Database URL or File Path – The database URL or absolute trail on a document machine this is out there to the appliance server.

To view main points of a distribution, click on View Details to the left of the distribution row. To delete a distribution, click on Mark Row for Delete to the correct of the distribution row.

Target Details segment

The Target Details segment contains the next fields:

User Name – User title for the objective database.

Schema Name – Name of the database schema.

Change By – The ID of the person that final changed the distribution definition.

Change Date – The date and time of the final adjustments to the distribution definition.

Package Tab

You use the Package tab to accomplish the next duties for a bundle definition:

– Create or delete a bundle

– Distribute or redistribute a bundle

– Download compiled assets in a bundle

– Download a bundle

– Deploy a bundle

– Close a bundle

Packages segment

Each row within the Packages segment contains the next attributes:

Package – Name of the bundle, which is a mix of the bundle definition title and the supply knowledge.

File Name – The title of the bundle with the archive document extension. For a bundle with a database as its goal, this box is empty.

Status – Status of the bundle.

Status Date – The date when the standing was once implemented to the bundle.

To view detailed details about a specific bundle, click on View Details.

Package Details segment

The Package Details segment displays the next fields for the chosen bundle:

Package – The title of the bundle. The title is a concatenation of the bundle definition title, supply, and date and time of advent, separated by means of underscores. For instance, if the bundle definition is MyTest, the supply is ServerA and the date and time is 10 July 2008, 16:00:00, the bundle title is MyTest_ServerA_20080430160000.

Status – Status of the bundle.

Progress Status – Indicates the development of the bundle processing within the supply or goal atmosphere.

File Name – The document title that corresponds to this bundle if a bundle document is generated

Direction – Specifies whether or not the bundle is outbound (from the supply atmosphere) or inbound (to the objective atmosphere).

Redistribution Source – The supply knowledge from the place the bundle is being redistributed. This worth is the mix of database identifier, database schema, and database host title. These values are retrieved from the database server within the atmosphere from the place the bundle is to be redistributed. The redistribution supply isn’t the unique supply of the bundle.

Change By – The person who final modified the bundle.

Status Date – The date and time when the bundle was once final modified.

Readme Information – The knowledge that was once entered when the bundle was once created.

SubTabs

The Package tab has tabs that display extra details about the chosen bundle.

Manifest tab

XML-formatted knowledge that represents the content material of the bundle and the model knowledge. This knowledge is used within the goal atmosphere to deploy the bundle.

Status History tab

The standing and development standing of the advent and deployment of the bundle. This tab has the next fields:

Status – The standing of the bundle.

Progress Status – The development standing of the bundle.

Memo – Information concerning the trade of standing.

Status Date – Date and time when the person modified the standing.

The Details segment displays the next further fields:

Redistribution Source – Indicates whether or not the standing trade was once brought about by means of a redistribution of the bundle. The worth displays the surroundings from the place the redistribution was once initiated. If the bundle isn’t a redistributed bundle, this box is empty.

Change By – The person who modified the standing.

Distribution Tracking tab

Information concerning the historical past of the distributions of the bundle to the objective atmosphere. Primarily signifies the good fortune or failure of the distributions This tab has the next fields:

Target – The atmosphere to which the bundle was once disbursed.

Status – The standing of the distribution.

Status Message – A message concerning the distribution.

Distribution Date – The date the bundle was once disbursed.

The Details segment has the next further box:

Distributed By – The person who disbursed the bundle.

Messages Tab

You use the Messages tab to view messages about bundle definitions and applications. The messages are created when applications are created and deployed. The messages include development knowledge or mistakes.

Message Filter Options segment

Use this segment to clear out the messages. You can choose some of the following choices:

By Package Definition – Shows all messages for all applications that had been comprised of the present bundle definition.

By Package – Shows messages for a unmarried bundle. If you choose this selection, specify a worth within the Filter Package box to choose the bundle whose messages you need to view.

Messages segment

This segment displays the messages for the bundle or bundle definition. The Messages segment has the next fields:

Package – Name of the bundle.

Message – Text of the message. The message may well be truncated on this box.

Message Type – Can be some of the following varieties: INFO, ERROR, or WARN.

Change Date – Date and time when the message was once final changed.

Message Details segment

This segment contains the next further fields:

Message – Full textual content of the message.

Message Details – Additional information about the message, corresponding to this system stack hint.

Change By – The ID of the person who final changed the message.

Migration Groups Application

You use the Migration Groups utility to arrange and crew configuration content material that you need emigrate. After you place up the configuration content material in migration teams, you’ll be able to come with those teams in bundle definitions within the Migration Manager utility. Migration applications may also be comprised of the bundle definitions and those applications can then be migrated to some other machine or atmosphere.

You can paintings with migration teams which are incorporated with the product (inner migration teams) or you’ll be able to create your individual (user-defined) migration teams.

The Migration Groups utility has the next tabs:

List: To seek for migration teams.

Mig Group: To create, view, regulate, or delete migration teams.

Mig Group Structure: To view in a hierarchy the migration gadgets which are contained in a migration crew.

Migration Groups Application List Tab

Migration Group Tab

You use the Migration Group tab within the Migration Groups utility to outline new migration teams and their dependencies. You can use those new migration teams in bundle definitions that you simply create within the Migration Manager utility. The Migration Group tab has the next sections:

Header

Migration Objects

Dependency

Header segment

The header segment has the next fields:

Migration Group – The title of the migration crew.

Migration Group Order – Assign the proper order to migration teams to make sure proper sequential processing of configuration information. If migration teams aren’t ordered as it should be, the deployment of migration applications that include those teams the usage of the Migration Manager utility would possibly fail. For instance, if data in migration crew B are depending on data in migration crew A, specify the proper ordering to be sure that the Migration Manager utility inserts or updates the data from migration crew A into the objective database earlier than putting or updating the data from migration crew B.

Internal – If this take a look at field is chosen, the migration crew is incorporated with the product. The take a look at field is learn simplest. You can’t regulate inner teams.

Migration Objects segment

The Migration Objects segment presentations the migration gadgets in a migration crew. You can view the migration gadgets or upload gadgets to a migration crew that you simply create. Each row on this segment incorporates the next attributes:

Migration Object – The title of the migration object.

Description – The description of the migration object.

Migration Object Order – The order of the migration object inside the migration crew. Objects are processed in sequential order throughout the create and deploy duties of the migration procedure. The worth will have to be distinctive inside the migration crew. As a default, the following sequential worth is assigned.

When a bundle is created, the Migration Manager utility assessments the article order to resolve the series through which the migration object are processed. When a bundle is deployed, the Migration Manager utility first populates tables within the goal database with father or mother data, after which populates comparable tables with the comparable kid data.

Internal – If this take a look at field is chosen, the migration object is incorporated with the product. You can’t regulate inner gadgets.

To view detailed details about a specific migration object, click on View Details to the left of the Migration Object row.

Example of migration object ordering

You can use the BPM (Business Process Management) migration crew to transport workflow processes. This migration crew incorporates the next migration gadgets, which will have to be processed within the order proven:

DMACTION

DMROLE

DMCOMMTEMPLATE

DMESCALATION

DMWFPROCESS

The order will have to be adopted as a result of a workflow procedure would possibly seek advice from a number of movements, roles, verbal exchange templates, or escalations. Similarly, an escalation would possibly seek advice from a number of movements or verbal exchange templates, and a template would possibly seek advice from a job.

If those gadgets aren’t processed on this order, the migration would possibly fail, for the reason that machine would possibly try to insert a document right into a desk earlier than putting a comparable and required document right into a comparable desk.

Dependency segment

The Dependency segment lists the teams upon which the migration crew this is proven within the header segment (the present migration crew) depends. These dependencies point out relationships between the underlying migration gadgets within the database.

To view detailed details about a dependency, click on View Details to the left of the Dependent Migration Group column within the Dependency row.

Migration Group Structure Tab

Use the Migration Group Structure tab to view a hierarchical illustration of the recently decided on migration crew, its migration gadgets, and the trade gadgets of each and every migration object.

This tab additionally displays the dependent teams of the recently decided on migration crew, the migration gadgets, and the trade gadgets of each and every migration object.

When you choose this tab, the hierarchy is proven collapsed. Expand the hierarchy by means of clicking the plus symbols.

Object Structures Application

You use the Object Structure tab to spot the gadgets and knowledge fields that contain an object construction. You additionally use the Object Structure tab to outline the next traits of the article construction:

Which machine utility consumes the article construction

Whether you’ll be able to use the article construction to create, replace, and delete object content material or to limit the article construction use to question and to post object content material

Whether you’ll be able to use the article construction to constitute a non-hierarchical construction (flat document information)

The gadgets you’ll be able to come with within the object construction and the relationships between the gadgets

The processing series for kid gadgets that percentage the similar father or mother object

Migration Of Configuration

Migration job drift

1 Define – The procedure of making a bundle definition on your supply atmosphere. A bundle definition defines the bounds of what product configuration content material you need to incorporate in applications in keeping with the definition.

2 Create – Prepare a bundle example containing the product configuration content material in keeping with the bundle definition.

3 Distribute – After you create a bundle, you distribute the bundle to a number of suitable goal environments. You will have to distribute a bundle to a goal atmosphere earlier than you’ll be able to deploy it to that atmosphere. You can distribute to a database goal or document goal. Distributing to database comes in handy when migrating information from construction to check. Distributing to document comes in handy when distributing from take a look at to manufacturing, the place direct get admission to to a manufacturing database may well be strictly managed.

4 Deploy – Directly observe the product configurations contained in a bundle into the objective atmosphere. Back up your goal database earlier than you deploy a bundle to that atmosphere. To maintain the integrity of structural adjustments, you’ll be able to simplest deploy one bundle at a time.