Feedback
Did this article resolve your question/issue?

   

Article

Does PASOE have the "Environment Variables" tab?

« Go Back

Information

 
TitleDoes PASOE have the "Environment Variables" tab?
URL Name000059929
Article Number000173870
EnvironmentProduct: OpenEdge
Version: 11.x,12.x
OS: All Supported Platforms
Other: PASOE
Question/Problem Description
Did the Environment Variables tab disappear under the agent configuration in Pacific AppServer? Is there any substitute?
How can be a environment variable set on PASOE?
How can be a environment variable set on Pacific AppServer, under tomcat?
Does PASOE have the "Environment Variables" tab"?
Does Pacific AppServer have the "Environment Variables" tab?
 
Steps to Reproduce
Clarifying Information
User-added image

In Progress OpenEdge Management on PASOE when navigate to Resources -> OpenEdge PASOE  -> oepas1 -> ABL Applications -> Configuration there is no Environment Variables tab.
Error Message
Defect Number
Enhancement Number
Cause
Resolution

No, PASOE does not have the Environment Variables tab in the Configuration settings. This is expected and Progress has no plans to add an environment block to the properties file at this time. 

There are two ways to set environment variables:

  1. Create a <myenv>_setenv.(bat/sh) script and place it in the <PASOE>\bin directory.  Different files with different prefix could be created to handle logically each environment variables per application.  User controls the application variables in each file, but they are accessible to all applications running on PASOE instance.

 

  1. All environment variables are placed in one file, proset.env (Linux/Unix) or proset.bat (Windows). In this case the proset.bat|env will be placed in the OpenEdge Working directory. All variables will be accessible the same way for all applications on PASOE instance.


 PASOE instance needs to be restarted once these files are created so environment variables are accessible to the web applications.

Example: 

For proset. 

  1. Create a text file named proset.env (Linux/Unix) or proset.bat (Windows). Add the following text:

 

Windows
set WHOIS=IAM

Linux/Unix
WHOIS=IAM;export WHOIS

 

  1. Copy proset.bat|env to the working directory (%WRKDIR% | $WRKDIR)of the OpenEdge installation. 


For _setenv

  1. Create a text file named myenv_setenv.sh (Linux/Unix) or myenv_setenv.bat (Windows). Add the following text:

 

Windows
set WHOIS=IAM

Linux/Unix
WHOIS=IAM;export WHOIS

 

  1. Copy myenv_setenv.bat|sh to the <PASOE-Instance>/bin directory. 
  2. Write an ABL procedure or Class to get the value of the environment variable :
MESSAGE "THIS IS WHOIS: " OS-GETENV("WHOIS").

 

  1. Deploy the r-code to <PASOE-Instance>/openedge directory or to a directory in the PROPATH. 
  2. Make a test call using an ABL client connection code:
DEFINE VARIABLE hAppSrv AS HANDLE NO-UNDO.
DEFINE VARIABLE ret AS LOGICAL NO-UNDO.

CREATE SERVER hAppSrv.
// If using the ROOT webapp the URL would be https://: port>/apsv instead
ret = hAppSrv:CONNECT("-URL http://localhost:<instanceport>/apsv","","").

IF NOT ret THEN 

DO:
DELETE OBJECT hAppSrv NO-ERROR.
RETURN ERROR "Failed to connect to the PASOE instance via HTTPS " + RETURN-VALUE.
END.

ELSE 

DO:
message "Connection successful" view-as alert-box.
RUN <testprocedure>.p ON hAppSrv.
END.
ret = hAppSrv:DISCONNECT().

DELETE OBJECT hAppSrv NO-ERROR.
  1. Check the <instance.agent.log> file located at  {CATALINA_BASE}/logs:
[<any time stamp>] P-003064 T-003070 1 AS-7 -- (Procedure: 'yourtestprocedure.p' Line:1) THIS IS WHOIS:  IAM
[<any time stamp>] P-003064 T-003070 2 AS-7 AS Application Server disconnected with connection id: FA0F121146566656566F4B6D4F1211F94B4E345938F6.<instance>. (8359)
Workaround
Notes
Last Modified Date2/25/2021 8:56 PM
Attachment 
Files
Disclaimer The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.