Back when I was involved with setting up a one-way DSO, you only needed DSO on the server that is sending the information (that was 6.3). Check in your Server information -> connection settings and see if you have a panel for 'DSO Server' - if you do, you can define a DSO Local Password that is then used by the server sending the information and will write the data as a user named 'Distributed Server'. I don't remember offhand in the newer versions whether that panel appears without having the DSO license. I don't remember older versions needing that setting. The other thing to note is there was a 'situation' where if you were DSO'ing between two different versions of Remedy, the encrypted password did not necessarily save to the ar conf file correctly - you needed to cut and paste directly from one to the other. The good thing about doing that was the system seemed to pick up the new encrypted password immediately.
----- Original Message ----- From: "Karthik" <[email protected]> To: [email protected] Sent: Monday, September 17, 2012 1:00:21 PM Subject: Re: Various Questions related to DSO, Atrium Integrator, Server Group Installation) ** Thanks to Both. Yes, i have implemented server group per BMC guide for a different customer who gave us good amount of time :) however, this customer hav given a strict deadline and i am trying to see what are the options. Pritch, so, if i understand your response to 2nd question correctly, you are saying that we dont need a 2nd server just for DSO purpose correct? -Karthik On 17 September 2012 21:31, pritch < [email protected] > wrote: For number 1 - if you're using the ARS Server group install (as LJ noted) you need to refer to the documentation. You would use the ranking forms to determine which server is the primary for each function (ie email) and which is secondary - with that, both servers will have the function active, but will determine which server does what based on the rank for that function. If you're just having multiple AR Servers point to the same database (ie a manual server group) then you would need to shut down each function (ie email, escalations, etc) on all but one of the servers so you don't end up with redundant processes. For number 2 - the answer is yes - DSO doesn't actually talk to DSO - it talks to the Arserver process as another user (can be set up via private threads). You can cross versions with a lower version talking with a more recent version (and vice versa) but need to be aware that only the functionality of the lower version will apply (ie if functionality was added for 7.6, the 7.1 version would not be aware of it or understand it. ----- Original Message ----- From: "LJ CTR MDA Longwing/IC" < [email protected] > To: [email protected] Sent: Monday, September 17, 2012 11:36:38 AM Subject: Re: Various Questions related to DSO, Atrium Integrator, Server Group Installation) Karthik, Running two independent Remedy applications against the same DB is possible, and supported, but has caveats, like the fact that you don't want escalations enabled on both machines. You will want to read up on the configuration in the server group documentation before embarking down this road -----Original Message----- From: Action Request System discussion list(ARSList) [mailto: [email protected] ] On Behalf Of Karthik Sent: Monday, September 17, 2012 9:24 AM To: [email protected] Subject: Various Questions related to DSO, Atrium Integrator, Server Group Installation) ** Hi listers, Trying to understand below things and your help in the same is appreciated: 1. Server group Installation I want to install server group in this fashion because of reduced timelines. a) Install Server 1 b) Start performing data load and other configurations on this server 1 c) Parallel to point "b" above start installing server 2 as a stand-alone server but pointing to the same DB d) Once Server 2 is also up, tie these 2 servers in the group by setting the server group configurations in various places Question 1) Is this feasible Question 2) If yes to question 1 above, will I face any problems with step b above if I run step c in parallel to step b 2. Configuring DSO between servers Scenario: Server 1 on version 7.6 Server 2 on version 7.1 Question 1) Can I configure DSO between these 2 servers In context? i.e. is DSO backward compatible? Question 2) What is the optimum configuration for achieving DSO? Do we need a separate servers tied to Server 1 and Server 2 for only handling DSO operations? or can we reuse the same servers. Point to note here is that the Server1 and Server 2 are seperate instances and have seperate DB 3. Atrium Integrator on 8.0/7.6.04 versions Question: Do we need Atrium Integrator to be installed as a separate server or can I install on the same remedy host? Regards, Karthik _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are" _attend WWRUG12 www.wwrug.com ARSlist: "Where the Answers Are"_ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug12 www.wwrug12.com ARSList: "Where the Answers Are"
