Hi Hugo, BMC only have purposed to upgrade Midtier, but not to configure the ARTCPPORT. I mean, we have turned off the Register-With-Portmapper in these preproduction server, but if we don´t configure the ARTCPPORT on each client, they get a RPC timeout. I can´t understand why, but if we turn it off clients turn it on, if we turn Register-With-Portmapper on, clients only use TCD-Specific-Port, so we have purposed to configure an environment variable (ARTCPPORT) via sms to every non-web clients. We only have one production server, so we have to be totally convinced to introduce changes on production environment, it´s critical for us.
Finally, the solution appears to consist in upgrade Midtier, turn off Register-With-Portmapper and configure ARTCPPORT for every ARS clients. What do you think about it? I can´t risk. How can I set the ARTCPPORT variable on Midtier startup? Regards, Enrique. Hugo Visser-3 wrote: > > OK, one thing to note that setting a server port does not override the use > of a portmapper. If you want the server only to run on a port you should > turn of the "Register-With-Portmapper option. > > Now, since the reporting problem appears to be a known bug, I understand > why > BMC adviced you to use the ARTCPPORT environment variable as that would > override any settings done in the API. And I guess that should have > worked, > but it might be that the ARTCPPORT must be set in a specific environment > (depending on your platform). The only problem with the setting would be > that it would override settings for all servers that the Mid-Tier connects > to, but if you only have one server this shouldn't be a problem. > > Hugo > -- View this message in context: http://www.nabble.com/Midtier-using-RPC-but-ars-is-not-configured-to-tf3757780.html#a10781278 Sent from the ARS (Action Request System) mailing list archive at Nabble.com. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
