OnDemand User Group

Support Forums => MP Server => Topic started by: Jaydeep Mehta on December 07, 2017, 01:06:34 AM

Title: ARSLOAD Process Need to run from Seprate Server Apart from library and object
Post by: Jaydeep Mehta on December 07, 2017, 01:06:34 AM
Hi All,

We are using CMOD 10.1.0.0 on Linux  and we have one Library server and one Object server .
We don't want to run ARSLOAD process from object server and library server . we want to run load process from another separate Linux server for better performance, reliability, and scalability .

So any one have any idea how we can achieve this..?

What kind of configuration or appropriate software  require to setup the network connection b/w library and object server and how we can do this .

Thanks in advance .

Regards
Jaydeep Mehta
Title: Re: ARSLOAD Process Need to run from Seprate Server Apart from library and object
Post by: Justin Derrick on December 07, 2017, 07:52:21 AM
In the customer sites where I've seen this used, it's as simple as installing CMOD on the system you'll be doing the loading from, and running arsload with the -h parameter and specifying the name of the server you want to load the file to.

Also consider that you may want to enable SSL for loading if your organization requires encryption of data in transit.

-JD.
Title: Re: ARSLOAD Process Need to run from Seprate Server Apart from library and object
Post by: Jaydeep Mehta on December 12, 2017, 04:03:07 AM
Hi JD,

Thanks for update , will follow the same approach .


Regards
JD
Title: Re: ARSLOAD Process Need to run from Seprate Server Apart from library and object
Post by: jsquizz on December 12, 2017, 11:16:11 AM
Jaydeep I've seen this work well too.

The environment I saw was

1) Library server running arsssockd
2) Obj server running arsobjd + tsm server
3) "Utility" server running arsload daemon, as well as any other custom code.
Title: Re: ARSLOAD Process Need to run from Seprate Server Apart from library and object
Post by: Jaydeep Mehta on January 11, 2018, 11:34:54 PM
Thanks for the Update.

It is working for Us as well.