------------------------------
Robert Berendt IBMChampion
------------------------------

Dear Robert

If you have HTTP Group PTF level 2 or higher in IBM i 7.5, ADMIN2 will provide only LDAP service at port 389 and LDAPS at port 636. 

Details on ADMIN2 are in these 2 Technotes:

https://www.ibm.com/support/pages/remove-heritage-ibm-navigator-i-admin2

https://www.ibm.com/support/pages/heritage-navigator-enable-and-disable-instructions

------------------------------
Satid S

Original Message:
Sent: Fri March 22, 2024 08:55 AM
From: Robert Berendt
Subject: What is the purpose of the ADMIN2 job on an IBM i 7.5 system with current PTFs?

------------------------------
Robert Berendt IBMChampion
------------------------------

Dear Robert

If you have HTTP Group PTF level 2 or higher in IBM i 7.5, ADMIN2 will provide only LDAP service at port 389 and LDAPS at port 636. 

Details on ADMIN2 are in these 2 Technotes:

https://www.ibm.com/support/pages/remove-heritage-ibm-navigator-i-admin2

https://www.ibm.com/support/pages/heritage-navigator-enable-and-disable-instructions

------------------------------
Satid S

Original Message:
Sent: Fri March 22, 2024 08:55 AM
From: Robert Berendt
Subject: What is the purpose of the ADMIN2 job on an IBM i 7.5 system with current PTFs?

------------------------------
Robert Berendt IBMChampion
------------------------------

Where is that image you provided gleaned from?

Dear Robert

If you have HTTP Group PTF level 2 or higher in IBM i 7.5, ADMIN2 will provide only LDAP service at port 389 and LDAPS at port 636. 

Details on ADMIN2 are in these 2 Technotes:

https://www.ibm.com/support/pages/remove-heritage-ibm-navigator-i-admin2

https://www.ibm.com/support/pages/heritage-navigator-enable-and-disable-instructions

------------------------------
Satid S

Original Message:
Sent: Fri March 22, 2024 08:55 AM
From: Robert Berendt
Subject: What is the purpose of the ADMIN2 job on an IBM i 7.5 system with current PTFs?

------------------------------
Robert Berendt IBMChampion
------------------------------

Hello Robert,

Satid's image looks like the WRKSRVTBLE screen.

Where is that image you provided gleaned from?

Dear Robert

If you have HTTP Group PTF level 2 or higher in IBM i 7.5, ADMIN2 will provide only LDAP service at port 389 and LDAPS at port 636. 

Details on ADMIN2 are in these 2 Technotes:

https://www.ibm.com/support/pages/remove-heritage-ibm-navigator-i-admin2

https://www.ibm.com/support/pages/heritage-navigator-enable-and-disable-instructions

------------------------------
Satid S

Original Message:
Sent: Fri March 22, 2024 08:55 AM
From: Robert Berendt
Subject: What is the purpose of the ADMIN2 job on an IBM i 7.5 system with current PTFs?

------------------------------
Robert Berendt IBMChampion
------------------------------

@Michael Swenson I believe you're right.  However that command doesn't seem to point to what jobs or anything are used to support those ports.  Not even sure what the use of that command is.  Other than adding a description to a number.  Is that where they get the description on NETSTAT *CNN?  So if I'm running a popular IBM i package which uses port 9000 I could ADDSRVTBLE to describe that port?

Hello Robert,

Satid's image looks like the WRKSRVTBLE screen.

Where is that image you provided gleaned from?

Dear Robert

If you have HTTP Group PTF level 2 or higher in IBM i 7.5, ADMIN2 will provide only LDAP service at port 389 and LDAPS at port 636. 

Details on ADMIN2 are in these 2 Technotes:

https://www.ibm.com/support/pages/remove-heritage-ibm-navigator-i-admin2

https://www.ibm.com/support/pages/heritage-navigator-enable-and-disable-instructions

------------------------------
Satid S

Original Message:
Sent: Fri March 22, 2024 08:55 AM
From: Robert Berendt
Subject: What is the purpose of the ADMIN2 job on an IBM i 7.5 system with current PTFs?

------------------------------
Robert Berendt IBMChampion
------------------------------

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

I have opened a case dealing with Navigator using the wrong link.  TS015775487

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

I can get the following to work from the browser URL line (one, after beating hsts into submission):

http://gdi.dekko-1:2004/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com
https://gdi.dekko.com:2005/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

but the link in Navigator tries to go to the wrong port(2002):

http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

I have opened a case dealing with Navigator using the wrong link.  TS015775487

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

You can try "Restore Shipped Bookmarks" and should get port 2001:

Or you can edit the bookmarks to your liking:

I can get the following to work from the browser URL line (one, after beating hsts into submission):

http://gdi.dekko-1:2004/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com
https://gdi.dekko.com:2005/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

but the link in Navigator tries to go to the wrong port(2002):

http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

I have opened a case dealing with Navigator using the wrong link.  TS015775487

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

Fascinating.  I have a total of 5 bookmarks and none of them are that.  Across 11 LPARs of IBM i, all at 7.5, cume 23306, HTTP group 13.

Some of these have been around since OS/400, some started out at 7.5.

How did you get that bookmark?

You can try "Restore Shipped Bookmarks" and should get port 2001:

Or you can edit the bookmarks to your liking:

I can get the following to work from the browser URL line (one, after beating hsts into submission):

http://gdi.dekko-1:2004/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com
https://gdi.dekko.com:2005/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

but the link in Navigator tries to go to the wrong port(2002):

http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

I have opened a case dealing with Navigator using the wrong link.  TS015775487

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

Fascinating.  I have a total of 5 bookmarks and none of them are that.  Across 11 LPARs of IBM i, all at 7.5, cume 23306, HTTP group 13.

Some of these have been around since OS/400, some started out at 7.5.

How did you get that bookmark?

You can try "Restore Shipped Bookmarks" and should get port 2001:

Or you can edit the bookmarks to your liking:

I can get the following to work from the browser URL line (one, after beating hsts into submission):

http://gdi.dekko-1:2004/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com
https://gdi.dekko.com:2005/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

but the link in Navigator tries to go to the wrong port(2002):

http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

I have opened a case dealing with Navigator using the wrong link.  TS015775487

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

Fascinating.  I have a total of 5 bookmarks and none of them are that.  Across 11 LPARs of IBM i, all at 7.5, cume 23306, HTTP group 13.

Some of these have been around since OS/400, some started out at 7.5.

How did you get that bookmark?

You can try "Restore Shipped Bookmarks" and should get port 2001:

Or you can edit the bookmarks to your liking:

I can get the following to work from the browser URL line (one, after beating hsts into submission):

http://gdi.dekko-1:2004/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com
https://gdi.dekko.com:2005/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

but the link in Navigator tries to go to the wrong port(2002):

http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

I have opened a case dealing with Navigator using the wrong link.  TS015775487

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

@Lora R Powell,

I snipped my current bookmarks and pasted that into a Word document.

I performed Restore Shipped Bookmarks, snipped that and added to the document.

I modified "IBM Web Administration for i" and "IBM Digital Certificate Manager for i" to use the right port, and to use https.  Snipped that and added it to the document.

I ran ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) , verified it was down with WRKSBSJOB SBS(QHTTPSVR) and started it back up.

The new bookmark works.  However, that did nothing to fix that button in my previous post.

I do appreciate this information but I'd like to get that button fixed too.

Fascinating.  I have a total of 5 bookmarks and none of them are that.  Across 11 LPARs of IBM i, all at 7.5, cume 23306, HTTP group 13.

Some of these have been around since OS/400, some started out at 7.5.

How did you get that bookmark?

You can try "Restore Shipped Bookmarks" and should get port 2001:

Or you can edit the bookmarks to your liking:

I can get the following to work from the browser URL line (one, after beating hsts into submission):

http://gdi.dekko-1:2004/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com
https://gdi.dekko.com:2005/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

but the link in Navigator tries to go to the wrong port(2002):

http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

I have opened a case dealing with Navigator using the wrong link.  TS015775487

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

@Lora R Powell,

I snipped my current bookmarks and pasted that into a Word document.

I performed Restore Shipped Bookmarks, snipped that and added to the document.

I modified "IBM Web Administration for i" and "IBM Digital Certificate Manager for i" to use the right port, and to use https.  Snipped that and added it to the document.

I ran ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) , verified it was down with WRKSBSJOB SBS(QHTTPSVR) and started it back up.

The new bookmark works.  However, that did nothing to fix that button in my previous post.

I do appreciate this information but I'd like to get that button fixed too.

Fascinating.  I have a total of 5 bookmarks and none of them are that.  Across 11 LPARs of IBM i, all at 7.5, cume 23306, HTTP group 13.

Some of these have been around since OS/400, some started out at 7.5.

How did you get that bookmark?

You can try "Restore Shipped Bookmarks" and should get port 2001:

Or you can edit the bookmarks to your liking:

I can get the following to work from the browser URL line (one, after beating hsts into submission):

http://gdi.dekko-1:2004/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com
https://gdi.dekko.com:2005/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

but the link in Navigator tries to go to the wrong port(2002):

http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

I have opened a case dealing with Navigator using the wrong link.  TS015775487

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

Thank you!  I have a case opened for DAYS and they haven't yet figured that out.  TS015775487

@Lora R Powell,

I snipped my current bookmarks and pasted that into a Word document.

I performed Restore Shipped Bookmarks, snipped that and added to the document.

I modified "IBM Web Administration for i" and "IBM Digital Certificate Manager for i" to use the right port, and to use https.  Snipped that and added it to the document.

I ran ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) , verified it was down with WRKSBSJOB SBS(QHTTPSVR) and started it back up.

The new bookmark works.  However, that did nothing to fix that button in my previous post.

I do appreciate this information but I'd like to get that button fixed too.

Fascinating.  I have a total of 5 bookmarks and none of them are that.  Across 11 LPARs of IBM i, all at 7.5, cume 23306, HTTP group 13.

Some of these have been around since OS/400, some started out at 7.5.

How did you get that bookmark?

You can try "Restore Shipped Bookmarks" and should get port 2001:

Or you can edit the bookmarks to your liking:

I can get the following to work from the browser URL line (one, after beating hsts into submission):

http://gdi.dekko-1:2004/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com
https://gdi.dekko.com:2005/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

but the link in Navigator tries to go to the wrong port(2002):

http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

I have opened a case dealing with Navigator using the wrong link.  TS015775487

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

Do you know this.
Qustion: When I got this kind of message


Where is the <WAS_Home> located?

And is the user ID the same as in General, Administrator Name and Password?

Thank you!  I have a case opened for DAYS and they haven't yet figured that out.  TS015775487

@Lora R Powell,

I snipped my current bookmarks and pasted that into a Word document.

I performed Restore Shipped Bookmarks, snipped that and added to the document.

I modified "IBM Web Administration for i" and "IBM Digital Certificate Manager for i" to use the right port, and to use https.  Snipped that and added it to the document.

I ran ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) , verified it was down with WRKSBSJOB SBS(QHTTPSVR) and started it back up.

The new bookmark works.  However, that did nothing to fix that button in my previous post.

I do appreciate this information but I'd like to get that button fixed too.

Fascinating.  I have a total of 5 bookmarks and none of them are that.  Across 11 LPARs of IBM i, all at 7.5, cume 23306, HTTP group 13.

Some of these have been around since OS/400, some started out at 7.5.

How did you get that bookmark?

You can try "Restore Shipped Bookmarks" and should get port 2001:

Or you can edit the bookmarks to your liking:

I can get the following to work from the browser URL line (one, after beating hsts into submission):

http://gdi.dekko-1:2004/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com
https://gdi.dekko.com:2005/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

but the link in Navigator tries to go to the wrong port(2002):

http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

I have opened a case dealing with Navigator using the wrong link.  TS015775487

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

I do not know where that directory is located.  There are some ifs search methods to find files.

Yes it is the same as that entered on the General tab.  You have to enter the user as cn=Administrator.  The password you simply enter in the password.  No yadayada=password syntax.

I logged in successfully for the first time just to figure this out for you.

Do you know this.
Qustion: When I got this kind of message


Where is the <WAS_Home> located?

And is the user ID the same as in General, Administrator Name and Password?

Thank you!  I have a case opened for DAYS and they haven't yet figured that out.  TS015775487

@Lora R Powell,

I snipped my current bookmarks and pasted that into a Word document.

I performed Restore Shipped Bookmarks, snipped that and added to the document.

I modified "IBM Web Administration for i" and "IBM Digital Certificate Manager for i" to use the right port, and to use https.  Snipped that and added it to the document.

I ran ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) , verified it was down with WRKSBSJOB SBS(QHTTPSVR) and started it back up.

The new bookmark works.  However, that did nothing to fix that button in my previous post.

I do appreciate this information but I'd like to get that button fixed too.

Fascinating.  I have a total of 5 bookmarks and none of them are that.  Across 11 LPARs of IBM i, all at 7.5, cume 23306, HTTP group 13.

Some of these have been around since OS/400, some started out at 7.5.

How did you get that bookmark?

You can try "Restore Shipped Bookmarks" and should get port 2001:

Or you can edit the bookmarks to your liking:

I can get the following to work from the browser URL line (one, after beating hsts into submission):

http://gdi.dekko-1:2004/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com
https://gdi.dekko.com:2005/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

but the link in Navigator tries to go to the wrong port(2002):

http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

I have opened a case dealing with Navigator using the wrong link.  TS015775487

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

I do not know where that directory is located.  There are some ifs search methods to find files.

Yes it is the same as that entered on the General tab.  You have to enter the user as cn=Administrator.  The password you simply enter in the password.  No yadayada=password syntax.

I logged in successfully for the first time just to figure this out for you.

Do you know this.
Qustion: When I got this kind of message


Where is the <WAS_Home> located?

And is the user ID the same as in General, Administrator Name and Password?

Thank you!  I have a case opened for DAYS and they haven't yet figured that out.  TS015775487

@Lora R Powell,

I snipped my current bookmarks and pasted that into a Word document.

I performed Restore Shipped Bookmarks, snipped that and added to the document.

I modified "IBM Web Administration for i" and "IBM Digital Certificate Manager for i" to use the right port, and to use https.  Snipped that and added it to the document.

I ran ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) , verified it was down with WRKSBSJOB SBS(QHTTPSVR) and started it back up.

The new bookmark works.  However, that did nothing to fix that button in my previous post.

I do appreciate this information but I'd like to get that button fixed too.

Fascinating.  I have a total of 5 bookmarks and none of them are that.  Across 11 LPARs of IBM i, all at 7.5, cume 23306, HTTP group 13.

Some of these have been around since OS/400, some started out at 7.5.

How did you get that bookmark?

You can try "Restore Shipped Bookmarks" and should get port 2001:

Or you can edit the bookmarks to your liking:

I can get the following to work from the browser URL line (one, after beating hsts into submission):

http://gdi.dekko-1:2004/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com
https://gdi.dekko.com:2005/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

but the link in Navigator tries to go to the wrong port(2002):

http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

I have opened a case dealing with Navigator using the wrong link.  TS015775487

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.

@Lora R Powell,

I snipped my current bookmarks and pasted that into a Word document.

I performed Restore Shipped Bookmarks, snipped that and added to the document.

I modified "IBM Web Administration for i" and "IBM Digital Certificate Manager for i" to use the right port, and to use https.  Snipped that and added it to the document.

I ran ENDTCPSVR SERVER(*HTTP) HTTPSVR(*ADMIN) , verified it was down with WRKSBSJOB SBS(QHTTPSVR) and started it back up.

The new bookmark works.  However, that did nothing to fix that button in my previous post.

I do appreciate this information but I'd like to get that button fixed too.

Fascinating.  I have a total of 5 bookmarks and none of them are that.  Across 11 LPARs of IBM i, all at 7.5, cume 23306, HTTP group 13.

Some of these have been around since OS/400, some started out at 7.5.

How did you get that bookmark?

You can try "Restore Shipped Bookmarks" and should get port 2001:

Or you can edit the bookmarks to your liking:

I can get the following to work from the browser URL line (one, after beating hsts into submission):

http://gdi.dekko-1:2004/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com
https://gdi.dekko.com:2005/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

but the link in Navigator tries to go to the wrong port(2002):

http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com

I have opened a case dealing with Navigator using the wrong link.  TS015775487

Tim,

1 - How do we tell Navigator to use https instead of http when we click on "Server Administration" to manage ldap?  You know, like we do with the other stuff under Managing Bookmarks?

2 - How do we tell it to use systemname.mycompany.com instead of whatever the domain is wherever it discovered this dekko-1 url http://gdi.dekko-1:2002/IDSWebApp/IDSjsp/Login.jsp?ldapserver=gdi.dekko.com  Again, something I can sometimes change with Managing Bookmarks.

These two issues resolved from clicking on Server Administration at:

Greetings!  Time to jump in.  

With the Heritage Nav riding off into he sunset, the ADMIN2 server is only for the LDAP directory management interface. Not the LDAP server, that runs in a totally different job.  Here is what that interface looks like.

You can get to it by - http://systemname:2004/IDSWebApp

Within Navigator, you can use Network ->Connections You see all the ports that are active, right click on the entry, and you can then see the actual Job that is running and connected to that port. 

I'm not so sure about that Robert but I may be wrong.
We have configured SSO/Kerberos and that services uses the LDAP service.
Even if ADMIN2 is down it's still possible to use the EIM in LDAP.
I don't think ADMIN2 is used any more after the Heritage Navigator was removed.
But I'm agree with you that the "Server Administration" is not working after shutting down ADMIN2.
I have never been able to log into that site. 
So I don't know what the Server admin does att all although the description tells you what.

I think I'm getting this now.

ADMIN2 does not "serve" or "provide" ldap.  That is done by the QUSRDIR job.

ADMIN2 "manages" ldap.  If you go into Navigator, Servers, TCP/IP Servers, Directory Server (LDAP), Properties, More, and click Server Administration it will abort when the ADMIN2 job is down.