|
There are two options listed below for having the default server start automatically - the first one is the recommended, always use the console, method. The second one is for the 'I can't have the system operator be expected to bring up an admin console and know what to do' situation. OPTION 1 ---------------- To have the Default Server (or any other application servers once you start creating your own) start automatically when the administrative server starts: End the node from the administrative console specifying Stop for restart while the Default Server application server is started (i.e. in a Running state). You will get the Stop for restart option if you right-click the node (node == host name of your system == administrative server == QEJBADMIN job). Taking this option has the following effect: 1). The administrative server (node) stops any running application servers. In your case this is the Default Server which equates to the DEFAULT_SE job running in the QEJBSBS subsystem. 2). Any running application servers are flagged to be started when the administrative server (node) is started again. 3). The administrative server (node) is stopped. This ends the QEJBADMIN job and QEJBMNTR job The next time you start the administrative server (i.e. STRSBS QEJB/QEJBSBS), the admin server job (QEJBADMIN) will start and then it will start any application servers which were running at the time it was stopped for restart. OPTION 2 ---------------- If you use the following method to do an ENDJOB on the QEJBADMIN job (and only the QEJBADMIN job - let it end the other jobs), any running application servers will be restarted when the administrative server is started again (i.e. when STRSBS QEJB/QEJBSBS is done again). So, prior to IPL'ing do the following: 1). Use ENDJOB OPTION(*CNTRLD) DELAY(600) to end the QEJBADMIN job running in the QEJBSBS subsystem. It is important to specify an adequate number of seconds for the delay parameter. For instance, 30 seconds is NOT enough generally. 600 seconds usually is. Ending the QEJBADMIN job (i.e. the administrative server) in this manner will cause it to end any running application servers and flag them to be started when the admin server starts the next time. The QEJBADMIN job will then end and then the QEJBMNTR job will end. This is all as a result of ending the QEJBADMIN job in a *CNTRLD manner with adequate delay time. 2). End the QEJBSBS once all the jobs have ended due to step 1 above: ENDSBS QEJBSBS 3). IPL 4). When the QEJBSBS subsystem starts from the QSTRUP program after IPL, the application servers that were running will be started. NOTE: The administrative server will take longer to reach the 'ready' state. Frances Stewart WebSphere Application Server for iSeries 400 External: (507) 253-2795 Tie-line: 8-553-2795 IBM Rochester "Claudio Gaiardi" <claudio.gaiardi@GMINFORMATICA.IT>@midrange.com on 02/08/2001 01:42:16 PM Please respond to JAVA400-L@midrange.com Sent by: owner-java400-l@midrange.com To: <JAVA400-L@midrange.com> cc: Subject: Re: WebSphere FixPack Installation You are right: I did install the Fixpack2, but no E-fixes, since I read they are targeted to "...critical problems without a valid workaround..." and usually the best "workaround" is understand what I've missed. Of course now I'll do it. The "extra-pass" is the following: <Pass /WebSphereSamples/* /QIBM/ProdData/WebASAdv/WebSphereSamples/*> as You may see in attached wrkhttpcfg printout, relevant to the original configuration created using the Java servlets link from the IBM HTTP Server for AS/400 Configuration and Administration page. I commented this directive and ordered the expected directives as per the Getting Started Guide. Now, if I don't abuse of your patience, a further question. I realized that even if I added to the QSTRUP pgm the start of the QEJBSBS (which causes QEJBADMIN e QEJBMNTR to start) and the start of the http instance WEBSPHERE (this is the name I choosed), the "Default server" does not start automatically (i.e: I start it manually at the NT console): is it possible to set it to autostart? May be more than obvious, but without starting manually the "Default server" nothing works, while when it is completely started all samples go. This is the situation (from an AS/400 perspective) when all is working: QEJBSBS QSYS SBS 0,0 DEQW DEFAULT_SE QEJB BCI 0,5 JVAW QEJBADMIN QEJB BCI 0,5 JVAW QEJBMNTR QEJB ASJ 0,0 PGM-QEJBMNTR EVTW Many thanks and regards. Claudio Gaiardi ----- Original Message ----- From: "Frances Stewart" <francess@us.ibm.com> To: <JAVA400-L@midrange.com> Sent: Wednesday, February 07, 2001 9:59 PM Subject: Re: WebSphere FixPack Installation > > Claudio, > > Excerpted from below: > - install JDBC driver fails if there is no /home/QEJB dir, specified at > QEJB > user profile level: maually creating it (empty) solved the problem; > > I believe you are missing the e-fix PQ43301 for the administrative console, > called out in the release notes at > > http://www.iseries.ibm.com/products/websphere/docs/relnotes352s.html#Install Inst > > item #4, subitem 5. If you do have that e-fix on the workstation, > something is not quite right and it is not being picked up. The Getting > Started > > > Excerpted from below: > - standard configuration process, put some directives in a different order > vs what stated in the guide, with an extra "pass"; > Did you manually add the directives or did you use the Java servlets link > from the IBM HTTP Server for AS/400 Configuration and Administration page? > What was the extra "pass"? If it was for wssamples, the Java servlets link > should have added that automatically. The Getting Started PDF has sections > for adding the directives both ways (manually and via the link). > > I will forward your samples comments on to the appropriate person. > > Thanks for the feed back. > > Frances Stewart > WebSphere Application Server for iSeries 400 > IBM Rochester > > > "Claudio Gaiardi" <claudio.gaiardi@GMINFORMATICA.IT>@midrange.com on > 02/07/2001 02:07:53 PM > > Please respond to JAVA400-L@midrange.com > > Sent by: owner-java400-l@midrange.com > > > To: <JAVA400-L@midrange.com> > cc: > Subject: Re: WebSphere FixPack Installation > > > > Once again, thanks! > > The console works fine, even if performances are not "exciting": I could > complete each configuration step without significant troubles. More, I > should say that following strictly the Getting Started guide makes a V4R5 > scratch install quite simple and fast. > > I could execute all the samples and performances were rather good; only > fiew > things to point out: > > - standard configuration process, put some directives in a different order > vs what stated in the guide, with an extra "pass"; > - install JDBC driver fails if there is no /home/QEJB dir, specified at > QEJB > user profile level: maually creating it (empty) solved the problem; > - the <Feedback> sample text states that <the logs has an index at the top > with a hot link to each entry>: my sample supply the ability to insert / > review feedback, but there is no hot links at the top; > - the <YourCo> sample, under <Help Wanted> and "manager level" accessing > user id, should give the ability to insert, update and delete database > records: only the insert option however is available. > > > Regards. > > Claudio Gaiardi > > > > > ----- Original Message ----- > From: "Frances Stewart" <francess@us.ibm.com> > To: <JAVA400-L@midrange.com> > Sent: Tuesday, February 06, 2001 10:45 PM > Subject: Re: WebSphere FixPack Installation > > > > > > Yep. The error 20(s) can safely be ignored. > > > > Frances Stewart > > WebSphere Application Server for iSeries 400 > > IBM Rochester > > > > > > > > > +--- > | 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 +---
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.