brokergatewaymigration Script

MGanesan · January 20, 2018, 10:19am

I installed 9.8 UM with latest fix. I cannot see the brokergatewaymigration script. please advise.
I checked in
On the machine that hosts the target Universal Messaging server, go to the Universal
Messaging_directory /tools/migrate directory, and run the brokergatewaymigration
script.

Jonathan_Heywood · January 20, 2018, 1:53pm

The gateway migration script has only been available since a later UM version than 9.8. You would need to install a later UM version.
Even though the utility will work with older versions of UM (if you copy it to the 9.8 installation) I would not recommend targeting 9.8 at this point as it reaches End Of Maintenance quite soon.

MGanesan · January 22, 2018, 7:07am

Thank you for your reply.

Is it possible to share the script it here ( for Linux)? I will try it 9.8.

Jonathan_Heywood · January 22, 2018, 8:05am

Hi,
I don’t have an installation to hand that includes it. You can easily install a later version (I recommend 9.12 or 10.1) in a separate directory and then copy the script to your 9.8 installation.

MGanesan · January 22, 2018, 1:25pm

Hi ,

Ok, I will check. I have few queries on this migration activity. Can you clarify?

what is the difference between JNDI migration and JMS migration script?
where to use JNDI and where to use JMS Script
3.How broker client groups are get migrated to UM, where to see in UM
for broker trigger and document migration for webMethods messaging, do we need to run only the specified service in the document or do we need to do any other steps?
In Gateway Migration, allow forward message and received migrations are getting converted to channel joins automatically?
how to handle G/W level filter in UM?
where to see the G/W Queue length in UM?
can publish / can subscribe, such concepts of Broker is available in UM?

Please help to find the answer.

Jonathan_Heywood · January 22, 2018, 4:11pm

what is the difference between JNDI migration and JMS migration script?
[JH] Each JMS queue/topic consists of two assets: the JNDI destination and the actual queue or topic. The JNDI destination is effectively a pointer to the actual queue/topic. So JNDI migration migrates those pointers, whereas JMS migration migrates the actual queues/topics.
where to use JNDI and where to use JMS Script
[JH] You typically need to do both (if you are using JMS), although the JMS migration has the option to automatically create the JNDI destinations on the target if you want.

3.How broker client groups are get migrated to UM, where to see in UM
[JH] Broker client groups are converted to UM groups. You can see them by selecting the Realm and going to Security.

for broker trigger and document migration for webMethods messaging, do we need to run only the specified service in the document or do we need to do any other steps?
[JH] There is a migration service that you run on IS to update the doc types and triggers. Then you sync the doc type as normal.
In Gateway Migration, allow forward message and received migrations are getting converted to channel joins automatically?
[JH] Gateway routing is converted to remote channel joins by the migration tool.
how to handle G/W level filter in UM?
[JH] Filters are converted by the tool.
where to see the G/W Queue length in UM?
[JH] Channel joins work completely differently in UM - there is no concept of a forwarding queue.
can publish / can subscribe, such concepts of Broker is available in UM?
[JH] Yes - they are part of the channel ACLs.

MGanesan · January 23, 2018, 7:13am

Thank you for your valuable reply. I gone through your replies.in that i have two clarifications.

for broker trigger and document migration for webMethods messaging, do we need to run only the specified service in the document or do we need to do any other steps?
[JH] There is a migration service that you run on IS to update the doc types and triggers. Then you sync the doc type as normal.

Do you refer the below service?

pub.utils.messaging:migrateDocTypesTriggersToUM service.

3.How broker client groups are get migrated to UM, where to see in UM
[JH] Broker client groups are converted to UM groups. You can see them by selecting the Realm and going to Security.

Can you check the attached screenshot? is that correct one where I have to refer the Client groups in Enterprise manager.

Jonathan_Heywood · January 23, 2018, 8:32am

re 4: Yes - that is the correct service.
re 3: Yes - that is correct. Although strictly speaking you don’t need to set up client groups at all if you weren’t using authenticated connections with Broker.
You can set the ACLs to use @

MGanesan · January 23, 2018, 11:58am

Hi Jonathan,

Thank you for the reply.

But I could get your below statement.

re 3: if you weren’t using authenticated connections with Broker.
You can set the ACLs to use @.

Also,
1.Can you tell me where I can find the Broker migrated Gateway level filter conditions in UM?
2. After the JMS migration and JNDI Migration, I could see some Event updated in the UM. I am not getting what it is. can you advise on this? I attached an image for reference.

MGanesan · January 23, 2018, 12:00pm

Hi Jonathan,

Thank you for the reply.

But I could get your below statement.

re 3: if you weren’t using authenticated connections with Broker.
You can set the ACLs to use @.

Also,
1.Can you tell me where I can find the Broker migrated Gateway level filter conditions in UM?
2. After the JMS migration and JNDI Migration, I could see some Event updated in the UM. I am not getting what it is. can you advise on this? I attached an image for reference.

Jonathan_Heywood · January 23, 2018, 12:09pm

If you don’t use authentication with Broker/UM, then you don’t need to worry about client groups at all. Just ensure @ ACL on channels/queues.

Gateway filters can be found in EM by clicking on the channel, then Joins.

The Events you are seeing are not specific to UM. They are related to internal EDA and you can ignore them.

MGanesan · January 24, 2018, 1:11am

Hi Jonathan,

Don’t mistake me. I would like to know more about that.

If you don’t use authentication with Broker/UM, then you don’t need to worry about client groups at all. Just ensure @ ACL on channels/queues.

@* ACL on channels/queues. - I attached the image - (UM_ACL_Section.jp). are you referring that one?
In migrated Client group like JMS Client - Do I need to update @ before that? please see the image - @Clients groups.jpg.
If you don’t use authentication - Here are you referring username/ password authentication and validation? How to do in UM?
few client groups we used to just differentiate the clients. if we migrate those client groups to UM. will it behave same as Broker and does we need to update anywhere in UM? see the attachment (Broker Client Groups.jpg)

I am curious to know more details. that’s why.

MGanesan · January 24, 2018, 1:14am

Hi Jonathan,

Don’t mistake me. I would like to know more about that.

If you don’t use authentication with Broker/UM, then you don’t need to worry about client groups at all. Just ensure @ ACL on channels/queues.

@* ACL on channels/queues. - I attached the image - (UM_ACL_Section.jp). are you referring that one?
In migrated Client group like JMS Client - Do I need to update @ before that? please see the image - @Clients groups.jpg.
If you don’t use authentication - Here are you referring username/ password authentication and validation? How to do in UM?
few client groups we used to just differentiate the clients. if we migrate those client groups to UM. will it behave same as Broker and does we need to update anywhere in UM? see the attachment (Broker Client Groups.jpg)

I am curious to know more details. that’s why.

Jonathan_Heywood · January 24, 2018, 11:01am

@* ACL on channels/queues. - I attached the image - (UM_ACL_Section.jp). are you referring that one?
[JH] Yes - the group Everyone includes @, so if you assign access rights to that group, it applies to unquthenticated users.
In migrated Client group like JMS Client - Do I need to update @ before that? please see the image - @Clients groups.jpg.
[JH] How are you using the Broker client groups? Are you using basic auth (username/password) with Broker? If not, then generally don’t worry about Broker client groups. If you are, then put the relevant users in the relevant groups in UM. UM users are user@host - you can use wild cards. Groups are groups of users, so group names do not include @.
If you don’t use authentication - Here are you referring username/ password authentication and validation? How to do in UM?
[JH] Yes - I am referring to username/password. This can be configured in UM. Please check the UM documentation for details. But if you weren’t using username/password with Broker, then you probably don’t want to use it with UM.
few client groups we used to just differentiate the clients. if we migrate those client groups to UM. will it behave same as Broker and does we need to update anywhere in UM? see the attachment (Broker Client Groups.jpg)
[JH] UM user groups are a little different than client groups in Broker, but they can be used in an equivalent way.

I don’t think I can provide you much more help here. You may need to engage help from a trained partner or Software AG consulting.

Topic		Replies	Views
Migration from Broker to UM – POC webMethods , Universal-Messaging-Broker , Integration-Server-and-ESB	4	1786	April 2, 2021
WARNING : before migrating from broker to UM webMethods , Universal-Messaging-Broker , Integration-Server-and-ESB	15	3429	April 2, 2021
webMethods Nirvana (Universal Messaging) versus webMethods Broker webMethods , Universal-Messaging-Broker , Integration-Server-and-ESB	29	37632	April 2, 2021
Difference between Broker and Universal Messaging webMethods , Universal-Messaging-Broker , Integration-Server-and-ESB	13	14648	April 2, 2021
migration of Broker to UM 9.7 webMethods , Universal-Messaging-Broker , Integration-Server-and-ESB	6	1391	April 2, 2021

brokergatewaymigration Script

Related Topics