ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » broker schema and patterns

Post new topic  Reply to topic
 broker schema and patterns « View previous topic :: View next topic » 
Author Message
dhireng
PostPosted: Wed Jun 20, 2012 6:58 am    Post subject: broker schema and patterns Reply with quote

Apprentice

Joined: 13 Jun 2011
Posts: 45

I'm I correct in understanding that to create a flow from a pattern and put it in its own broker schema,
1. first you create a flow from the pattern.
2. then define the broker schema
3. move the executable flow (main flow) into the broker schema.

Is this correct?
Are there ways in which you can provide the broker shema name when the pattern is created?
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Wed Jun 20, 2012 11:40 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

you can create the pattern in a broker schema, other than the default schema...
What is behind this question? Do you have naming clashes and need to separate by broker schema?
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
dhireng
PostPosted: Tue Jun 26, 2012 8:08 am    Post subject: Reply with quote

Apprentice

Joined: 13 Jun 2011
Posts: 45

Thanks for the response.
My pattern is created in the schema com.company.test.core but developers are asked to create their flows with
com.company.countrycode.sector.division
depending on the country of the implementation.

In short, naming conventions...
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Tue Jun 26, 2012 12:17 pm    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY

dhireng wrote:
Thanks for the response.
My pattern is created in the schema com.company.test.core but developers are asked to create their flows with
com.company.countrycode.sector.division
depending on the country of the implementation.

In short, naming conventions...

The pattern itself should be more neutral in the naming conventions.
So having it in com.company.core should be ok.
What you might want is to have the pattern instances in their own schema like
com.company.countrycode.sector.division....
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
dhireng
PostPosted: Tue Jul 10, 2012 12:53 am    Post subject: Reply with quote

Apprentice

Joined: 13 Jun 2011
Posts: 45

correct... So, is there a way to get this done?
Back to top
View user's profile Send private message
MBMQDeveloper
PostPosted: Tue Jul 10, 2012 4:11 am    Post subject: Reply with quote

Novice

Joined: 02 Jul 2012
Posts: 19

You can get this done. You can configure the schema in the 'General' section while generating the new instance.
Back to top
View user's profile Send private message
dhireng
PostPosted: Thu Aug 23, 2012 7:39 am    Post subject: Reply with quote

Apprentice

Joined: 13 Jun 2011
Posts: 45

i'm not sure what you mean. can you provide screenshots?
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » broker schema and patterns
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.