Link in NWA won't work

[Former Member]

After installing a non-central AAE is would like to perform the postaction. However if i want to install the license key or go to the configuration wizard via nwa -> configuration management -> infrastructure is get stuck. I can logon to the NWA with my administrator user. But when logged on i can;t do anything anymore. All available options are clickable but nothing will happen after clicking them.

So neither Availability and Performance Management, Operation Management, Configuration Management, Problem Management and SOA Management work. But also items like Connection manager, java system reports, locks or log viewer i cant go to.

And, by the way, I can use the direct links, like nwa/cfg-wizard but then in that screen none of the clickable items work.

I don't get an error message nor can i find log file entries.

Another weird thing is that in http://hostname:port/ clicking on user management results in a blank screen.

I use IE7. I tried to approach the nwa via IE on another system, same result however.

please help

regards

Peter

[p330068]

Hi Peter,

Please use the FQDN (Fully Qualify Domain Name ) to access the NWA. Also update the host file with server IP and Host name then check the portal url http://FQDN:Port/nwa

Hope it will helps

Best Regards,

Arun Jaiswal

[Former Member]

Hello Peter,

Looks like Java is not completely up.

Kindly go through JCMON and check whether all the java components are up.

http://<hostname>:5<instance Number>00/ should open the page if java is Up.

Kindly restart Java and check if this URL comes up. Later on you can logon to NWA.

Regards

Vivek

[Former Member]

well, maybe i was not clearly enough, java is up and i can connect to NWA, however once im connected clicking the option result in nothing. Nothing happens. As said, using the direct links do get me to the configuration wizard instance but then also in that screen none of the links are working...

[Former Member]

using the FQDN didnt matter. The host file already contains the ipadres/host name... so unfortunately it didnt help

[Former Member]

so ive found out that most likely this problem is caused by locale ip addresses getting proxied. So i guess the proxy server also kind of firewall and blocking certain things. I found out by using localhost instead the ip address or host name.