Highlighted
Acclaimed Contributor.
Acclaimed Contributor.
1156 views

Several WebTiers

Hello.

Can you help to know how can i setup several webtiers to one SM application ?

For example there is one webtier with address: http://FQDN/sm9/index.do

And i need add another one version of webtier - 9.35

So i add new webtier sm935 to Tomcat-Webapps folder.

Where do i need configure if this is setuped for SSO (IIS-Tomcat)

0 Likes
16 Replies
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Seversl WebTiers

I did this a long time ago. It's all controlled via the url. Just point it to the right directory on tomcat. For example, http://FQDN/sm9/index.do for your current webtier which point to sm9 on tomcat and http://FQDN/sm935/index.do which point to the directory sm935 on tomcat.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Seversl WebTiers

That's what i asking about - what is "configuration" files contain this settings ?

uriworkermap.properties and workers.properties.minimal in Jakarta\conf folder ?

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Seversl WebTiers

No tomcat settings required. Only SM webtier settings that is required and only settings to point the webtier to your SM db. That is in the SM webtier installation guide. Single tomcat with several SM webtier versions. Next step is just tell your users which url to use for which web tier versions.

If you want better shorter urls, you could look into tomcat aliases and the tomcat settings required.

 

Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Seversl WebTiers

As i know there is settings in web.xml where i specify SM APP (not DB) server (serverhost and port for it)

I'm warry about settings in file - uriworkermap.properties, wich used for SSO (IIS -> isapi_redirect.dll -> Tomcat)

this file specifies where to redirect the URL request (to which worker in Tomcat)

My uriworkermap.properties:

/sm9/*=wlb
/sm9=wlb
/jkmanager=jkstatus

So when i type in url http://FQDN/sm9

Then automatically loading http://FQDN/sm9/index.do

So what will happen if i set new webtier, for example sm935 ?

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Seversl WebTiers

Maybe someone else can help. I don't play that much with Apache Tomcat beyond the standard installs.

0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: Seversl WebTiers

If you are only running the one Tomcat machine, and the sm941 and sm952 webapps are under that one Tomcat, your uriworkermap.properties can be very simple. You only need one worker in workers.properties, and then your uriworkermap.properties can have two lines:

/=workerName

/*=workerName

(I suppose *=workerName might work, though I haven't tried it).

These files really only need to be complex if you are using multiple Tomcat instances and/or multiple machines. For your case, it should be straightforward. Just send any requests to the single worker, and they should direct fine. You'll still need to type http://FQDN/sm941 or http://FQDN/sm952, though.

SHORT ANSWER: If your Trusted-Sign On was already working for the one webapp, it should continue to work unchanged if you drop another folder inside tomcat\webapps; you would just use that new folder name in the URL instead of the previous folder name in the URL.

0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Seversl WebTiers

Thank you.

But, as you tell me -  i have one setuped with TSO webtier (sm93) and now setup new one (sm935) in same tomcat.

And now if just change URL from FQDN/sm93 to FQDN/sm935 then i get error:

404 - File or directory not found.

Server Error
404 - File or directory not found. The resource you are looking for might have been removed, had its name changed, or is temporarily unavailable.
===========
by the way in my file uriworkermap.properties:
/sm9/*=wlb
/sm9=wlb
/jkmanager=jkstatus
 
If i change this to 
/sm935/*=wlb
/sm935=wlb
/jkmanager=jkstatus
 
then new one URL will work fine (but old will be with error as above)
0 Likes
Highlighted
Outstanding Contributor.. Outstanding Contributor..
Outstanding Contributor..

Re: Seversl WebTiers

Do you have any redirects or anything particular in your IIS config?

Can you try with uriworkersproperties like this:

/*=wlb
/=wlb
/jkmanager=jkstatus
0 Likes
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Seversl WebTiers

Yes, of course I have a redirector. (IIS->TomCat)

And I tried setting up like this

/sm9*/*=wlb
/sm9*=wlb
/jkmanager=jkstatus

-------

And this is  did not work (my webtier: sm9 and sm935)

0 Likes
Highlighted
Micro Focus Expert
Micro Focus Expert

Re: Seversl WebTiers

what if you change it to:

sm9/*=wlb
/sm9=wlb 
/sm935/*=wlb
/sm935=wlb
/jkmanager=jkstatus
 
i.e. include all URI paths you need to use
Highlighted
Acclaimed Contributor.
Acclaimed Contributor.

Re: Seversl WebTiers

I did it.

Looks like on user side all work fine (using sm9 and sm935 url SM loading fine)

But now in jakarta isapi_redirect.log error every second - see next part of log.

Spoiler
[Fri Apr 13 09:16:39.923 2018] [1320:2372] [info] init_jk::jk_isapi_plugin.c (2405): Starting Jakarta/ISAPI/isapi_redirector/1.2.28
[Fri Apr 13 09:16:39.939 2018] [1320:2372] [info] init_jk::jk_isapi_plugin.c (2572): Jakarta/ISAPI/isapi_redirector/1.2.28 initialized
[Fri Apr 13 09:16:40.986 2018] [1320:2368] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
[Fri Apr 13 09:16:40.986 2018] [1320:2376] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
[Fri Apr 13 09:16:40.986 2018] [1320:2372] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
[Fri Apr 13 09:16:40.986 2018] [1320:2368] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=61)
[Fri Apr 13 09:16:40.986 2018] [1320:2368] [error] ajp_send_request::jk_ajp_common.c (1507): (ajp13w) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Fri Apr 13 09:16:40.986 2018] [1320:2368] [info] ajp_service::jk_ajp_common.c (2447): (ajp13w) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
[Fri Apr 13 09:16:40.986 2018] [1320:2376] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=61)
[Fri Apr 13 09:16:40.986 2018] [1320:2376] [error] ajp_send_request::jk_ajp_common.c (1507): (ajp13w) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Fri Apr 13 09:16:40.986 2018] [1320:2372] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=61)
[Fri Apr 13 09:16:40.986 2018] [1320:2376] [info] ajp_service::jk_ajp_common.c (2447): (ajp13w) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
[Fri Apr 13 09:16:40.986 2018] [1320:2372] [error] ajp_send_request::jk_ajp_common.c (1507): (ajp13w) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Fri Apr 13 09:16:40.986 2018] [1320:2372] [info] ajp_service::jk_ajp_common.c (2447): (ajp13w) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
[Fri Apr 13 09:16:41.001 2018] [1320:2380] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
[Fri Apr 13 09:16:41.001 2018] [1320:2380] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=61)
[Fri Apr 13 09:16:41.001 2018] [1320:2380] [error] ajp_send_request::jk_ajp_common.c (1507): (ajp13w) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Fri Apr 13 09:16:41.001 2018] [1320:2380] [info] ajp_service::jk_ajp_common.c (2447): (ajp13w) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
[Fri Apr 13 09:16:41.876 2018] [1320:2556] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
[Fri Apr 13 09:16:41.876 2018] [1320:2556] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=61)
[Fri Apr 13 09:16:41.876 2018] [1320:2556] [error] ajp_send_request::jk_ajp_common.c (1507): (ajp13w) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Fri Apr 13 09:16:41.876 2018] [1320:2556] [info] ajp_service::jk_ajp_common.c (2447): (ajp13w) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
[Fri Apr 13 09:16:42.095 2018] [1320:2372] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
[Fri Apr 13 09:16:42.095 2018] [1320:2368] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
[Fri Apr 13 09:16:42.095 2018] [1320:2372] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=61)
[Fri Apr 13 09:16:42.095 2018] [1320:2368] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=61)
[Fri Apr 13 09:16:42.095 2018] [1320:2372] [error] ajp_send_request::jk_ajp_common.c (1507): (ajp13w) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Fri Apr 13 09:16:42.095 2018] [1320:2368] [error] ajp_send_request::jk_ajp_common.c (1507): (ajp13w) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Fri Apr 13 09:16:42.095 2018] [1320:2372] [info] ajp_service::jk_ajp_common.c (2447): (ajp13w) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
[Fri Apr 13 09:16:42.095 2018] [1320:2368] [info] ajp_service::jk_ajp_common.c (2447): (ajp13w) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
[Fri Apr 13 09:16:42.095 2018] [1320:2372] [error] ajp_service::jk_ajp_common.c (2466): (ajp13w) connecting to tomcat failed.
[Fri Apr 13 09:16:42.095 2018] [1320:2368] [error] ajp_service::jk_ajp_common.c (2466): (ajp13w) connecting to tomcat failed.
[Fri Apr 13 09:16:42.095 2018] [1320:2372] [info] service::jk_lb_worker.c (1384): service failed, worker ajp13w is in local error state
[Fri Apr 13 09:16:42.095 2018] [1320:2368] [info] service::jk_lb_worker.c (1384): service failed, worker ajp13w is in local error state
[Fri Apr 13 09:16:42.095 2018] [1320:2376] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
[Fri Apr 13 09:16:42.095 2018] [1320:2376] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=61)
[Fri Apr 13 09:16:42.095 2018] [1320:2376] [error] ajp_send_request::jk_ajp_common.c (1507): (ajp13w) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Fri Apr 13 09:16:42.095 2018] [1320:2376] [info] ajp_service::jk_ajp_common.c (2447): (ajp13w) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
[Fri Apr 13 09:16:42.095 2018] [1320:2376] [error] ajp_service::jk_ajp_common.c (2466): (ajp13w) connecting to tomcat failed.
[Fri Apr 13 09:16:42.095 2018] [1320:2376] [info] service::jk_lb_worker.c (1384): service failed, worker ajp13w is in local error state
[Fri Apr 13 09:16:42.126 2018] [1320:2380] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
[Fri Apr 13 09:16:42.126 2018] [1320:2380] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=61)
[Fri Apr 13 09:16:42.126 2018] [1320:2380] [error] ajp_send_request::jk_ajp_common.c (1507): (ajp13w) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Fri Apr 13 09:16:42.126 2018] [1320:2380] [info] ajp_service::jk_ajp_common.c (2447): (ajp13w) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
[Fri Apr 13 09:16:42.126 2018] [1320:2380] [error] ajp_service::jk_ajp_common.c (2466): (ajp13w) connecting to tomcat failed.
[Fri Apr 13 09:16:42.126 2018] [1320:2380] [info] service::jk_lb_worker.c (1384): service failed, worker ajp13w is in local error state
[Fri Apr 13 09:16:42.907 2018] [1320:2656] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
[Fri Apr 13 09:16:42.907 2018] [1320:2656] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=61)
[Fri Apr 13 09:16:42.907 2018] [1320:2656] [error] ajp_send_request::jk_ajp_common.c (1507): (ajp13w) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Fri Apr 13 09:16:42.907 2018] [1320:2656] [info] ajp_service::jk_ajp_common.c (2447): (ajp13w) sending request to tomcat failed (recoverable), because of error during request sending (attempt=1)
[Fri Apr 13 09:16:43.017 2018] [1320:2556] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
[Fri Apr 13 09:16:43.017 2018] [1320:2556] [info] ajp_connect_to_endpoint::jk_ajp_common.c (922): Failed opening socket to (127.0.0.1:8009) (errno=61)
[Fri Apr 13 09:16:43.017 2018] [1320:2556] [error] ajp_send_request::jk_ajp_common.c (1507): (ajp13w) connecting to backend failed. Tomcat is probably not started or is listening on the wrong port (errno=61)
[Fri Apr 13 09:16:43.017 2018] [1320:2556] [info] ajp_service::jk_ajp_common.c (2447): (ajp13w) sending request to tomcat failed (recoverable), because of error during request sending (attempt=2)
[Fri Apr 13 09:16:43.017 2018] [1320:2556] [error] ajp_service::jk_ajp_common.c (2466): (ajp13w) connecting to tomcat failed.
[Fri Apr 13 09:16:43.017 2018] [1320:2556] [info] service::jk_lb_worker.c (1384): service failed, worker ajp13w is in local error state
[Fri Apr 13 09:16:43.204 2018] [1320:2368] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
[Fri Apr 13 09:16:43.204 2018] [1320:2376] [info] jk_open_socket::jk_connect.c (594): connect to 127.0.0.1:8009 failed (errno=61)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.