Exporting WAR File to other Production servers / Development environments throws 500 Error, Java Null Pointer - Forum - OpenEdge Development - Progress Community

Exporting WAR File to other Production servers / Development environments throws 500 Error, Java Null Pointer

 Forum

Exporting WAR File to other Production servers / Development environments throws 500 Error, Java Null Pointer

This question is answered

Hi Guys,

We normally like to create multiple ABL Services and WAR files for our applications. This is because some of them have a different level of security (anonymus, oerealm, basic, etc..). For that purpose, we export a WAR file for PASOE to all of our development group to have the same links with the same security level.

Right now, if we export a WAR file from Progress Developer Studio, and deploy it on a PAS instance, is throwing the error the following error:

Does anybody knows how to solve this?

Regards

Verified Answer
  • Hi Eduardo,
     
    I’m able to publish to Production PAS instance with the WAR file exported from PDSOE’s ABL Web App project. Also able to access the services after deploying. Please let us know what are the steps you have followed to publish the WAR file to Production server.
     
    Here are the steps I have followed:

    1.       Create an ABL Web App project

    2.       Develop some Data Object Services (You can develop any ABL service)

    3.       Export the services as WAR file using Export > Export as ABL Web Application option.

    a.       Provide a proper destination for WAR file

    b.       Choose “Choose ABL services for Pacific Application Server” radio button (by default selected)

    c.       Select the services under ABL Services section and click Finish.

    4.       Copy the WAR file to Production server machine

    5.       Also copy ABL Sources files from PDS OE’s project to Production servers openedge directory. (C:\OpenEdge\WRK\oepas1\openedge)

    6.       Go to Production machine and then launch Proenv

    7.       Deploy the WebApp (oepas1\bin\tcman.bat deploy <WAR-File-Path>)

    8.       Enable Web Application after deployment (by default Web Application is disabled in Production server after deployment)

    a.       oepas1\bin\tcman.bat enable <Web-App-Name>

    9.       Start the server (oepas1\bin\tcman.bat start)

    10.   Launch the WebApp in browser and verify the results.

     
    Hope this helps,
    Sanjeev.
     
All Replies
  • Hi Eduardo,
     
    I’m able to publish to Production PAS instance with the WAR file exported from PDSOE’s ABL Web App project. Also able to access the services after deploying. Please let us know what are the steps you have followed to publish the WAR file to Production server.
     
    Here are the steps I have followed:

    1.       Create an ABL Web App project

    2.       Develop some Data Object Services (You can develop any ABL service)

    3.       Export the services as WAR file using Export > Export as ABL Web Application option.

    a.       Provide a proper destination for WAR file

    b.       Choose “Choose ABL services for Pacific Application Server” radio button (by default selected)

    c.       Select the services under ABL Services section and click Finish.

    4.       Copy the WAR file to Production server machine

    5.       Also copy ABL Sources files from PDS OE’s project to Production servers openedge directory. (C:\OpenEdge\WRK\oepas1\openedge)

    6.       Go to Production machine and then launch Proenv

    7.       Deploy the WebApp (oepas1\bin\tcman.bat deploy <WAR-File-Path>)

    8.       Enable Web Application after deployment (by default Web Application is disabled in Production server after deployment)

    a.       oepas1\bin\tcman.bat enable <Web-App-Name>

    9.       Start the server (oepas1\bin\tcman.bat start)

    10.   Launch the WebApp in browser and verify the results.

     
    Hope this helps,
    Sanjeev.
     
  • Anything from the log files in your instance

    Regards,

    Irfan

  • The important part of step 2 is that for PASOE you MUST use “ABL Services” for your service interface definitions. The “Data Object” and “REST” services are intended for use with Classic AppServer and the REST Adapter.