OEManagerNotAccessible-exception when testing connection for PAS - Forum - OpenEdge Development - Progress Community

OEManagerNotAccessible-exception when testing connection for PAS

 Forum

OEManagerNotAccessible-exception when testing connection for PAS

This question is answered

Hallo,

I am using the 64-bit version of Open Edge and I have created a new pacific application server. After I have specified all parameters testing connection fails with the following error message:
PAS Connection test failed – Server returned 403.
Forbidden for localhost:8821/.../ with an HTML response (17899).

Testing connection for predefind pas oepas1 works without any problems and accessing the new pas via http.port using ABL comannd connect works without any problems too.

Has anyone an idea why I get this excpetion? Or where to find further information?

Kind regards
Kai Siegele

Verified Answer
  • Hi Kai,

    I think differently, but everyone chooses what he was comfortable ;-)

    I use the OEManagement, so do not know if there is in the OEExplorer, but you can try the following:

    1. Go to instance page:

    2. Stop instance

    3. Click on Extras icon in Command and Control section

    4. On the Extras page choose what you need.

    "Install Tomcat manager web application" - equivalent to manager.war

    "Install Pacific Application Server OpenEdge manager web application" -  - equivalent to oemanager.war

    5. Start instance.

    I hope this helps

All Replies

  • Might be that the optional remote management web applications did not get added to your new PAS server instance?  Check in the webapps directory to see if if manager and oemanager directories exist.

    When you create a new PAS server instance only the minimum required web application (ROOT) is added, meaning that the remote management Tomcat Manager and OpenEdge Manager web applications do not get deployed.   I use the -f command line option to add the optional remote management applications when I want them.

    pasman create -f ...

    Mike J.

  • Hallo Mike,

    thanks for your answer.

    You are right: The war-files have not been copied in the wabapps directory so far.

    Now I want to correct the error using Open Edge Explorer. For this purpose I have tried following steps:

    I have selected my new Pacific Application Server.

    On the page I have selected the same Pacific Application Server under ABL Applications.

    I have changed the configuration: On tab Advanced I have set pc.as.autodeploy to true.

    Unfortunately after stopping and restarting the pas the error is still there.

    Do you have another idea?

    Kind regards

    Kai Siegele

    By the way: Is there any documentation showing what pasman parameter is related to which edit field in Open Edge Explorer?

  • For deploy manager and oemanager apps if you not using -f option when create instance you need to deploy it manually:

    pasoeinstance_dir/bin/tcman.sh deploy $DLC/servers/pasoe/extras/manager.war

    pasoeinstance_dir/bin/tcman.sh deploy $DLC/servers/pasoe/extras/oemanager.war

    then restart insttance.

  • Hallo Andriy,

    thanks for your answer. After invoking proenv as administrator and using –u parameter for deploying oemanager testing connection is successful.

    But using proenv with pasman and tcman and myriad of parameters is very cumbersome and error prone, isn’t it?

    So the best way to manage all my pacific application servers and it’s attributes should be to use the Open Edge Explorer, right? Has anyone another idea how to create a pas equivalent of invoking pasman with –f as parameter?

    Kind regards

    Kai Siegele

  • Hi Kai,

    I think differently, but everyone chooses what he was comfortable ;-)

    I use the OEManagement, so do not know if there is in the OEExplorer, but you can try the following:

    1. Go to instance page:

    2. Stop instance

    3. Click on Extras icon in Command and Control section

    4. On the Extras page choose what you need.

    "Install Tomcat manager web application" - equivalent to manager.war

    "Install Pacific Application Server OpenEdge manager web application" -  - equivalent to oemanager.war

    5. Start instance.

    I hope this helps

  • and one more thing...

    I am using OpenEdge 11.6.3.

  • Hi Kai,

    You have different options to create and maintain your instances. Obviously OEE/OEM is a easier approach as you can manage all your PASOE Instances from one browser console.

    If you want do everyhting online then "pasman/tcman" are best approaches. You can choose to do it from "proenv" or run a shell script that runs pasman/tcman from $DLC/bin.

    Regards,

    Irfan

  • Thank you for your answer. That is exactly what I am looking for.

    Kind regards Kai