on ‎2013 Apr 11 9:13 PM
Hello,
We are using SAP Web Dispatcher 7.2 reverse proxy, and we are really stuck at this problem.
Each system (wdisp/system_x) is assigned with the SRCURL parameter along with the specific paths it must foward the requests.
The problem is that we are unable to specify more than 8 sub-parameters in the SRCURL parameter. There is an image of the error attached.
This example executes ok, it has only 8 sub-parameters:
wdisp/system_0 = SID=***, MSHOST=***, MSPORT=***, MSSPORT=***, SRCURL=/irj/;/webdypro/;/pegasus/;/services/;/com.sap.ui.lightspeed/;/rtmfCommunicator/;/com.sap.portal.design.urdesigndata/;/mobile/, SRCSRV=*:***
This example fails, since it has 9 parameters:
wdisp/system_0 = SID=***, MSHOST=***, MSPORT=***, MSSPORT=***, SRCURL=/irj/;/webdypro/;/pegasus/;/services/;/com.sap.ui.lightspeed/;/rtmfCommunicator/;/com.sap.portal.design.urdesigndata/
;/mobile/;/soainterface, SRCSRV=*:***
The server shows the following error on startup (image attached).
*** ERROR => too many sub-parameters (max. 8) for '/irj' [icrxx_mt.c 1580]
Is this value 8 in a paremeter? Can we increase the limit in some way, in a configuration file or database parameter for example?
We appreciate any help.
Thanks.
Request clarification before answering.
Hello Evandro,
I just wanted to confirm Samuli's previous reply: the limit of 8 values for SRCURL is hard coded and cannot be changed. SRCURL and SRCSRV are not meant for very complex configurations.
If you require more flexibility, you should use the modification handler. A good starting point about how to achieve that is the online documentation:
http://help.sap.com/saphelp_nw73/helpdata/en/c5/ec466f5544409982c7d3ca29ce1ad3/content.htm
Best,
Tobias
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Samuli and Tobias,
We had a look on the filtering this week, but hoping to avoid it since we never used the configuration. It seems we have no choice but use it, unless I can reduce the number of paths needed in the scenario. It would work for a while, but not solve the problem.
Thanks for the help.
Probably not, create a customer message to SAP support. Meanwhile you can overcome the limitation by using modification rules to control where to send the requests to.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 9 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 | |
| 2 | |
| 2 | |
| 2 | |
| 2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.