Re: For midtier/tomcat gurus. Tomcat configuration question

2009-08-25 Thread Lyle Taylor
Rabi,

If I'm understanding things correctly, you've basically got a mismatch between 
how Remedy updated your httpd.conf and your manually maintained 
workers.properties file.  You should be able to comment out the following line 
if it's still there in httpd.conf:

JkWorkersFile /var/tomcat/.../remedy/conf/arsysworker.properties

The reason being, you've got essentially the same things defined in your 
workers.properties file.

I'm not sure about the other jk* lines specific to the Remedy settings - if 
they've already been defined earlier in httpd.conf, you can probably leave them 
as they are above and comment them out in the Remedy section.  You may also 
need to keep this line if you can:

JkOptions +ForwardURIEscaped +ForwardURICompatUnparsed

The one line you probably need to keep would be one like

JkMount  /arsys/* arsysWorker1

If you have that line (or just with arsysWorker), change arsysWorker(1) to 
remedy, as defined in your workers.properties file:

JkMount  /arsys/* remedy

So, you might end up with just this in your Remedy specific section in 
httpd.conf:

JkOptions +ForwardURIEscaped +ForwardURICompatUnparsed
JkMount  /arsys/* remedy

With the options for the remedy work defined in the file referenced here:

JkWorkersFile /someotherlocation/workers.properties

Basically, as I understand it (and my understanding is very limited), in 
httpd.conf, you're simply telling the web server how to hand requests off to 
the application server (Tomcat), defining workers that know where to forward 
requests to.  Tomcat has the application installed and knows where the files 
are, because it is managing the application.  Apache gets a request for 
/arsys/something/or/other, and forwards that request onto Tomcat via the port 
defined in workers.properties.  Tomcat processes the request and send the 
response back to the user through Apache.

Try making those changes and restarting Apache (not Tomcat) and see what you 
get.

Lyle

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Rabi Tripathi
Sent: Tuesday, August 25, 2009 2:36 PM
To: arslist@ARSLIST.ORG
Subject: For midtier/tomcat gurus. Tomcat configuration question

Hi all,
I'm trying to install midtier 7.1 on a solaris box with apache 2.2.8 and tomcat 
5.5.25. 

This apache server hosts many instances of tomcat for use besides Remedy and it 
already has parameters configured that mid-tier install seems to ignore, so 
it's not working for me. My main tomcat admin is out, so it's not helping much.

Midtier installer writes this at the end of httpd.conf
JkWorkersFile /var/tomcat/.../remedy/conf/arsysworker.properties
JkOptions +ForwardURIEscaped +ForwardURICompatUnparsed

This doesn't work because there is already a line such as...
JkWorkersFile /someotherlocation/workers.properties

...on httpd.conf and you can't set this property twice.

The referenced workers.properties file has lines such as this...note that 
remedy specific lines are at the end...as added by tomcat admin:

worker.list= ...,atg_lb, art_lb, wind_lb, rtlt_lb, remedy_lb, jkstatus

...
worker.basetemplate.host=localhost
worker.basetemplate.type=ajp13
worker.basetemplate.socket_timeout=0
worker.basetemplate.connection_pool_size=1
worker.basetemplate.lbfactor=1

worker.nsdl.reference=worker.basetemplate
worker.nsdl.port=9988
worker.nsdl_lb.type=lb
worker.nsdl_lb.balanced_workers=nsdl

worker.remedy.reference=worker.basetemplate
worker.remedy.port=10288
worker.remedy_lb.type=lb
worker.remedy_lb.balanced_workers=remedy
...

First issue I see is "remedy" vs. "arsysworker". Looks like I need to have 
admin change "remedy" to "arsysworker" or on my side...perhaps rename file 
"arsysworker.properties" as "remedy.properties"? Not sure this will suffice.

Or, adding the lines in "arsysworker.properties" directly on the existing
/etc/httpd/conf/workers.properties
should work?

If I do that...I can leave httpd.conf alone and just add these contents of 
"arsysworker.properties" to existing "/etc/httpd/conf/workers.properties"?

worker.list=arsysWorker1
worker.arsysWorker1.port=8088
worker.arsysWorker1.host=localhost
worker.arsysWorker1.type=ajp13

Thinking "arsysWorker1" on the first line can be included on the first 
"worker.list" line of existing workers.properties.
Second line should go with corrected port number
Last two can probably go as they are.

I might have to replace "arsysworker1" with "remedy" to have it work with my 
tomcat admin's setup.

Anybody has anything to say about my musings?

No fun working without much insight into apache/tomcat. I'm blind and just 
feeling my way around.


  

_

Re: For midtier/tomcat gurus. Tomcat configuration question

2009-08-25 Thread Grooms, Frederick W
I believe all Apache defines is the port(s) that are used to send to Tomcat.  I 
think the Tomcat conf/server.xml file defines where the app is located.

Fred

-Original Message-
From: Action Request System discussion list(ARSList) 
[mailto:arsl...@arslist.org] On Behalf Of Rabi Tripathi
Sent: Tuesday, August 25, 2009 4:43 PM
To: arslist@ARSLIST.ORG
Subject: Re: For midtier/tomcat gurus. Tomcat configuration question

Hugo,
I have another install in which tomcat is used only for Remedy and it has 
midtier files on a directory outside of tomcat's. So I would say that it can 
work like you mention, but it's not necessary.

I've been reading up on tomcat on the web and currently I am trying to 
understand how apache/tomcat know where to find midtier's files.

This in httpd.conf...
JkWorkersFile /.../arsysworker.properties

...leads apache to the contents of arsysworker.properties that define  worker 
instances for tomcat...but how does this duo know where midtier files are?

So far a mystery, but I will keep looking.





On Tue, Aug 25, 2009 at 5:00 PM, Hyunkel v2.0  wrote:

**
Per my background using tomcat as JSP Engine for Mid tier, only you need to 
publish the WAR File or install the midtier inside the webapps directory of 
tomcat.

This means to install mid tier under:

apache-directory/tomcat5.5.25/webapps/arsys/

If you do this you'll have the arsys context for application inside the 
tomcat, and you won't need to modify the httpd.conf files or others related to 
apache server (unless you need to make a performance & tunning).

Best regards

Hugo Ruesga
perotsystems(r)
US  972.577.7000
MX +52 (33) 3332.3868

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"


Re: For midtier/tomcat gurus. Tomcat configuration question

2009-08-25 Thread Rabi Tripathi
Hugo,
I have another install in which tomcat is used only for Remedy and it has 
midtier files on a directory outside of tomcat's. So I would say that it can 
work like you mention, but it's not necessary.

I've been reading up on tomcat on the web and currently I am trying to 
understand how apache/tomcat know where to find midtier's files.

This in httpd.conf...
JkWorkersFile /.../arsysworker.properties

...leads apache to the contents of arsysworker.properties that define  worker 
instances for tomcat...but how does this duo know where midtier files are?

So far a mystery, but I will keep looking.





On Tue, Aug 25, 2009 at 5:00 PM, Hyunkel v2.0  wrote:

**
Per my background using tomcat as JSP Engine for Mid tier, only you need to 
publish the WAR File or install the midtier inside the webapps directory of 
tomcat.

This means to install mid tier under:

apache-directory/tomcat5.5.25/webapps/arsys/

If you do this you'll have the arsys context for application inside the 
tomcat, and you won't need to modify the httpd.conf files or others related to 
apache server (unless you need to make a performance & tunning).

Best regards

Hugo Ruesga
perotsystems®
US  972.577.7000
MX +52 (33) 3332.3868




___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"


Re: For midtier/tomcat gurus. Tomcat configuration question

2009-08-25 Thread Hyunkel v2.0

Per my background using tomcat as JSP Engine for Mid tier, only you need to 
publish the WAR File or install the midtier inside the webapps directory of 
tomcat.

This means to install mid tier under:

apache-directory/tomcat5.5.25/webapps/arsys/

If you do this you'll have the arsys context for application inside the tomcat, 
and you won't need to modify the httpd.conf files or others related to apache 
server (unless you need to make a performance & tunning).

Best regards


Hugo Ruesga 
perotsystems® 
US  972.577.7000
MX +52 (33) 3332.3868
P Please consider the environment before printing this email

The information contained in and transferred with this electronic message is 
intended only for the recipient(s) designated above, it is protected by law and 
it may contain information which is privileged and confidential. If you are not 
the intended recipient, please do not read, copy, or use it, and do not 
disclose it to others. Please notify the sender of the delivery error by 
replying to this message, and then delete it from your system. Thank you.






> Date: Tue, 25 Aug 2009 13:35:48 -0700
> From: ars_l...@yahoo.com
> Subject: For midtier/tomcat gurus. Tomcat configuration question
> To: arslist@ARSLIST.ORG
> 
> Hi all,
> I'm trying to install midtier 7.1 on a solaris box with apache 2.2.8 and 
> tomcat 5.5.25. 
> 
> This apache server hosts many instances of tomcat for use besides Remedy and 
> it already has parameters configured that mid-tier install seems to ignore, 
> so it's not working for me. My main tomcat admin is out, so it's not helping 
> much.
> 
> Midtier installer writes this at the end of httpd.conf
> JkWorkersFile /var/tomcat/.../remedy/conf/arsysworker.properties
> JkOptions +ForwardURIEscaped +ForwardURICompatUnparsed
> 
> This doesn't work because there is already a line such as...
> JkWorkersFile /someotherlocation/workers.properties
> 
> ...on httpd.conf and you can't set this property twice.
> 
> The referenced workers.properties file has lines such as this...note that 
> remedy specific lines are at the end...as added by tomcat admin:
> 
> worker.list= ...,atg_lb, art_lb, wind_lb, rtlt_lb, remedy_lb, jkstatus
> 
> ...
> worker.basetemplate.host=localhost
> worker.basetemplate.type=ajp13
> worker.basetemplate.socket_timeout=0
> worker.basetemplate.connection_pool_size=1
> worker.basetemplate.lbfactor=1
> 
> worker.nsdl.reference=worker.basetemplate
> worker.nsdl.port=9988
> worker.nsdl_lb.type=lb
> worker.nsdl_lb.balanced_workers=nsdl
> 
> worker.remedy.reference=worker.basetemplate
> worker.remedy.port=10288
> worker.remedy_lb.type=lb
> worker.remedy_lb.balanced_workers=remedy
> ...
> 
> First issue I see is "remedy" vs. "arsysworker". Looks like I need to have 
> admin change "remedy" to "arsysworker" or on my side...perhaps rename file 
> "arsysworker.properties" as "remedy.properties"? Not sure this will suffice.
> 
> Or, adding the lines in "arsysworker.properties" directly on the existing
> /etc/httpd/conf/workers.properties
> should work?
> 
> If I do that...I can leave httpd.conf alone and just add these contents of 
> "arsysworker.properties" to existing "/etc/httpd/conf/workers.properties"?
> 
> worker.list=arsysWorker1
> worker.arsysWorker1.port=8088
> worker.arsysWorker1.host=localhost
> worker.arsysWorker1.type=ajp13
> 
> Thinking "arsysWorker1" on the first line can be included on the first 
> "worker.list" line of existing workers.properties.
> Second line should go with corrected port number
> Last two can probably go as they are.
> 
> I might have to replace "arsysworker1" with "remedy" to have it work with my 
> tomcat admin's setup.
> 
> Anybody has anything to say about my musings?
> 
> No fun working without much insight into apache/tomcat. I'm blind and just 
> feeling my way around.
> 
> 
>   
> 
> ___
> UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
> Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"

_
Feliz aniversario Messenger!
www.aniversariomessenger.com.mx
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"


For midtier/tomcat gurus. Tomcat configuration question

2009-08-25 Thread Rabi Tripathi
Hi all,
I'm trying to install midtier 7.1 on a solaris box with apache 2.2.8 and tomcat 
5.5.25. 

This apache server hosts many instances of tomcat for use besides Remedy and it 
already has parameters configured that mid-tier install seems to ignore, so 
it's not working for me. My main tomcat admin is out, so it's not helping much.

Midtier installer writes this at the end of httpd.conf
JkWorkersFile /var/tomcat/.../remedy/conf/arsysworker.properties
JkOptions +ForwardURIEscaped +ForwardURICompatUnparsed

This doesn't work because there is already a line such as...
JkWorkersFile /someotherlocation/workers.properties

...on httpd.conf and you can't set this property twice.

The referenced workers.properties file has lines such as this...note that 
remedy specific lines are at the end...as added by tomcat admin:

worker.list= ...,atg_lb, art_lb, wind_lb, rtlt_lb, remedy_lb, jkstatus

...
worker.basetemplate.host=localhost
worker.basetemplate.type=ajp13
worker.basetemplate.socket_timeout=0
worker.basetemplate.connection_pool_size=1
worker.basetemplate.lbfactor=1

worker.nsdl.reference=worker.basetemplate
worker.nsdl.port=9988
worker.nsdl_lb.type=lb
worker.nsdl_lb.balanced_workers=nsdl

worker.remedy.reference=worker.basetemplate
worker.remedy.port=10288
worker.remedy_lb.type=lb
worker.remedy_lb.balanced_workers=remedy
...

First issue I see is "remedy" vs. "arsysworker". Looks like I need to have 
admin change "remedy" to "arsysworker" or on my side...perhaps rename file 
"arsysworker.properties" as "remedy.properties"? Not sure this will suffice.

Or, adding the lines in "arsysworker.properties" directly on the existing
/etc/httpd/conf/workers.properties
should work?

If I do that...I can leave httpd.conf alone and just add these contents of 
"arsysworker.properties" to existing "/etc/httpd/conf/workers.properties"?

worker.list=arsysWorker1
worker.arsysWorker1.port=8088
worker.arsysWorker1.host=localhost
worker.arsysWorker1.type=ajp13

Thinking "arsysWorker1" on the first line can be included on the first 
"worker.list" line of existing workers.properties.
Second line should go with corrected port number
Last two can probably go as they are.

I might have to replace "arsysworker1" with "remedy" to have it work with my 
tomcat admin's setup.

Anybody has anything to say about my musings?

No fun working without much insight into apache/tomcat. I'm blind and just 
feeling my way around.


  

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:rmisoluti...@verizon.net ARSlist: "Where the Answers Are"