× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. JAVA400-L
  3. March 2002

Re: iSeries Access for Web

Is there anything in this file: /QIBM/UserData/Access/Web/logs/iwacfg.log

Frances Stewart
WebSphere Application Server for iSeries 400
IBM Rochester




                      P.Goovaerts@Clipp
                      er.Be                    To:       java400-l@midrange.com
                      Sent by:                 cc:
                      java400-l-admin@m        Subject:  iSeries Access for Web
                      idrange.com


                      03/13/02 08:55 AM
                      Please respond to
                      java400-l





This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
We have installed iSeries Access for Web.

1) Then we have executed configuration as follows:
QIWA/CFGACCWEB PORT(2032) WASINST(*DEFAULT)

We got no errors but... there is no new entry in our Administrative
Console

2) Then we removed the configuration with RMVACCWEB and re-executed
configuration as follows:
QIWA/CFGACCWEB PORT(2032) WASINST(DEFAULT)
('default' -lower case- is our was-instance.  At least, this is the folder
following 'QIBM/UserData/WebASAdv/...)

Again no errors but still no new entry.

3) Finally we tried same with the node-name i.s.o. 'default', but then
iSeries Access for Web refuses to configure...


any help welcome...

Here's an extract of the log:
********************************************************
Wed Mar 13 14:01:50 GMT+00:00 2002


Processing iSeries Access for Web command for WebSphere 3.5.


Running CFGACCWEB command.


Verifying current user has required authority.


    Current signed on user: QSECOFR


    The currently signed on user does have the required authority.


    Creating the data queue.


    Data Queue already exists.


    Clearing the data queue.


Verifying IBM WebSphere Application Server is installed on the server.


    PID: 5733WA3  VER: V3R5M0  OPT: 0000


    PID: 5733AS3  VER: V3R5M0  OPT: 0000


    WebSphere Standard 128-bit 3.5.0 found to be installed.


The WebSphere QEJBSBS subsystem is active.


    The WebSphere QEJBSBS subsystem is active.


Determining if WebSphere security has been enabled.


    Verifying WebSphere administrative instance exists on the server.


        Checking to see if the following path exists:
/QIBM/UserData/WebASAdv/DEFAULT


    WebSphere security has not been enabled.


    WebSphere security verification has completed.


Setting required object authorities.


    Updating authority to the library.


    Updating authority to the data queue.


    Updating the authority for the following directories...


        /QIBM/ProdData/Access/Web


        /QIBM/ProdData/Access/Web/classes


        /QIBM/ProdData/Access/Web/config


        /QIBM/ProdData/Access/Web/html


        /QIBM/ProdData/Access/Web/html/images


        /QIBM/ProdData/Access/Web/install


        /QIBM/ProdData/Access/Web/lib


        /QIBM/ProdData/Access/Web/MRI2924


        Checking to see if the following path exists:
/QIBM/ProdData/Access/Web/MRI2924


        /QIBM/ProdData/Access/Web/MRI2938


        Checking to see if the following path exists:
/QIBM/ProdData/Access/Web/MRI2938


        The path does not exist: /QIBM/ProdData/Access/Web/MRI2938


        /QIBM/ProdData/Access/Web/MRI2950


        Checking to see if the following path exists:
/QIBM/ProdData/Access/Web/MRI2950


        The path does not exist: /QIBM/ProdData/Access/Web/MRI2950


        /QIBM/ProdData/Access/Web/MRI2984


        Checking to see if the following path exists:
/QIBM/ProdData/Access/Web/MRI2984


        The path does not exist: /QIBM/ProdData/Access/Web/MRI2984


    Updating the ownership of the following objects...


        /QIBM/UserData/Access


        /QIBM/UserData/Access/Web


        /QIBM/UserData/Access/Web/logs


        /QIBM/UserData/Access/Web/logs/install.log


        /QIBM/UserData/Access/Web/temp


        /QIBM/UserData/Access/Web/temp/users


        /QIBM/UserData/Access/Web/users


    Updating the authority for the following directories...


        /QIBM/UserData/Access/Web


        /QIBM/UserData/Access/Web/config


        /QIBM/UserData/Access/Web/logs


        /QIBM/UserData/Access/Web/temp


        /QIBM/UserData/Access/Web/temp/users


        /QIBM/UserData/Access/Web/users


Preparing to start the iSeries Access for Web configuration of WebSphere.


    Check to see if iSeries Access has already been configured.


        Checking to see if the following path exists:
/QIBM/UserData/Access/Web/config/webaccess.properties


        Reading values from iSeries Access for Web properties file.


        iSeries Access for Web has not be previously configured.


    Determining server node name which is input to the WebSphere
configuration.


Determining the nameServiceHost value.


    The default value is being used for the nameServiceHost:
CONTINENTALLINES


Determining the nameServicePort value.


    Reading value from WebSphere properties file:
/QIBM/UserData/WebASAdv/DEFAULT/properties/admin.properties


    The property file value is being used for the nameServicePort: 900


The iSeries Access for Web configuration of WebSphere has started.


    WebSphere is being invoked with the following command...


        QSH CMD('/QIBM/ProdData/WebASAdv/bin/XMLConfig -adminNodeName
CONTINENTALLINES.SEAGHA.COM -import
/QIBM/ProdData/Access/Web/install/iwacfg.xml -instance DEFAULT
-nameServiceHost CONTINENTALLINES -nameServicePort 900 -substitute
"NODE_NAME=CONTINENTALLINES.SEAGHA.COM;PORT_NUMBER=2032" >
/QIBM/UserData/Access/Web/logs/iwacfg.log')


    The iSeries Access for Web configuration of WebSphere has completed.


    The configuration information is being saved to the iSeries Access for
Web properties file.


        Checking to see if the following path exists:
/QIBM/UserData/Access/Web/config/webaccess.properties


        was35.port = 2032


        was35.instance = DEFAULT


        was35.servicehost = CONTINENTALLINES


        was35.serviceport = 900


        webappsvr.type = *WAS35


        was35.version.type = StandardEdition


        was35.nodename = CONTINENTALLINES.SEAGHA.COM


    The save of the configuration information has completed.


Processing for iSeries Access for Web for WebSphere 3.5 has completed.

********************************************************
_______________________________________________
This is the Java Programming on and around the iSeries / AS400 (JAVA400-L)
mailing list
To post a message email: JAVA400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/java400-l
or email: JAVA400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/java400-l.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.