Kbase 19011: Apptivity 3.1 limitations with Managers as Windows NTService
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
8/4/1999 |
|
Apptivity 3.1 limitations with Managers as Windows NTService
Apptivity 3 limitations with Managers as Windows NT Services
Tests with Apptivity 3.1 Running the DistributionManager
and the ComponentManger as Windows NT Services show that
there exist an undocumented limitation in the length of the
service parameters what causes under certain circumstances the
to the service given Java VM arguments to be ignored.
This applies also to the CLASSPATH argument given to
the service.
For instance creating the NT Service for the
DistributionManager the following way will cause
the service to start fine but to ignore the parameters:
AppServ -install DMService progress.apptivity.dmanager.DistributionMan
ager -ca=.;D:\Apptivity31;D:\Apptivity31\Java\lib\classes.zip;
D:\Apptivity31\OrbixWeb;D:\Apptivity31\Javax\lib\jsdk.jar;
D:\Apptivity31\Gallery\Beans\swingall.jar;.;D:\Apptivity31\Server;
D:\Apptivity31\Server\jre\lib\rt.jar;D:\Apptivity31\Server\OrbixWeb;
D:\Apptivity31\Server\Javax\lib\jsdk.jar;D:\Apptivity31\Gallery\Beans;
D:\Apptivity31\Server\Javax\lib\jsdk.jar;D:\Apptivity31\Gallery\Beans;
D:\Apptivity31\Server\Gallery\Beans\swingall.jar -start=d:\apptivity31
\server\service\DM_start.properties -stop=d:\apptivity31\server\servic
e\DM_stop.properties -Dapptivity.dmanager.name=DMService -Dapptivity.d
manager.host=pcrwe2
The solution for the problem is to make the classpath as short as
possible and over give the needed properties with the JVM argument
-Dapptivity.properties.file=<disk:\path\filename> to the Managers.
Tested example for creating the NT Service with AppServ.exe
for the ComponentManager which gives the desired results:
AppServ -install CM31Serv progress.apptivity.cmanager.ComponentManager
-ca=.;D:\Apptivity31\Server;D:\Apptivity31\Server\jre\lib\rt.jar;
D:\Apptivity31\Server\OrbixWeb;D:\Apptivity31\Server\Javax\lib\jsdk.ja
r;D:\Apptivity31\Gallery\Beans;D:\Apptivity31\Server\Gallery\Beansswingall.jar
-start=d:\apptivity31\server\service\CM1_start.properties -stop=d:\app
tivity31\server\service\CM1_stop.properties -Dapptivity.properties.fil
e=d:\apptivity31\server\service\cm.prop
where the contents of the file cm.prop is:
apptivity.cmanager.host=pcrwe2
apptivity.naming.host=pcrwe2
apptivity.naming.retries=6
apptivity.naming.wait=5
apptivity.naming.host.alt=pcrwe
apptivity.naming.port.alt=7777
apptivity.cmanager.name=test
apptivity.cmanager.cfactoryName=test
apptivity.cmanager.port=7890
If the service is configured to start automatically at boot
time additional for it's user account it is also necessary
to have the right to logon as service.
Additional note: Since with the Service installation utility
the password for the user is not supplied
it is necessary after creation of the service to
go to the service entry over the NT Control panel > Services
and retype the password twice since otherwise an error 1069:
"The service did not start due login failure" will occur.
References To Written Documentation or other
KnowledgeBase Documents:
Progress Apptivity Update Booklet
DISCLAIMER
The origins of this information may be internal or
external to Progress Software Corporation. Progress
Software Corporation makes all reasonable efforts
to verify this information. However, the
information provided in this document is for your
information only.
Progress Software Corporation makes no explicit or
implied claims to the validity of this information.
Any trademarks referenced in this document are the
property of their respective owners. Consult your
product manuals for complete trademark information.
Copyright 1999 Progress Software Corporation, Inc.
All Rights Reserved.