Received: from [10.159.233.145] (/10.159.233.145) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Wed, 19 Jan 2011 10:31:46 -0800 Message-ID: <4D372DFF.70002@oracle.com> Date: Wed, 19 Jan 2011 10:31:27 -0800 From: Bill Weber User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.2.13) Gecko/20101207 Thunderbird/3.1.7 MIME-Version: 1.0 To: Andy Bang CC: Mark Matthews , Mark Leith , Gary Whizin Subject: Re: EM-3816 - Include the "tomcat-native" packages with our Dashboard installations References: <4D364218.3070707@oracle.com> In-Reply-To: <4D364218.3070707@oracle.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Andy, It seems the SSL Agent is up and running fine, so...success! :) Thanks again for the great instructions, it is very much appreciated. Bill P.S. This is using 2.3.2.2048 Monitor and 2.3.2.2051 Agent. On 1/18/2011 5:44 PM, Andy Bang wrote: > Bill, > > Before I update the build system to fix this issue, and then have > BitRock do their part, could I ask you (or one of your guys) to please > do a sanity check for me? > > The basic idea is to start from a 2.3.2 install that's set up to use SSL > between the Agent and the Service Manager, perform the steps below, and > see if it all works: > > 1) Untar 1 of the 2 attached Tomcat native tar.gz bundles to the > apache-tomcat directory (one is for a 32-bit system, the other for a > 64-bit system). There are bin, include, and lib sub-directories in the > tar.gz bundles which correspond to the bin and lib directories under > apache-tomcat, but only the lib sub-directory seems to have anything > useful in it. > > 2) Create an apache-tomcat/ssl directory and put the 2 attached PEM > files in it. > > 3) Update server.xml per step #6 in the attached email. Note the 2 new > SSLCertificateFile and SSLCertificateKeyFile parameters, which need a > path to the PEM files. > > 4) Restart Tomcat. > > 5) Be sure an Agent is configured to use SSL and restart it if necessary. > > 6) Let us know what happened! :) > > 7) If it doesn't work, then please try step #4 in the attached email as > well (adding the LD_LIBRARY_PATH line to setenv.sh). > > Sorry about all the work, but I really think it's better to start this > way than jam it all under source control and deal with it then. > > Thanks, > > Andy