Link to home
Start Free TrialLog in
Avatar of sgdought
sgdought

asked on

Cannot connect to Novell's iManager

I cannot connect to Novell'siManager.  I can connect to iMonitor at https://<my.server.name>:8009
I've tried http://<my.server.name>:2200 like some places on the net suggest, also
According to this:
www.novell.com/documentation/lg/nw65/ admin_ovw/data/am4s09s.html
I should be able to do this:
... To start iManager in regular mode, open a Web browser and enter either the IP address
or DNS name of the server, followed by /nps/iManager.html.  This does not work either.

Acording to this link:
www.novell.com/documentation/lg/ nw65/uddi/data/aj4j2tu.html
I should be able to use this:
http://xxx.xxx.xxx.xxx:port/nps/iManager.htmlFor Tomcat Standalone: http://hostname:8080/nps/iManager.html 
For Apache/Tomcat: http://hostname/nps/iManager.html 
For Apache/Tomcat with SSL: https://hostname/nps/iManager.html 
On NetWare 6.5 for Apache/Tomcat with SSL: https://hostname/nps/iManager.html 
On NetWare 6.5 for Apache/Tomcat without SSL: http://hostname/nps/iManager.html 

where hostname is the server name or IP address of the server where the UDDI service is running.


None of these work.   Which file do I examine, or how else do I find which port iManager is listening to?  TCPCON/protocol information/tcp/tcp connections lists the ports, but not what is listening on them.  

NDSIMON.nlm is indeed running, and I can connect to iMonitor with https://<ipaddress>:8009 just to recap.

More info:  I've upgraded to edir 8.71 on the server with the Master Replica, I've install iManager 2.01 and installed the Novell JVM 1.4.1 which was required by Tomcat.

Found some stuff here (finally after 12 hours of searching).  I'll keep you all up to date.
http://support.novell.com/cgi-bin/search/searchtid.cgi?/10078877.htm


Avatar of ShineOn
ShineOn
Flag of United States of America image

Firstly, I would recommend that you ask in the CS TA to have this question moved to the NetWare subtopic area.  There are ppl there that are true Novell Experts that don't always show up in the Networking TA.

As to your problem.  Do you have a link to iManager from iMonitor?  Does it also give you an error?
Also, have you tried reinstalling iManager?

http://support.novell.com/cgi-bin/search/searchtid.cgi?/10065902.htm

The TID talks about iManager 1.2 and 1.51 and not 2.01, but it may still apply.
Avatar of sgdought
sgdought

ASKER

I did not see a Netware area.  Anyway, at this point I can get to to first iManager screen. I used an apache\conf\adminserv.conf from the UMich to see what ports I need to fix.  It was listening on 52443 instead of ssl 443.  Also redirects need to be pointed to port 2200.    Now I get prompted for a password, but it does not accept it.  I can use the login function to login to iMonitor, but the iManager login just prompts me 3 times, then goes to a page that says Authentication required.
That's where I stand at the moment.  
This question is posted in the Networking topic area.  Among the subtopics in the networking topic area is Netware.  That's where all the NetWare wizards in EE do their wizardry.

When you put your login ID in, are you using the full context?  i.e. .admin.myorg?  or .me.myou.myorg?
Ok. I went to https://<IP Address>:2200/eMFrame/Simple.html and go a login screen complete with context.  I could login from this screen.  So I tried logging in from https://<IP Address>:2200 and got the windows authentication screen  I used just admin NOT admin.FullContext  and it worked.  Seems that the apache config files are ALREADY point to the correct context for admin, so I didnt needed to use anything but the name without the context.  Thanks anyway folks.
I will say iManager install and troubleshooting SUCKS as their is no documentation.
There is documentation.  Don't get too frustrated too quickly. The Novell support knowledgebase is superior to any other software provider's knowledgebase I have used, including the mess that Microsoft has for a knowledgebase.  They have more online, web-accessible documentation available than any other software provider I have encountered in my 20-plus years in IT.
When I tried logging in from https://<IP Address>:2200 and got the windows authentication screen, the screen came up Netware Web Manager, with
NetWare® Enterprise Web Servers  
WHITE-SRV1


Novell® eDirectory™  
WHITE-SRV1


NetWare® Remote Manager  
WHITE-SRV1


eDirectory™ iManager    


On the left hand side.  You will notice that my test server White-srv1 is not listed under iManager

When I go to the URL https://<IP Address>:2200/eMFrame/Simple.html I get the following screen:
IManage
Version 1.0

   You are currently logged in as user admin.WHITE.CRIME.TOKYO.ACME
   in the Novell Directory Services tree acme-tree

Now I know I installed version 2.01 and that is what shows up in nwconfig\products\currently installed products.  So I wonder why iManage does not show up in Web Manager?  

Obviously this is a complex product that uses Apache and Tomcat4  which I will have to learn more about.

   Please select a task on the left.
ASKER CERTIFIED SOLUTION
Avatar of ShineOn
ShineOn
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I noticed that you were trying "simple.html" and getting a message regarding iManage 1.0.  

Have you tried accessing it directly using "imanager.html" instead of "simple.html" ???
have you tried updating iManager to it's latest version?  I'm running iManager 1.21 myself - all is well here...

100 points to the man, ShineON.  There was indeed a file named iManage.html, NOT imanager.   I just copied it over to iManager.html and the URLs worked.  It still does not show up in Web Manager, but I can now get to it.  I looked for hours at the Novell website and managed to miss the TID that mentioned the name change.

Thank You.
Check your redirect and include statements in ADMINSERV.CONF also - it may be missing the redirects for iManager, which would cause the link not to show in Web Manager.
Did you shut down Java prior to upgrading iManager?  It's a must.