Planned or not planned there is a number of situations where it can be necessary that you do a fast switch of your scenarios between you central and non central adapter engine. If you will do that manually it may take a long time … time that especially in critical situations is not available.

This thread will show you how you can do a fast switch from one to an other machine with the PI Migration Tool.

Open the PI monitoring tool (PIMON http://host:port/pimon) and go to the Migration Tool.

/wp-content/uploads/2016/03/1_913291.png

As soon it’s open it should look like this. Now you have to open the channel migration.

/wp-content/uploads/2016/03/2_913331.png

Now you have to enter the Source and Target System. In your case Source and Traget System will be the same.

/wp-content/uploads/2016/03/3_913332.png

After you entered your user credentials and clicked on the next button you will be able to get a list of all available communication channels.

/wp-content/uploads/2016/03/4_913333.png

You can simply click on the Search Button to get a list of all channels or you can use the filter function.

/wp-content/uploads/2016/03/5_913334.png

In the result list it’s possible to mark several communication channels. Mark all the should be switched.

/wp-content/uploads/2016/03/6_913335.png

As soon the channels are marked you will see in the property window the parameters that can be changed.  Flag the checkbox at the “Adapter Engine” parameter and choose the engine on which the channels should run.

/wp-content/uploads/2016/03/7_913336.png

As soon you have done your selection click on the Apply Button. And after that on the Next Button. (Can be that you have to scroll dwon).

On the next screen you can define the name of the change list where the changes will be added to.

/wp-content/uploads/2016/03/8_913337.png

Click on create to to the changes.

/wp-content/uploads/2016/03/9_913338.png

When all changed have been done you get a protocol about the changes. Click on Finish an start you Integration Builder.

/wp-content/uploads/2016/03/10_913339.png

A problem can be how to identify the channels that have to be moved, especially when you want to move the channels back, later. For that it can be usefull if you include the default machine of a channel in its name (e.g. CC_AEX_MYCHANNEL) or you do a identification via the communication component. In standard all channels of component A are running in the central engine and channels of component b are running on he decentral engine.

That progress can be used also for other mess manipulation like inactivate a huge number of channels.

To report this post you need to login first.

Be the first to leave a comment

You must be Logged on to comment or reply to a post.

Leave a Reply