|
Thankyou...thankyou... Mr. Richard/Graeme for jumping in and try to help me to over come this problem. Yes ! the WebSphere is running and I had done the same thing what you (graeme) have described and I had the same experience, so, I enabled the "JavaServer Pages" and "URL invocation" from my HTTP server pages (i.e. http://your400:2001 <http://your400:2001> ) and the same line was inserted , what you mentioned i.e......./bootstrap.properties. Only after this I was able to get into my http://your400:9090 <http://your400:2001> (if I remember correctly ) we tried all the options, but we're not successful in testing our WAS by running the following i.e: http://yourServer:xxxx/servlet/HelloWorldServlet <http://yourServer:xxxx/servlet/HelloWorldServlet> . Still any help is greatly appreciated . Am sending my CFG file for your Concerns . <<htpcfg.txt>> THANKYOU VERY MUCH. RAVI. -----Original Message----- From: Richard Dean [SMTP:rddean@gdi.net] Sent: Thursday, January 13, 2000 8:34 PM To: JAVA400-L@midrange.com Subject: RE: WebSphere Question Hi Ravi, Did you ever get your WebSphere going? I noticed from your post that we had similar problems. I got mine going, and I want to see if I could help you if you guys are still having problems. Richard Dean -----Original Message----- From: owner-java400-l@midrange.com [mailto:owner-java400-l@midrange.com]On Behalf Of Jaladi Ravi Kiran, Gurgaon Sent: Monday, January 03, 2000 3:59 AM To: JAVA400-L@midrange.com Subject: RE: WebSphere Question Hi soni, This's with respect to the same question we've raised. We're following the steps given in http://www.as400.ibm.com/websphere <http://www.as400.ibm.com/websphere> For IBM WebSphere Application server getting started V4R4. But here we're unable to complete the Step5 . For implementing this websphere application server apart from the ADMIN and DEFAULT instances and the associated configuration files ADMIN and CONFIG respe...which comes by default with the product, we've created a separate instance and configuration for this implementation(websp). As you said, all the instances (ADMIN,DEFAULT & WEBSP in my case) are started once you start the HTTP server, but the DEFAULT sits in CNDW and WEBSP sits in SIGW status. In order to get the status of WEBSP to CNDW either I'll have to end the DEFAULT instance or Start the WEBSP first than the DEFAULT which ultimately sits in the SIGW status. In this, the instance which sits in the SIGW status will be there for few minutes and than the job gets ended automatically. In which ever way I follow , I never succeeded in completing the STEP:5 as given in the mentioned site. We're going through the FAQ's as per your suggestion and will get back to you with the developments. Before that, we expect your concerns on this. Regards Ravi -----Original Message----- From: niranjan soni [SMTP:niranjan_soni@hotmail.com] Sent: Friday, December 31, 1999 5:07 PM To: JAVA400-L@midrange.com Subject: Re: WebSphere Question Hi Richard I guess u have got things some bit wrong over here.As far the instances under Qhttpsvr are concerned, there are actually two instances one is ADMIN and other one is DEFAULT, if u do not create a new server instance. The default instance of is associated with CONFIG file(the Http Configuration file which is shipped with the AS400) and ur jvm.properties file for Websphere application server points to this CONFIG file. So when the AS400 starts up it brings up all the instances under Qhttpsvr. Now if add websphere support to CONFIG.MBR file and associate two different server instances to the same CONFIG file, then when HTTP start, it will try to bring up both the instances which in ur case are CONFIG and DEFAULT.But as we know there is only one Http Server instance under which the Websphere Application server can run, so it has to be either CONFIG or DEFAULT. If u do WRKACTJOB SBS(QHTTPSVR), u would see ur CONFIG server instance's status at CNDW and ur DEFAULT server instance at SIGW which means that the Websphere is running under ur CONFIG server instance. Hope it answers ur queries. Niranjan >From: "Richard Dean" <rddean@gdi.net> >Reply-To: JAVA400-L@midrange.com >To: <JAVA400-L@midrange.com> >Subject: WebSphere Question >Date: Wed, 29 Dec 1999 17:25:05 -0500 > >So we got WebSphere 1.1 going on our AS/400 running V4R4M0 of the O/S(I >know >there is a version 2.02, but we have not gotten it yet). Anyway we have >gotten to the point where the HelloWorldServlet will come up. I began >looking around in the Active Jobs and I noticed that we have 3 server >instances running under QHTTPSVR. One is "Admin" which I understand, the >other is "Config" and "Default". I have set "Config" up to point to a >sample web page, I have also configured it for WebSphere. This seems to be >working, at least according to the "Hello World" servlet test. I am a >little confused at what the "Default" instance is doing. I noticed that if >I do a ENDTCPSVR on Default, then I can no longer pull up my sample web >page >or the "HelloWorld" servlet. I thought since I configured the "Config" >instance, that the only thing that would be needed running would be the >"Config" instance, but it does not seem to be working that way. When I >restart the "Default" instance(while the "Config" instance is still >running), everything starts working again? It is not a big deal to me if >they both need to be running in order for things to work, I was just >wondering if there was a reason or if I have something set up wrong? > > >Thanks, >Richard > >+--- >| This is the JAVA/400 Mailing List! >| To submit a new message, send your mail to JAVA400-L@midrange.com. >| To subscribe to this list send email to JAVA400-L-SUB@midrange.com. >| To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. >| Questions should be directed to the list owner: joe@zappie.net >+--- ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +--- +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +--- +--- | This is the JAVA/400 Mailing List! | To submit a new message, send your mail to JAVA400-L@midrange.com. | To subscribe to this list send email to JAVA400-L-SUB@midrange.com. | To unsubscribe from this list send email to JAVA400-L-UNSUB@midrange.com. | Questions should be directed to the list owner: joe@zappie.net +---
midrange.com
00010 # HTTP CONFIGURATION FILE
00020 # Enable WebSphere support
00030 Service /*.jsp /QSYS.LIB/QAPPSVR.LIB/QZHJSVLT.SRVPGM:AdapterService
00040 Service /servlet/*
/QSYS.LIB/QAPPSVR.LIB/QZHJSVLT.SRVPGM:AdapterService
00050 ServerInit /QSYS.LIB/QAPPSVR.LIB/QZHJSVLT.SRVPGM:AdapteerInit
/QIBM/ProdData/IBMWebAS/properties/bootstrap.properties
00060 ServerTerm /QSYS.LIB/QAPPSVR.LIB/QZHJSVLT.SRVPGM:AdapterExit
00070 Pass /IBMWebAS/samples/* /QIBM/ProdData/IBMWebAS/samples/*
/QIBM/ProdData/IBMWebAS/samples/*
00080 Pass /IBMWebAS/doc/* /QIBM/ProdData/IBMWebAS/doc/*
00090 Pass /IBMWebAS/system/admin/* /QIBM/ProdData/IBMWebAS/system/admin/*
00100 Pass /IBMWebAS/* /QIBM/ProdData/IBMWebAS/web/*
00110 # ServerInit /QSYS.LIB/QAPPSVR.LIB/QZHJSVLT.SRVPGM:AdapterInit
/QIBM/ProdData/IBMWebAS/properties/bootstrap.properties
00120 # ServerTerm /QSYS.LIB/QAPPSVR.LIB/QZHJSVLT.SRVPGM:AdapterExit
00130 # End - WebSphere support
00140 BindSpecific Off
00150 UserID %%SERVER%%
00160 DNS-Lookup Off
00170 Imbeds On html
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
