The oemanager web application is not accessible: Server returned 403 Forbidden - Forum - OpenEdge RDBMS - Progress Community

The oemanager web application is not accessible: Server returned 403 Forbidden

 Forum

The oemanager web application is not accessible: Server returned 403 Forbidden

This question is not answered

Hi,

Win64 bit
OpenEdge 11.6.2 64 bit

After adding PAS4OE Prod to OpenEdge installation with RDBMS license only, in the OEM after starting the PAS instance the client receives the following message:
"The oemanager web application is not accessible: Server returned 403 Forbidden for localhost:8202/.../ with an HTML response (17899)":

What does it mean? Will this affect the work of an instance?

How to fix this?

Regards,
Valeriy

All Replies
  • Should it be localhost:8202/manager instead of oemanager?  

  • This message says that, OEM fails to contact oemanager webapp of that PAS instance. OEM actually uses this webapp to get the metrics/configurations and manages the deployments of all transports and shows it on UI.
     
    Make sure you install oemanager (from Instance Home page -> Extras page) to get additional benefit from OEM UI.
     
    Thanks,
    Satya
     
  • I saw something very similar last week in 11.6.2. We had to go into OE Explorer and manually set both the tomcat and OEE passwords in the PASOE config.

    Paul Koufalis
    White Star Software

    pk@wss.com
    @oeDBA (https://twitter.com/oeDBA)

    ProTop: The #1 Free OpenEdge DB Monitoring Tool
    http://protop.wss.com
  • Hi Paul,

    Paul Koufalis

    I saw something very similar last week in 11.6.2. We had to go into OE Explorer and manually set both the tomcat and OEE passwords in the PASOE config.

    I think at that time you receiving a message "401 Unauthorized".
    In my case it's something different - "403 Forbidden".
  • Hi Satya,

    Satya Prasad
    Make sure you install oemanager (from Instance Home page -> Extras page) to get additional benefit from OEM UI.
     

    The client install oemanager when created an instance in the OEM by set flags "Install Pacific Application Server OpenEdge manager web application" and "Install Tomcat manager web application".

    But, I'll check it again in their place...