Roger..
Will be glad to explain.. please scroll down for my responses to your
questions..
If for any reason you think I have still not clearly explained or if you
haven't understood correctly, feel free to write back either to the list of
me.. I'm installing Patch 7 for my ITSM apps here so I have the time to watch
both the list as well as my personal emails..
Cheers
Joe
----- Original Message ----
From: "Nall, Roger" <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Wednesday, June 4, 2008 1:22:03 PM
Subject: Re: Virtual Server Name
**
Joe,
I am not sure I follow. Here is what I know about Server Groups:
* Only one sever can act as the Admin server.
* Both servers are accessing the same database.
Yes and Yes. Both servers will share the same database but only one of the
servers can act as an admin server which includes the creation or modification
of any workflow.
Here is what I assume if you use the actual Admin server name:
* All workflow should be developed only on the Admin server.
Yes, but its saved on the database that the other servers share, but the cache
on the other servers will not be updated immediatly. The other servers will
however get a signal to recache from the primary admin server. You can set the
time interval that is used for this signal to propogate using the server group
interval
* Any creation/modification of workflow on the non-admin server should
fail.
Yes. I do not have the exact error that you get but it will clearly indicate
that this is not an admin server instance that you are connected to.
* The server reference in the workflow will be the actual server name
of the Admin server.
No. Actual names are no longer stored in the database. The current server is
represented by @ when workflow saves the information to the DB. Its only if you
are doing something to a remote AR Server that the workflow will save the
actual name of the server in the worlfow.
* If the Admin server fails and another server is promoted to the admin
server and creation/modification of work flow will have the server reference of
the new admin server thus creating a condition of have different server
references in different pieces of work flow.
No - for reasons explained above...
Here is what I assume of you use the Virtual server name:
* All servers in the group will have the same Virtual server alias.
For the purpose of connecting - Yes..
* All workflow created/modified will have the same server reference
regardless of which server was the Admin server.
No. Local server is represented in the database as @ in all workflow objects
including table fields. The server name is hardcoded only in case of a remote
server
Of course I have not worked with Server Groups so I am only speculating. I
would think if a user is logged into the non-admin server and performed some
ort of action that required admin functionality that request would be passed to
the Admin server for processing. I am basing all of this on my own experience.
I maintain two servers that access the same database, one active and one
passive. I have the Virtual server name referenced as the alias of both
servers. No matter which server is active I can create/modify workflow and the
only the Virtual server will be referenced.
Thanks,
Roger A. Nall
Manager, OSSNMS Remedy
T-Mobile USA
Desk: 813-348-2556
Cell: 973-652-6723
FAX: 813-348-2565
sf49fanv AIM IM
RogerNall Yahoo IM
________________________________
From:Action Request System discussion list(ARSList) [mailto:
arslist@ARSLIST.ORG ] On Behalf Of Joe DeSouza
Sent: Wednesday, June 04, 2008 12:44 PM
To: arslist@ARSLIST.ORG
Subject: Re: Virtual Server Name
Roger,
If you use the virtual server name, there are chances it might try to save the
workflow on the server that is not owning the admin server operations..
So it is better to check which server has come up as the admin server and use
that server name..
If you choose the virtual server, if at the time of login it gets connected to
the admin server - you would be good to go but if not you will have to keep
attempting to login until you are connected to the admin server.. you will know
you are connected to the admin server if you can see all the Server
configuration options in enabled for admin operations in the Server information
tab from the admin tool - you will need to enable the server information tab
from the registry if you are on ARS 7.1.
Hope this helps..
Joe
----- Original Message ----
From: " Nall, Roger " <[EMAIL PROTECTED]>
To: arslist@ARSLIST.ORG
Sent: Wednesday, June 4, 2008 12:02:12 PM
Subject: Virtual Server Name
**
ARS 7.0.1 patch4
Oracle 10g
HPUNIX
Server Group
Another put a new instance of Remedy into production. This environment has two
application servers behind a load balancer. All users are using the virtual
server name for the load balancer to log into Remedy. We are also using Server
Group technology in this environment.
My big question is when developing workflow what server should be referenced in
the workflow, the virtual server name or the server name of the server that is
acting as the admin server? I am thinking it should be the Virtual Server name.
That way, if the Admin Server falls over and the non-admin server becomes the
admin server there will not be a problem with workflow.
We have another environment that has one active and one passive application
server without a load balancer. We do have a Virtual Server name and IP for
this environment. When developing workflow I reference the Virtual Server name
as the server of record. We have been doing this for years without a problem.
Thanks,
Roger A. Nall
Manager, OSSNMS Remedy
T-Mobile USA
Desk: 813-348-2556
Cell: 973-652-6723
FAX: 813-348-2565
sf49fanv AIM IM
RogerNall Yahoo IM
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
