Salesforce

Can the Appserver PROPATH be set using an .ini file?

« Go Back

Information

 
TitleCan the Appserver PROPATH be set using an .ini file?
URL NameP51222
Article Number000156492
EnvironmentProduct: Progress
Version: 9.x
Product: OpenEdge
Version: 10.x, 11.x
OS: Windows
Question/Problem Description
Can the Appserver PROPATH be set in the [WinChar Startup] of an .ini file
Can the Appserver PROPATH be set using an .ini file instead of OpenEdge Explorer
Can the Appserver PROPATH be set using an .ini file instead of the PATH definition in the ubroker.properties file
If the application code paths are not defined in the ubroker.properties PROPATH, will the AppServer programs still be found using the ini file specified in the Agent startup parameters? 
Is it possible to have the PROPATH setting in the INI file specified with the -ininame switch in the startup line of an AppServer agent
Will an INI file set the PROPATH for the AppServer agent: srvrStartupParam : -pf appserverstart.pf -ininame progress.ini
Steps to Reproduce
Clarifying Information
Error Message
Defect Number
Enhancement Number
Cause
Resolution
In Progress 8, the PROPATH for a Windows AppServer could be configured in the WinChar Startup section of an .ini file.
Refer to Article  How to set the PROPATH for Progress 8 AppServers   

For Progress 9 or later versions of AppServer or WebSpeed agent:
  • Only the PROPATH  setting from the ubroker.properties file is used. Refer to Article  How to set PROPATH for AppServer and WebSpeed?   
  • For AppServer and WebSpeed sessions the Registry/INI setting is ignored. It is no longer possible to set the PROPATH or any other parameter using an .ini file in the agent startup parameters. 
  • When the PROPATH is set in the srvrStartupParam : -pf ubrokerstart.pf -ininame progress.ini, and not in the ubroker.properties configuration file, the AppServer will fail to start with errors 8113, 8117, 8100, 8067:    
Message from server : Startup Procedure Failed (8113) 
IOException reading message from server : java.io.EOFException: pipe to server broken (8117) 
cannot start server. (8100) 
admin error response received: 2. (8067)
Workaround
Notes
Keyword Phrase
Last Modified Date11/20/2020 7:39 AM

Powered by