Re: Web Admin Tool on 6.1 at port 2001 -- WEB400

Henrik,

Thank you .... this looks quite promising. I was under the impression
that a cume PTF was really cumulative, but it looks like some may be
missing .... and there is another 5761JV1 component that was not discussed
in the preparatory steps.

Rich

--------------------------------------------------------------------------

On 4/22/2014 11:43 AM, Henrik R�wrote:

It is ADMIN2

[1]http://www-01.ibm.com/support/docview.wss?uid=nas8N1018538

On Tue, Apr 22, 2014 at 4:27 PM, Rich Loeber [2]<rich@xxxxxxxxx> wrote:

All of the parts of the admin server appear to be starting OK. I see
the
following:

ADMIN QLWISVR BCH .0 PGM-QLWISVR EVTW
ADMIN QLWISVR BCI .0 JVM-com.ibm.lw THDW
ADMIN QTMHHTTP BCH .0 PGM-QZHBMAIN SIGW
ADMIN QTMHHTTP BCI .0 PGM-QZSRLOG SIGW
ADMIN QTMHHTTP BCI .0 PGM-QZSRHTTP SIGW
ADMIN3 QLWISVR BCI .0 JVM-com.ibm.lw THDW
ADMIN4 QWEBADMIN BCI .0 JVM-com.ibm.lw THDW

and ...

QP0ZSPWP QLWISVR BCI .0 PGM-QZSHSH TIMW
QP0ZSPWP QLWISVR BCI .0 PGM-csh DEQW
QZSHSH QLWISVR BCI .0 PGM-QZSHSH EVTW

These last three start when the admin instance starts, so I'm assuming
they are related. All of the required Java parts are installed in the
OS. When I have problems of this sort with my own server instances, I
look at the logs for a clue, but I can't find the server instance logs
for
*ADMIN and the joblogs do not show any information.

Rich

--------------------------------------------------------------------------

On 4/21/2014 4:14 PM, Jim Oberholtzer wrote:

Re-verify that ADMIN4 has started, and check to be sure all of the new to
V6R1 Java bits are loaded. I almost always find the extra Java parts were
not added to the system when I see this.

--
Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects

-----Original Message-----
From: [[3]1]web400-bounces@xxxxxxxxxxxx [[2]mailto:
[4]web400-bounces@xxxxxxxxxxxx] On
Behalf Of Rich Loeber
Sent: Monday, April 21, 2014 2:56 PM
To: Web Enabling the AS400 / iSeries
Subject: [WEB400] Web Admin Tool on 6.1 at port 2001

I just upgraded to 6.1 from V5R4. The HTTP *ADMIN tool starts find
from
the STRTCPSVR command. When I try to use the url:2001 to access the
main
tool, it fails telling me there is an Internal Server error when it
tries
to resolve to url:2001/ibm/console.

When I go directly to the DCM tool, that comes up fine. Same for the
HTTP
server instance tool.

I don't see any messages in QSYSOPR and I'm not seeing any AF records
in
the security journal.

For now, I can work around it, but I'm just wondering what I might be
missing. All of the required OS components are installed and the
latest
cume as installed this morning.

Rich Loeber - @richloeber
Kisco Information Systems
[1][3][5]http://www.kisco.com

References

Visible links
1. [4][6]http://www.kisco.com/
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list To post a message email: [[7]5]WEB400@xxxxxxxxxxxx To subscribe,
unsubscribe,
or change list options,
visit: [6][8]http://lists.midrange.com/mailman/listinfo/web400
or email: [[9]7]WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at
[8][10]http://archive.midrange.com/web400.

References

Visible links
1. [11]mailto:web400-bounces@xxxxxxxxxxxx
2. [12]mailto:web400-bounces@xxxxxxxxxxxx
3. [13]http://www.kisco.com/
4. [14]http://www.kisco.com/
5. [15]mailto:WEB400@xxxxxxxxxxxx
6. [16]http://lists.midrange.com/mailman/listinfo/web400
7. [17]mailto:WEB400-request@xxxxxxxxxxxx
8. [18]http://archive.midrange.com/web400
--
This is the Web Enabling the IBM i (AS/400 and iSeries) (WEB400) mailing
list
To post a message email: [19]WEB400@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: [20]http://lists.midrange.com/mailman/listinfo/web400
or email: [21]WEB400-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at [22]http://archive.midrange.com/web400.

References

Visible links
1. http://www-01.ibm.com/support/docview.wss?uid=nas8N1018538
2. mailto:rich@xxxxxxxxx
3. mailto:1]web400-bounces@xxxxxxxxxxxx
4. mailto:web400-bounces@xxxxxxxxxxxx
5. http://www.kisco.com/
6. http://www.kisco.com/
7. mailto:5]WEB400@xxxxxxxxxxxx
8. http://lists.midrange.com/mailman/listinfo/web400
9. mailto:7]WEB400-request@xxxxxxxxxxxx
10. http://archive.midrange.com/web400
11. mailto:web400-bounces@xxxxxxxxxxxx
12. mailto:web400-bounces@xxxxxxxxxxxx
13. http://www.kisco.com/
14. http://www.kisco.com/
15. mailto:WEB400@xxxxxxxxxxxx
16. http://lists.midrange.com/mailman/listinfo/web400
17. mailto:WEB400-request@xxxxxxxxxxxx
18. http://archive.midrange.com/web400
19. mailto:WEB400@xxxxxxxxxxxx
20. http://lists.midrange.com/mailman/listinfo/web400
21. mailto:WEB400-request@xxxxxxxxxxxx
22. http://archive.midrange.com/web400