wgate config url not functioning

[Former Member]

In sap note 688295 it tells you to

Using the WGate Configuration Tool

change file ItsRegistryWGATE.xml (in e.g. c:\program files\sap\its\6.20\config)

search for "<value name="ConfigMonitorEnabled" type="text">no</value>" and change 'no' to 'yes'

call http://hostname.domain.com/scripts/wgate/wgate-restart to reload the WGate configuration file ItsRegistryWGATE.xml

(this will not restart the web server. WGate will check for changes in its XML configuration and reload information if necessary. For most changes, this will happen transparent to the users. Changes to URLs or SNC should not be done with users on the system.)

call http://hostname.domain.com/scripts/wgate/wgate-config for all further configuration

questions

1. When you call these urls are you connecting to your ADM instance or your standard instance

(if you are running ADM and standard instance on the same physical webserver)

I am getting the error that I have specified an invalid service?

Thanks

[Former Member · Accepted solution]

Thanks. I got almost all of it working, except.

In the host:port/scripts/wgate/admin/!

On this site I can see my two hosts for the QAS instance.

Under the listing for the first host all the utilities work.

But for the second host, it says

"Go to Native ADM" When I click this link I get an http 500 error page?

Ever seen this before.

And thanks for all your help!!

[Former Member · Accepted solution]

Ok Jeremy,

after your crash course you now understand how dispatching works on wgate level.

For this we have to trick a bit, actually we repeat the process.

First have a look at the URL that is generated to access the "other" ADM natively (on both A and B you have an ADM running do you?)

The URL is saying something like

/scripts/wgate/admin/!?agate_routing=secondhost

This instructs the wgate to to do the normal prefix URL matching with the extension that it looks for an AGate (in this case an ADM instance) which matches with "Host=secondhost".

i.e. You have to loadbalance your ADM AGates also so that the WGate can find a route to the other ADM (WGate has to know at least the hostname and the AGate port to contact that ADM AGate)

That will do for today, regards,

Fekke

[Former Member]

Thank you very much!!

One more question, what is the purpose of proxy adm?

Which instance should you be proxying ADM or QAS?

Thanks

[Former Member]

Hello Jeremy,

as to my knowledge you have to fill in the remote ADM instance to have monitoring info in one view.

Else you have to use the "switch to native" link to see the info individually for the according QAS instance.

I.e. the local ADM displays the local QAS monitoring info and if filled in it also gets the remote monitoring info by using the proxy connection to the remote ADM instance.

Regards,

Fekke

[Former Member]

I did not try the ? at the end, however when I restarted my adm and qas agates it worked????

[Former Member]

Sure you didn't restart your webserver? Or that your /scripts/wgate/wgate-restart was effective after all?

It might be that wgate does not respond on the first request that is fired when the agates are down since it forks of polling threads for every agate that is not reachable on that request. But from your description you got an answer from the agate saying that the service is not available i.e. wgate is past its initialisation phase.

[Former Member]

Hello Jeremy,

The WGate configuration is a stand-alone tool that runs in the WGate itself, i.e. it is not a service and has nothing to do with the app. part (AGate) and the app. administration tool (ADM).

It is there to make life easier so that you do not have the change the configuration in the XML by hand. The ADM instance on the AGate side has no control over the WGate configuration since in most production environments the WGate and AGate are physically seperated.

Now to your problem:

I can think of two situations which gave you the error:

1) did you type

http://host:port/scripts/wgate/wgate-config!

(with a "bang" at the end?)

then try the correct notation:

http://host:port/scripts/wgate/wgate-config?

2) if the above is not functioning then follow the instructions you described:

• edit ItsRegistryWGATE.xml (make a backup)

• search/change ConfigMonitorEnabled from "no" to "yes"

• save the file

• RESTART your webserver (do it yourself, NOT by a URL)

• then try the correct URL from 1)

Regards,

Fekke