***** SOLVED *****

Hi,

Thank u Hugo. We finally solved the ticket. It was not necessary to upgrade
Midtier. We have introduced the variable of tcp port on the weblogic start
script and IT WORKS! We have create this entry on the
startManagedMidtier.sh:

export ARCTCPPORT = 1234

Thanks a lot, useful help!
Regards,
Enrique.


Hugo Visser-3 wrote:
> 
> I don't know what you mean with "all ars clients". The usertool should
> honour the tcp port settings if you set it at the accounts page and the
> admin tool should do this as well. So on the clients there's no change
> needed.
> 
> As I understand from you, BMC has identified a bug in the Mid-Tier
> reporting
> part that doesn't use the port. So only for the Mid-Tier it would make
> sense
> to set the ARTCPPORT variable. If your platform is a unix flavor such as
> Solaris, you could add this variable to the startscript for the Mid-Tier
> depending on what you are using.
> 
> On windows I think you have to set it on the Mid-Tier server as a global
> environment variable, unfortunately. Upgrading the Mid-Tier should also
> help
> if the bug is resolved in other versions.
> 
> So to sum up:
> - Your server settings are OK, Register-With-Portmapper:F will make sure
> it's not using the portmapper
> - For the usertool and admintool clients you should add the tcp port in
> the
> connection settings
> - For the Mid-Tier you should either upgrade it or try to set the
> ARTCPPORT
> to make the Mid-Tier use the tcp port, not the portmapper. In the long
> run,
> I guess you'd be better off upgrading the Mid-Tier.
> 
> Hugo
> 
> On 5/24/07, Enrique Palazuelos <[EMAIL PROTECTED]> wrote:
>>
>> 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"
>>
> 
> _______________________________________________________________________________
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where
> the Answers Are"
> 
> 

-- 
View this message in context: 
http://www.nabble.com/Midtier-using-RPC-but-ars-is-not-configured-to-tf3757780.html#a11389622
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"

Reply via email to