| Author |
Message
|
| Andy |
 Posted: Tue May 20, 2003 7:36 am Post subject: Multiple Systems and Configurations |
 |
|
Centurion
Joined: 14 May 2003
Posts: 122
|
There has been a lot of discussion on these two in the forum, but I am still not sure that what I should do to have multiple systems and multiple configurations working.
I have a standalone Windows2000 system and I want to have 2 systems FMCSYS1 and FMCSYS2 under group FMCGRP. I want to have only FAT client as here we specify the System name when log on. I am going to use GUI based configuration utility.
a) What is the use of having multiple configurations? Even if there is only one system, we can have multiple configurations to connect to the same and we wont have any diffrence what we see after log in using any of these 2?
b) To define one more system, I need to define Systems and Queue Managers in BuildTime(QMGR1,QMGR2) and import the FDL into runtime. Now what else have to be done to make systems ready to use?
c) What is the significance of Queue Prefix in "Client Connection" tab which we assign on click of ADD button in 'Connection Names'?Can it be anything or same for all configurations?
d)Can single configuration connect to both systems?
e)Whats is the meaning of having different Buildtime configurations?(There going to have single Buildtime and Runtime database?)
Multiple systems and multiple configurations both together are confusing and doesnt allow me organize my thoughts 
Thanks 
_________________
Andy |
|
| Back to top |
|
 |
| vennela |
| Posted: Tue May 20, 2003 7:54 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
1 b) I am not sure if this is necessary. I guess the config utility will generate and import the FDL into Runtime.
In Buildtime, I am not sure but if the config utility doesn't do this then you may have to do this.
c) I am not sure but this will be used to define MQ queues I guess.
d) Yes
e) What do you mean by this.
Two buildtimes pointing to one single database -> May be it is possible but it deesn't make sense.
Two buildtimes pointing to 2 databases may be for having two different environments.
Somebody else will be glad to answer (a). |
|
| Back to top |
|
|
| jmac |
| Posted: Tue May 20, 2003 8:35 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
a) I am not sure why you would have multiple configurations over the same database, other than for the WebClient, which is IBM's recommendation.
b) Define QMgr in BT; define new System in BT;. Export FDL; Import into Runtime; Stop/Restart MQWF; Define new configuration using config utility
c) Venny has answered this.
d) I am not certain I fully understand this question, but I believe the answer is yes.
e) I use multiple Buildtimes quite a bit. BUT, you should realize that I look at a lot of FDL for people and never intend to use it. Also, when working on multiple client projects, I tend to keep each BT separate. When I do run things it is in a single Runtime DB. I.E. all my buildtimes point to the same Runtime. In the more "real world" I would think that you would want to have a Single Buildtime per Runtime DB.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| vennela |
| Posted: Tue May 20, 2003 9:01 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
| jmac wrote: |
b) Define QMgr in BT; define new System in BT;. Export FDL; Import into Runtime; Stop/Restart MQWF; |
John:
Do you think this is necessary. I have never done this with 3.3.2 or 3.4. I have never had any problems. I don't remember doing anything other than configuring another system using the config utility. |
|
| Back to top |
|
|
| vennela |
| Posted: Tue May 20, 2003 9:11 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
Sorry....
I think I am wrong. |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue May 20, 2003 9:19 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
John,
| Quote: |
a) I am not sure why you would have multiple configurations over the same database, other than for the WebClient, which is IBM's recommendation.
|
I dont understand this. can you explain what you were thinking about multiple configurations? I thought 'andy' was referring to multiple systems, and they should talk to a single database.
_________________
-Ratan |
|
| Back to top |
|
|
| jmac |
| Posted: Tue May 20, 2003 11:06 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Ratan:
It seems to me that Andy is talking about both... Multiple systems and multiple configurations.
I agree with what you are saying that the multiple configurations and systems all point to the single database. What I don't know is could I add a configuration (why I don't know) and have it point to the existing DB and existing System group. I think the answer is yes.
My original statement with regards to IBM's recommendation refers to the fact that they want us to define a separate configuration for the WebClient that points to the same DB.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue May 20, 2003 12:35 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
| Quote: |
| What I don't know is could I add a configuration (why I don't know) and have it point to the existing DB and existing System group. I think the answer is yes. |
Isnt this how we add systems in a existing group? That is how I do it.
_________________
-Ratan |
|
| Back to top |
|
|
| jmac |
| Posted: Tue May 20, 2003 12:42 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Ratan:
EXACTLY, that's how we add a new system... What I was thinking was a different configuration pointing to the existing system. I.E 2 different configs pointing at exactly the same thing.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| Ratan |
| Posted: Tue May 20, 2003 12:46 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
Is it even possible. I thought a configuration always points to the Database (group) as opposed to a system.
_________________
-Ratan |
|
| Back to top |
|
|
| jmac |
| Posted: Tue May 20, 2003 1:06 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Ratan:
Never tried it... But cant afford to now, since I wouldnt have time to rebuild my system if it causes a problem.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| Andy |
| Posted: Wed May 21, 2003 8:02 am Post subject: |
|
|
Centurion
Joined: 14 May 2003
Posts: 122
|
| Quote: |
| It seems to me that Andy is talking about both... Multiple systems and multiple configurations. |
I want to know about every possibility and difference i.e. single system-multi config,multi systems-multi configs,multi systems-single config.
| Quote: |
Quote:
| Quote: |
| What I don't know is could I add a configuration (why I don't know) and have it point to the existing DB and existing System group. I think the answer is yes. |
Isnt this how we add systems in a existing group? That is how I do it. |
1.What happens when we create new runtime database using configuration utility? Do we create new System Group? If yes, is it related someway to earlier existing configurations ?Do we now need to cofigure BuildTime for new database(System Group), so that we have 1-1 and in sync Runtime n Buildtime database?
2.I noticed that when we point to one database, there is always a System name is configuration connection string like-FMCSYS.FMCGRP,FMC,FMCQM
So we point not only to database but System also. Whats is the use of pointing to same database through different Systems? How is it useful in real time enviournment?
Also:
Looking at the Configuration Utility-
On selecting Client option, the warning comes:
FMC33760I:Already configureded q manager found, Do u want to use it?
YES:We need to define RTDB,Client Connection
(first thing to specify is these values - FMCSYS.FMCGRP,FMC,FMCQM)
NO :You need to define RTDB,QMngr,Cluster,Client n Client Connection
(So here we can create new QueueManager in cluster )
looking at above, is it correct if I say:
"You can choose any System(Already imported in RTDB from BTDB) and QueueManager to reach to Runtime Database. Configuration just stores the route you are going to use to reach RunTime Database."
My thoughts are becoming organized I guess 
Thanks
_________________
Andy |
|
| Back to top |
|
|
| Ratan |
| Posted: Wed May 21, 2003 9:19 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
| Quote: |
| 1.What happens when we create new runtime database using configuration utility? Do we create new System Group? If yes, is it related someway to earlier existing configurations ?Do we now need to cofigure BuildTime for new database(System Group), so that we have 1-1 and in sync Runtime n Buildtime database? |
If you are creating a new runtime database, you are essentially creating a new Group. There is no and should not be any relevance to the earlier configurations.
| Quote: |
2.I noticed that when we point to one database, there is always a System name is configuration connection string like-FMCSYS.FMCGRP,FMC,FMCQM
So we point not only to database but System also. Whats is the use of pointing to same database through different Systems? How is it useful in real time enviournment?
|
It increases the throughput of your workflow server. There will be a linear growth in performance for each additional system added to a group (atleast this is what IBM claims).
_________________
-Ratan |
|
| Back to top |
|
|
| Andy |
| Posted: Wed May 21, 2003 8:12 pm Post subject: |
|
|
Centurion
Joined: 14 May 2003
Posts: 122
|
Thanks Ratan!!
Any comment from somebody else?
_________________
Andy |
|
| Back to top |
|
|
| Andy |
| Posted: Thu May 29, 2003 6:09 am Post subject: |
|
|
Centurion
Joined: 14 May 2003
Posts: 122
|
I sent private message to slnelson76 to comment on this..I got this reply..
| Quote: |
Well....In general we use 2 systems. One for batch processing the large scale stuff and one that interacts with the users via the web-client. System 1 processes all of our incoming data, inserts stuff into the application DB, then starts processes via XML in System 2. All of the user processes are in System 2. This keeps the heavy load off of the servers handling the user interface activities.
Multiple Groups, in my opinion are for different applications. Because you have 2 different runtime dbs you have 2 different sets of users and user relations. So to me this indicates a seperation of applications.
Hope this helps
-Steve |
Thanks Steve, it clears the picture a little.
_________________
Andy |
|
| Back to top |
|
|
|
|
