Hi,
I have some flows with based on below scenario:

Sample1 & Smaple2 are two independent message flows which refer to a common message set SampleMSP based on MRM (built as Independent message broker project) in V10. Common Message set was built as a separate bar file because it needs to be referred by multiple flows, hence it is deployed separately.
Sample1 and Sample2 Msg flows which refer the SampleMSP built as two bar files. All 3 bar files are deployed into a same IntergrationServer.

While migrating the above 3 flows/msg set into V11, not able to create SampleMSP as shared Library (since SharedLibrary is not supporting message set based on MRM). Since SampleMSP is referred by multiple message flows and needs to be deployed independently, what is the best way to migrate the above components to V11? (keeping the reusability of message set )

------------------------------
Thanks,
Santhosh Ramanathan
------------------------------

You're going to need to recreate your message models. Depending on the format of the messages, it will likely be DFDL (for CSV, flat file, record formats, etc). Constructing message models Once you've redefined your message models and stored them in a new Shared Library, you can update your code to use the correct parser. This is how you'll reference the new model in your shared library.
SET OutputRoot.Properties.MessageSet = '{SharedLibraryName}';
SET OutputRoot.Properties.MessageType = '{NameSpaceIfUsedOrEmpty}:NameOfTheMessageModel';

------------------------------
James E. (Jim) Berube
Technical Account Manager (TAM) - Specialist, IBM Expertise Connect
IBM Cloud and Cognitive Software
------------------------------

Original Message:
Sent: Mon October 11, 2021 03:07 AM
From: Santhosh Ramanathan
Subject: Migrating Independent Message Broker project from IIBV10 to ACE 11

Hi,
I have some flows with based on below scenario:

Sample1 & Smaple2 are two independent message flows which refer to a common message set SampleMSP based on MRM (built as Independent message broker project) in V10. Common Message set was built as a separate bar file because it needs to be referred by multiple flows, hence it is deployed separately.
Sample1 and Sample2 Msg flows which refer the SampleMSP built as two bar files. All 3 bar files are deployed into a same IntergrationServer.

While migrating the above 3 flows/msg set into V11, not able to create SampleMSP as shared Library (since SharedLibrary is not supporting message set based on MRM). Since SampleMSP is referred by multiple message flows and needs to be deployed independently, what is the best way to migrate the above components to V11? (keeping the reusability of message set )

------------------------------
Thanks,
Santhosh Ramanathan
------------------------------

Hi Jim,
If I have more than 10 message flows refer to that message set, then wont it be a lot of dev work and testing involves for this change?
can we deploy the flows and message sets as Independent Project (V11 Feature), since no code change involve, it will take less time and testing effort will be considerably reduced.
Please provide your suggestion about it.

------------------------------
Thanks,
Santhosh Ramanathan
------------------------------

Original Message:
Sent: Mon October 11, 2021 01:58 PM
From: Jim Berube
Subject: Migrating Independent Message Broker project from IIBV10 to ACE 11

You're going to need to recreate your message models. Depending on the format of the messages, it will likely be DFDL (for CSV, flat file, record formats, etc). Constructing message models Once you've redefined your message models and stored them in a new Shared Library, you can update your code to use the correct parser. This is how you'll reference the new model in your shared library.
SET OutputRoot.Properties.MessageSet = '{SharedLibraryName}';
SET OutputRoot.Properties.MessageType = '{NameSpaceIfUsedOrEmpty}:NameOfTheMessageModel';

------------------------------
James E. (Jim) Berube
Technical Account Manager (TAM) - Specialist, IBM Expertise Connect
IBM Cloud and Cognitive Software

Original Message:
Sent: Mon October 11, 2021 03:07 AM
From: Santhosh Ramanathan
Subject: Migrating Independent Message Broker project from IIBV10 to ACE 11

Hi,
I have some flows with based on below scenario:

Sample1 & Smaple2 are two independent message flows which refer to a common message set SampleMSP based on MRM (built as Independent message broker project) in V10. Common Message set was built as a separate bar file because it needs to be referred by multiple flows, hence it is deployed separately.
Sample1 and Sample2 Msg flows which refer the SampleMSP built as two bar files. All 3 bar files are deployed into a same IntergrationServer.

While migrating the above 3 flows/msg set into V11, not able to create SampleMSP as shared Library (since SharedLibrary is not supporting message set based on MRM). Since SampleMSP is referred by multiple message flows and needs to be deployed independently, what is the best way to migrate the above components to V11? (keeping the reusability of message set )

------------------------------
Thanks,
Santhosh Ramanathan
------------------------------

You are welcome to try that, but I certainly wouldn't recommend it. At some point, you will need to get off Message Sets and the MRM parser. IBM has been deprecating it since IIB version 9. I wouldn't recommend continuing to try to make it work in version 11 or 12. Yes it's going to be more work, but eventually, you will need to do it.

------------------------------
James E. (Jim) Berube
Technical Account Manager (TAM) - Specialist, IBM Expertise Connect
IBM Cloud and Cognitive Software
------------------------------

Original Message:
Sent: Tue October 12, 2021 03:08 AM
From: Santhosh Ramanathan
Subject: Migrating Independent Message Broker project from IIBV10 to ACE 11

Hi Jim,
If I have more than 10 message flows refer to that message set, then wont it be a lot of dev work and testing involves for this change?
can we deploy the flows and message sets as Independent Project (V11 Feature), since no code change involve, it will take less time and testing effort will be considerably reduced.
Please provide your suggestion about it.

------------------------------
Thanks,
Santhosh Ramanathan

Original Message:
Sent: Mon October 11, 2021 01:58 PM
From: Jim Berube
Subject: Migrating Independent Message Broker project from IIBV10 to ACE 11

You're going to need to recreate your message models. Depending on the format of the messages, it will likely be DFDL (for CSV, flat file, record formats, etc). Constructing message models Once you've redefined your message models and stored them in a new Shared Library, you can update your code to use the correct parser. This is how you'll reference the new model in your shared library.
SET OutputRoot.Properties.MessageSet = '{SharedLibraryName}';
SET OutputRoot.Properties.MessageType = '{NameSpaceIfUsedOrEmpty}:NameOfTheMessageModel';

------------------------------
James E. (Jim) Berube
Technical Account Manager (TAM) - Specialist, IBM Expertise Connect
IBM Cloud and Cognitive Software

Original Message:
Sent: Mon October 11, 2021 03:07 AM
From: Santhosh Ramanathan
Subject: Migrating Independent Message Broker project from IIBV10 to ACE 11

Hi,
I have some flows with based on below scenario:

Sample1 & Smaple2 are two independent message flows which refer to a common message set SampleMSP based on MRM (built as Independent message broker project) in V10. Common Message set was built as a separate bar file because it needs to be referred by multiple flows, hence it is deployed separately.
Sample1 and Sample2 Msg flows which refer the SampleMSP built as two bar files. All 3 bar files are deployed into a same IntergrationServer.

While migrating the above 3 flows/msg set into V11, not able to create SampleMSP as shared Library (since SharedLibrary is not supporting message set based on MRM). Since SampleMSP is referred by multiple message flows and needs to be deployed independently, what is the best way to migrate the above components to V11? (keeping the reusability of message set )

------------------------------
Thanks,
Santhosh Ramanathan
------------------------------