Skip to Content
A B

Channel Update

Hi

We need to do a system copy and would like all the channels to be inactive while taking this copy.

so that when the new system comes up, it doesn't get started automatically.

We are currently using PI7.4 dual stack.  Mass channel update is useful only on migration.

any suggestions please?

Regards

Sam

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

3 Answers

  • Feb 02, 2016 at 03:49 PM

    Hi Sam,

    Maybe not the intent of the option but you could likely use channel availability to disable all of the channels in the system for the copy so that it would get pulled into the target system.  Not sure if you are talking about a production system or not however which maybe isn't something you would want to try.

    Regards,

    Ryan Crosby

    Add comment
    10|10000 characters needed characters exceeded

  • Feb 02, 2016 at 03:55 PM

    Hi Sam,

    May be i am little coward but i always prefer to check one by one 😊.

    If you check this link Starting and Stopping - PI (Process Integration) - SAP Library, point 3 in STOP Procedure there is a webservice to let you to stop (not de-active).

    There is a wbservice but i haven't tested yet and i think may be can be use per one channel and not for all like you want SAP PI : Start/Stop Communication Channel using Webservice

    Regards.

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Sam,

      I'm not much of a fan of the use of administrative action.  We recently upgraded to 7.4 single stack and we went with the federated approach for business continuity reasons.  One thing we had always done was set channels to inactive but then the question came up of what would happen on a restart for channels that were turned off by administrative action - what we observed was that after a restart the channels remained off.  The one problem area is that if somehow the same channel is turned off in both systems then I'm not sure which one is supposed to be the primary and have to try and determine which should be running (all our scenarios are duplicated for that same business continuity reasoning - failing in one we can turn it on in the other).

      Regards,

      Ryan Crosby

  • Feb 02, 2016 at 05:19 PM

    Hi Sam,

    Agreeing with Inaki of following one by one approach. In case for system copy you are doing migration/transport then your channel will go to Change List before they get activated

    ( even if in case of CTS the option of automatic activation is enabled then do not transport ICOs until you are done changing channels availability).

    When the channels are there in change list , open them one by one go to advanced tab and select Inactive for channel state and then activate them. and then stop all the channels ..

    then turn them back to active sometime before you require them to be switched on and then start from channel monitor in bulk.#

    This is the best I can think of 😊

    REegards,

    Vikas

    Add comment
    10|10000 characters needed characters exceeded