Kbase 18863: Apptivity Java Component Manager on AS400 V4R2M0 JDK 1.1.4
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
10/06/1999 |
|
Apptivity Java Component Manager on AS400 V4R2M0 JDK 1.1.4
DRAFT COPY - Currently under review and edit.
Knowledgebase number: 18863
Creation Date: May-24-1999
Modified Date:
This document applies to: Apptivity
Version and Release Number: 3.01
Summary:
Apptivity Java Component Manager on AS400 V4R2M0 JDK 1.1.4
Step by step details:
Apptivity 3.x is currently (May 24. 1999) not released yet for
AS400 and that is why also no documentation exists at this time.
That article may assists customer needs to test already
their application on the JVM for AS400 to get faster success.
For the installation and configuration of Apptivity on
the AS400 machine see KBase ID: 18860 title:
"Apptivity Java Distribution Manager on AS400 V4R2M0 JDK 1.1.4"
Based on the example provided with the mentioned kbase entry
the steps to run the Apptivity Component Manager are similar.
The best way to give the necessary properties
for the Component Manager being able to connect to the
Distribution Manager on the AS400 is by a file with the name
cmanager.properties
located in the Component Manager's current working or
start directory, which with the tested example was the same as
the that of the Distribution Manager and the
ifstools command dsplnk would show for the contents of
the Component Manager's start directory:
Directory . . . . : /rwe/app
Type options, press Enter.
5=Next level 8=Display attributes
Opt Object link Type
com DIR
cmanager.propertie > STMF
dmanager.propertie > STMF
java DIR
javax DIR
jdbc DIR
netscape DIR
org DIR
progress DIR
sun DIR
sunw DIR
Gallery DIR
Ie DIR
The really for the Component Manager needed properties
for the example are:
apptivity.naming.host which has to be the same value as
apptivity.dmanager.host
and
apptivity.cmanager.host which value should be the
hostname of the machine the Component Manager is
running on.
Resulting from that the contents of the
cmanager.properties created on the client and transferred to
the AS400 machine using Client Access e.g looks like:
apptivity.naming.host=priorat
apptivity.naming.port=2804
apptivity.cmanager.host=priorat
apptivity.log.level=2
The AS400 system console command to start the
Apptivity Component Manager after the CLASSPATH
set with the command wrkenvvar :
java CLASS('progress.apptivity.cmanager.ComponentManager')
The above description is based on tests made with
Apptivity 3.01 build 159 appearing the Component Manager
working fine on AS400 V4R2M0 and the installed JDK 1.1.4
5769JV1 *COMPATIBLE AS/400 Developer Kit for Java .
References To Written Documentation or Other
KnowledgeBase Documents:
KBase ID: 18860
Apptivity Deployment Guide
Apptivity 3.01 Online Documentation
http://publib.boulder.ibm.com/pubs/html/as400/java/rzaha.htm
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.