Server Installation

This chapter describes how to install ProFrame Server.

The following are the steps for installing ProFrame Server.

  1. Checking directory structure before installation

  2. Running the installer

  3. Modifying configuration files

The process of installing Server is the same regardless of the platform.

1. Checking Directory Structure before Installation

The directory structure must be as follows:

{INSTALL_HOME_DIRECTORY}
|---- package
        +---- jeus
        +---- tmax
{INSTALL_HOME_DIRECTORY}

ProFrame Server installation directory.

package

Contains the following subdirectories.

Subdirectory Description

package/jeus

JEUS installation directory. To use another JEUS that is installed in another directory, set a symbolic link.

A symbolic link, also called a soft link, allows to access a different path, not an actual path, and not to copy unnecessary files. It is used when a library is used by multiple directories or when a single file is shared by multiple users.

package/tmax

Tmax installation directory. To use another Tmax that is installed in another directory, set a symbolic link.

2. Running the Installer

The following describes how to run the installer to install ProFrame Server.

The installer can install the following.

  1. Installing RunTime

  2. Installing integrated server

  3. Installing both RunTime and integrated server

2.1. Installing RunTime

The installer provides default values. Since you cannot go to a previous step in a shell, change necessary values after the installation. However, you can go to a previous step up to a certain step by pressing <back> or <Enter>.

The following are the steps for installing RunTime by using a binary file (ProFrame_C_5_0_Fix1_{OS_Type}_{Bit}.bin).

  1. Grant execute permission to the binary file.

    > chmod u+x ProFrame_C_5_0_Fix1_AIX_64.bin
    [pfm5qa2@tmaxi7:/data2/pfm5qa2]$ProFrame_C_5_0_Fix1_AIX_64.bin
Preparing to install...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...

Launching installer...

Preparing CONSOLE Mode Installation...

===============================================================================
ProFrame_C_5.0_Fix#1             (created with InstallAnywhere by Macrovision)
-------------------------------------------------------------------------------

===============================================================================
Introduction
------------

APPLIES TO

- Product Name : ProFrame_C_5.0_Fix#1
- Platform : AIX 64bit
- DB : Tibero 5.0, Oracle 10g/11g
- JEUS Ver : JEUS 6.0 Fix#8
- TMAX Ver : Tmax5 SP2
- JAVA Ver : 1.5 over

It is strongly recommended that you quit all programs before continuing with
this installation.

Respond to each prompt to proceed to the next step in the installation.  If you
want to change something on a previous step, type 'back'.

You may cancel this installation at any time by typing 'quit'.



PRESS <ENTER> TO CONTINUE:

  2. Check the license agreement and then enter 'Y' and press <Enter>.

    ===============================================================================
License Agreement
-----------------

Installation and Use of ProFrame_C_5.0_Fix#1 Requires Acceptance of the
Following License Agreement:

ProFrame C 5.0 Fix#1
This Software is made by 'TmaxSoft Co.,Ltd.' and this software is distributed
under our license agreement.

Software End-User License Agreement

Product : ProFrame C 5.0 Fix#1
This is a legal agreement between you (either an individual or an entity) and
TmaxSoft, Incorporated.
By opening the  sealed software package and/or by using the software, you agree
to be bound by the terms of this agreement.

ProFrame C 5.0 Fix#1 Software License

1.  Grant of License:  This ProFrame C 5.0 Fix#1 Software License Agreement
("License") permits you to use one copy of the TmaxSoftware product Tmax, on
any single computer, provided the software is in use on only one computer at
any one time. If this package is a license pack, you may make and use
additional copies of the software up to the number of licensed copies
authorized.  If you have multiple licenses for the software, then at any time
you may have as many copies of the software in use as you have licenses.
The software is "in use" on a computer when it is loaded into the temporary
memory (i.e., RAM) or installed into the permanent memory (e.g., hard disk,

PRESS <ENTER> TO CONTINUE:

CD-ROM, or other storage device) of that computer, except that a copy installed
on a network server for the sole purpose of distribution to other computers is
not "in use".  If the anticipated number of users of the software will exceed
the number of applicable licenses, then you must have a reasonable mechanism or
process in place to ensure that the number of persons using the software
concurrently does not exceed the number of licenses.

2.  Copyright:  The software (including any images, applets, photographs,
animations, video, audio, music and text  incorporated into the software) is
owned by TmaxSoft or its suppliers and international treaty provisions.
Therefore,  you must treat the software like any other copyrighted material
(e.g., a book or musical recording) except that you may either (a) make one
copy of the software solely for backup or archival purposes, or (b) transfer
the software to a single hard disk provided you keep the original solely for
backup or archival purposes.  You may not copy the printed materials
accompanying the software, nor print copies of any user documentation provided
in "online"or electronic form.

3.  Other restrictions:  This license is your proof of license to exercise the
rights granted herein and must be retained by you.
You may not rent or lease the software, but you may transfer your rights under
this license on a permanent basis provided you transfer this license, the

PRESS <ENTER> TO CONTINUE:

software, and all accompanying printed materials, retain no copies, and the
recipient agrees to the terms of this license.  You may not reverse engineer,
decompile, or disassemble the software, except to the extent that the foregoing
restriction is expressly prohibited by applicable law.


TmaxSoft Co., Ltd.



DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT? (Y/N):

  3. Choose an installation set. To install RunTime, enter '1' and press <Enter>.

    Since the default value is '1', you can just press <Enter>.

    ===============================================================================
Choose Install Set
------------------

Please choose the Install Set to be installed by this installer.

  ->1- Runtime
    2- Server
    3- All

ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS <ENTER> TO ACCEPT THE DEFAULT
   : 1

  4. Choose a Java directory. The Java home directory must be set in the environment variable ($JAVA_HOME) in advance.

    ===============================================================================
Choose Java Home Folder
-----------------------

Please Choose Java Home Folder ($JAVA_HOME):

Input Java Home Path (DEFAULT: /usr/java5):

  5. Choose an installation directory.

    Enter a desired directory or just press <Enter> to use the default value.

    ===============================================================================
Choose Install Folder(Input FrameWork Root)
-------------------------------------------

Where would you like to install?

  Default Install Folder: /data2/pfm5qa2/proframe5.0

ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT
      :

  6. Enter basic ProFrame information such as PROJECT_ID and log and build server information.

    ===============================================================================
ProFrame Environment Setting
-----------------------------

Enter requested information

PROJECT_ID (DEFAULT: PRJ1):

PROJECT_ROOT (DEFAULT: /data2/pfm5qa2/proframe5.0):

LOGIN_TYPE (DEFAULT: 1):

LOGSERVER_IP (DEFAULT: 192.168.1.87):

LOGSERVER_PORT (DEFAULT: 8585):

BUILDSERVER_PORT (DEFAULT: 8586):
    Environment Variable Description

    PROJECT_ID

    Current project ID. Can be up to 6 bytes. It is the same as the ID to be selected when logging in Studio.

    PROJECT_ROOT

    Default project directory. It is usually the same as the installation directory.

    LOGIN_TYPE

    Server type to connect.

    • 1: ProFrame

    • 2: ProFrame Admin

    • 3: TPM

    • 4: WAS

    • 10: AP

    To access ProFrame Server, enter '1'. Currently, only '1' is used and other values (2, 3, 4, and 10) are not used.

    LOGSERVER_IP

    IP address of the server where a log server is installed.

    LOGSERVER_PORT

    Port number of the server to be used by a log server.

    BUILDSERVER_PORT

    Port number of the server to be used by a build server.

  7. Enter Tmax installation directory.

    It is automatically checked whether Tmax is installed in the entered directory. If Tmax does not exist in the entered directory, a window where you can change the directory or end the installation is displayed.

    ===============================================================================
Choose Tmax Installed Folder
-----------------------------


Where are been installed? (DEFAULT: /data2/pfm5qa2/proframe5.0/package/tmax)
   :

  8. Enter an IP address and a port number of the system where Tmax is installed.

    ===============================================================================
RunTime Environment Setting
---------------------------



TMAX_HOST_ADDR (DEFAULT: 192.168.1.87):

TMAX_HOST_PORT (DEFAULT: 8888): 8786

  9. For RunTime engine’s DBMS connection (non-XA), choose a database and enter its information.

    ===============================================================================
Choose RunTime DB Vendor
------------------------

Enter requested information

  ->1- Tibero
    2- Oracle

ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT:
   :

===============================================================================
RunTime DB Connect Infomation Setting (tibero)
----------------------------------------------

CONNECT_INFO(Tibero) Setting Infomation for Non-XA Enviroment.

TB_HOME (DEFAULT: /home/tibero):

TB_SID (DEFAULT: tibero):

DB_USER (DEFAULT: root): RTE_USER

DB_PASSWORD (DEFAULT: root): RTE_PASSWORD

DB_SERVER_IP (DEFAULT: 127.0.0.1):

DB_SERVER_PORT (DEFAULT: 38629):
    Environment Variable Description

    TB_HOME

    Home directory where Tibero client is installed.

    TB_SID

    Connection name set in Tibero client’s tbdsn.tbr.

    DB_USER

    User name of RunTime DB connection account.

    DB_PASSWORD

    Password of RunTime DB connection account.

    DB_SERVER_IP

    IP address of RunTime DB server.

    DB_SERVER_PORT

    Port number of RunTime DB server.

  10. To use RunTime engine’s DBMS, enter the full path to JDBC library.

    Since the installer does not provide the JDBC library, download it from each DBMS vendor.

    ===============================================================================
Input tibero JDBC Library File Full Path(Local)
-----------------------------------------------

$

Input JDBC library file full path(local) (DEFAULT: Based On Locale)
   : /data2/pfm5qa2/tibero5-jdbc-14.jar

  11. Choose whether to create RunTime engine’s database.

    Selecting '1' creates RunTime engine’s database based on the information entered in previous steps. Selecting '2' only installs files and does not create a database. You can manually create a database.

    ===============================================================================
Create Runtime DB Schema
------------------------

Do you want to create a new runtime database schema?

  ->1- YES
    2- NO

ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE
   DEFAULT:

  12. Check the entered information. If there is incorrect information, cancel the installation and start it again.

    ===============================================================================
Set Variables
-------------

LOCAL_HOST: tmaxi7
OS_ARCH: PPC
OS_VENDOR: aix
OS_BIT: 64
OS_VERSION: 6
LD_PATH: LIBPATH
USER_INSTALL_DIR: /data2/pfm5qa2/proframe5.0
PROJECT_ID: PRJ1
PRJROOT: /data2/pfm5qa2/proframe5.0
LOGIN_TYPE: 1
LOGSERVER_IP: 192.168.1.1
LOGSERVER_PORT: 8585
BUILDSERVER_PORT: 8586
JAVA_HOME: /usr/java5
USER_MAGIC_FOLDER_1: /data2/pfm5qa2/proframe5.0
USER_MAGIC_FOLDER_2:
USER_MAGIC_FOLDER_3: /data2/pfm5qa2/proframe5.0/package/tmax

...

TMAX_HOST_ADDR: 192.168.1.1
TMAX_HOST_PORT: 8786
TMAXDIR: /data2/pfm5qa2/proframe5.0/package/tmax
TP_HOME_FLAG: TRUE
RT_DB_HOME: /data2/tibero5
RT_DB_SID: tibero
RT_DB_USERNAME: RTUSER
RT_DB_PASSWORD: RTPASS
RT_DB_IP: 192.168.1.1
RT_DB_PORT: 38629
RT_DB_VENDOR: tibero
RT_DB_DS_CLASS: com.tmax.tibero.jdbc.ext.TbConnectionPoolDataSource
RT_DB_DRIVER: com.tmax.tibero.jdbc.TbDriver
RT_DB_URL: jdbc:tibero:thin:@192.168.1.1:38629:tibero
RT_DB_JDBC_LIB_FULLPATH: /data2/pfm5qa2/tibero5-jdbc-14.jar
CREATE_RT_DB_TABLE: 0

PRESS <ENTER> TO INSTALL:

  13. Check the installation summary. Pressing <Enter> starts the installation.

    ===============================================================================
Pre-Installation Summary
------------------------

Please Review the Following Before Continuing:

Product Name:
    ProFrame_C_5.0_Fix#1

Install Folder:
    /data2/pfm5qa2/proframe5.0

Install Set
    Runtime

Disk Space Information (for Installation Target):
    Required:  45,732,264 bytes
    Available: 107,586,813,952 bytes

PRESS <ENTER> TO CONTINUE:

  14. The progress bar shows the installation status.

    ===========================================================
Installing...
-------------

[===============|===============|===============|===============]
[---------------|---------------|---------------|---------------]

  15. If you select '1' in the step 11 to create RunTime engine’s database, the following is the result after the installation. If an error occurs, manually create a database by using SQL in $PRJROOT/db_sql/RunTime.

    ===============================================================================
RunTime DB CREATE RESULT
------------------------

===============================================================================
Run Ant (RT_CREATE&INSERT)
===============================================================================

RT_TABLE_CREATE_STDOUT:
-----------------------
Buildfile: build.xml

prepare:

db-rt-create-schema:
      [sql] Executing resource: /data2/pfm5qa2/proframe5.0/db_sql/RunTime/PFM5C
_Create_RuntTime_Table_5.0.1.0_FULL.sql
[sql] 568 of 568 SQL statements executed successfully

db-rt-insert-data:
      [sql] Executing resource: /data2/pfm5qa2/proframe5.0/db_sql/RunTime/PFM5C
_Insert_RuntTime_Data_5.0.1.0_FULL.sql
[sql] 1767 of 1767 SQL statements executed successfully

BUILD SUCCESSFUL
Total time: 12 seconds


RT_TABLE_CREATE_STDERR:
-----------------------

RT_TABLE_CREATE_STDEXITCODE:
----------------------------



PRESS <ENTER> TO CONTINUE:

  16. Installing RunTime automatically execute pfmdlupdate. For this, tdlinit must operate. If an error occurs, manually execute pfmdlupdate by using a shell file in the $PRJROOT path.

    ===============================================================================
PFM DLUPDATE
------------

Press <Enter> To pfmdlupdate automatically. (tdlinit required)
If fail pfmdlupdate, please manually pfmdlupdate using shell file.

FilePath: /data2/pfm5qa2/proframe5.0/pfm_dlupdate.sh

PRESS <ENTER> TO CONTINUE:


===============================================================================
PFM DLUPDATE RESULT
-------------------

DLUPDATE_STDOUT:
----------------
#------------------------------------------------------
Executing DLUPDATE after executing TDLINIT
#------------------------------------------------------
-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperOnlstst00010t01InStr.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperOnlstst00010t01InStr.so -
-(pfmdlupdate) sucess : libpfmMapperOnlstst00010t01InStr.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperOnlstst00010t01InStr_WS.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperOnlstst00010t01InStr_WS.so -
-(pfmdlupdate) sucess : libpfmMapperOnlstst00010t01InStr_WS.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperOnlstst00010t01OutStr.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperOnlstst00010t01OutStr.so -
-(pfmdlupdate) sucess : libpfmMapperOnlstst00010t01OutStr.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperOnlstst00010t01OutStr_WS.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperOnlstst00010t01OutStr_WS.so -
-(pfmdlupdate) sucess : libpfmMapperOnlstst00010t01OutStr_WS.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperOutQueDataBody.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperOutQueDataBody.so -
-(pfmdlupdate) sucess : libpfmMapperOutQueDataBody.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperOutQueDataBody_WS.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperOutQueDataBody_WS.so -
-(pfmdlupdate) sucess : libpfmMapperOutQueDataBody_WS.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperOutQueDataHeader.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperOutQueDataHeader.so -
-(pfmdlupdate) sucess : libpfmMapperOutQueDataHeader.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperOutQueDataHeader_WS.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperOutQueDataHeader_WS.so -
-(pfmdlupdate) sucess : libpfmMapperOutQueDataHeader_WS.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmCustomizeHeaderStr.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmCustomizeHeaderStr.so -
-(pfmdlupdate) sucess : libpfmMapperPfmCustomizeHeaderStr.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmCustomizeHeaderStr_WS.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmCustomizeHeaderStr_WS.so -
-(pfmdlupdate) sucess : libpfmMapperPfmCustomizeHeaderStr_WS.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmErrorHeaderStr.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmErrorHeaderStr.so -
-(pfmdlupdate) sucess : libpfmMapperPfmErrorHeaderStr.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmErrorHeaderStr_WS.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmErrorHeaderStr_WS.so -
-(pfmdlupdate) sucess : libpfmMapperPfmErrorHeaderStr_WS.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmErrorHeaderSubStr.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmErrorHeaderSubStr.so -
-(pfmdlupdate) sucess : libpfmMapperPfmErrorHeaderSubStr.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmErrorHeaderSubStr_WS.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmErrorHeaderSubStr_WS.so -
-(pfmdlupdate) sucess : libpfmMapperPfmErrorHeaderSubStr_WS.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmMessageHeaderStr.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmMessageHeaderStr.so -
-(pfmdlupdate) sucess : libpfmMapperPfmMessageHeaderStr.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmMessageHeaderStr_WS.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmMessageHeaderStr_WS.so -
-(pfmdlupdate) sucess : libpfmMapperPfmMessageHeaderStr_WS.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmMessageHeaderSubStr.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmMessageHeaderSubStr.so -
-(pfmdlupdate) sucess : libpfmMapperPfmMessageHeaderSubStr.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmMessageHeaderSubStr_WS.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmMessageHeaderSubStr_WS.so -
-(pfmdlupdate) sucess : libpfmMapperPfmMessageHeaderSubStr_WS.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmSystemHeaderStr.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmSystemHeaderStr.so -
-(pfmdlupdate) sucess : libpfmMapperPfmSystemHeaderStr.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmSystemHeaderStr_WS.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmSystemHeaderStr_WS.so -
-(pfmdlupdate) sucess : libpfmMapperPfmSystemHeaderStr_WS.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmTestModuleHeaderStr.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmTestModuleHeaderStr.so -
-(pfmdlupdate) sucess : libpfmMapperPfmTestModuleHeaderStr.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/pmap/lib/libpfmMapperPfmTestModuleHeaderStr_WS.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmMapperPfmTestModuleHeaderStr_WS.so -
-(pfmdlupdate) sucess : libpfmMapperPfmTestModuleHeaderStr_WS.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/dbio/lib/libpfmDbioPfmBatchExt.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmDbioPfmBatchExt.so -
-(pfmdlupdate) sucess : libpfmDbioPfmBatchExt.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/dbio/lib/libpfmDbioPfmSm.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmDbioPfmSm.so -
-(pfmdlupdate) sucess : libpfmDbioPfmSm.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/dbio/lib/libpfmDbioPfmSmExt.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmDbioPfmSmExt.so -
-(pfmdlupdate) sucess : libpfmDbioPfmSmExt.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/dbio/lib/libpfmDbioPfmSvc.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmDbioPfmSvc.so -
-(pfmdlupdate) sucess : libpfmDbioPfmSvc.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/release/dbio/lib/libpfmDbioPfmSvcExt.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmDbioPfmSvcExt.so -
-(pfmdlupdate) sucess : libpfmDbioPfmSvcExt.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/package/proframe/pfm/lib/libpfmIpprExternalProcess.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmIpprExternalProcess.so -
-(pfmdlupdate) sucess : libpfmIpprExternalProcess.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/package/proframe/pfm/lib/libpfmIpprProcess.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmIpprProcess.so -
-(pfmdlupdate) sucess : libpfmIpprProcess.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/package/proframe/pfm/lib/libpfmOpprExternalProcess.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmOpprExternalProcess.so -
-(pfmdlupdate) sucess : libpfmOpprExternalProcess.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/package/proframe/pfm/lib/libpfmOpprProcess.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmOpprProcess.so -
-(pfmdlupdate) sucess : libpfmOpprProcess.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/package/proframe/pfm/lib/libpfmServiceFrame.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmServiceFrame.so -
-(pfmdlupdate) sucess : libpfmServiceFrame.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/package/proframe/pfm/lib/libpfmServiceFrameExt.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmServiceFrameExt.so -
-(pfmdlupdate) sucess : libpfmServiceFrameExt.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/package/proframe/pfm/lib/libpfmServiceModule.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmServiceModule.so -
-(pfmdlupdate) sucess : libpfmServiceModule.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/package/proframe/pfm/lib/libpfmServiceModuleExt.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmServiceModuleExt.so -
-(pfmdlupdate) sucess : libpfmServiceModuleExt.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/package/proframe/pfm/lib/libpfmTransactionFrame.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmTransactionFrame.so -
-(pfmdlupdate) sucess : libpfmTransactionFrame.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/package/proframe/pfm/lib/libpfmAmsWrapper.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmAmsWrapper.so -
-(pfmdlupdate) sucess : libpfmAmsWrapper.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/package/proframe/pfm/lib/libpfmResidentBatch.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmResidentBatch.so -
-(pfmdlupdate) sucess : libpfmResidentBatch.so -

-(pfmrel) Does not copy because source and target directories are the same. -
-(pfmdlupdate) ln -s /data2/pfm5qa2/proframe5.0/package/proframe/pfm/lib/libpfmAmsWrapperExt.so
/data2/pfm5qa2/proframe5.0/package/tmax/tdlcall/mod/pfmAmsWrapperExt.so -
-(pfmdlupdate) sucess : libpfmAmsWrapperExt.so -


DLUPDATE_STDERR:
----------------
(I) TDLUTIL0046 TDLDIR initialization complete [TDL0331]
(I) TDLUTIL0083 pfmMapperOnlstst00010t01InStr.53739e9e updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperOnlstst00010t01InStr_WS.53739e9f updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperOnlstst00010t01OutStr.53739ea0 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperOnlstst00010t01OutStr_WS.53739ea1 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperOutQueDataBody.53739ea2 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperOutQueDataBody_WS.53739ea3 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperOutQueDataHeader.53739ea4 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperOutQueDataHeader_WS.53739ea5 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmCustomizeHeaderStr.53739ea6 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmCustomizeHeaderStr_WS.53739ea7 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmErrorHeaderStr.53739ea8 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmErrorHeaderStr_WS.53739ea9 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmErrorHeaderSubStr.53739eaa updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmErrorHeaderSubStr_WS.53739eab updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmMessageHeaderStr.53739eac updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmMessageHeaderStr_WS.53739ead updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmMessageHeaderSubStr.53739eae updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmMessageHeaderSubStr_WS.53739eaf updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmSystemHeaderStr.53739eb0 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmSystemHeaderStr_WS.53739eb1 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmTestModuleHeaderStr.53739eb2 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmMapperPfmTestModuleHeaderStr_WS.53739eb3 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmDbioPfmBatchExt.53739eb4 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmDbioPfmSm.53739eb5 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmDbioPfmSmExt.53739eb6 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmDbioPfmSvc.53739eb7 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmDbioPfmSvcExt.53739eb8 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmIpprExternalProcess.53739eb9 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmIpprProcess.53739eba updated successfully [TDL0418]
(I) TDLUTIL0083 pfmOpprExternalProcess.53739ebb updated successfully [TDL0418]
(I) TDLUTIL0083 pfmOpprProcess.53739ebc updated successfully [TDL0418]
(I) TDLUTIL0083 pfmServiceFrame.53739ebd updated successfully [TDL0418]
(I) TDLUTIL0083 pfmServiceFrameExt.53739ebe updated successfully [TDL0418]
(I) TDLUTIL0083 pfmServiceModule.53739ebf updated successfully [TDL0418]
(I) TDLUTIL0083 pfmServiceModuleExt.53739ec0 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmTransactionFrame.53739ec1 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmAmsWrapper.53739ec2 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmResidentBatch.53739ec3 updated successfully [TDL0418]
(I) TDLUTIL0083 pfmAmsWrapperExt.53739ec4 updated successfully [TDL0418]


DLUPDATE_STDEXITCODE:
---------------------


PRESS <ENTER> TO CONTINUE:

  17. RunTime Server installation is complete.

    ===============================================================================
Installation Complete
---------------------

Congratulations. ProFrame_C_5.0_Fix#1 has been successfully installed to:

ProFrame: /data2/pfm5qa2/proframe5.0
Tmax: /data2/pfm5qa2/proframe5.0/package/tmax

PRESS <ENTER> TO EXIT THE INSTALLER:

  18. To support non-XA, create database connection information.

    Non-XA allows a server program to control transactions by directly connecting to a relational database system with native SQL. To support non-XA, compile the pfmDbioConnectDB.c file that creates database connection information and then update the libpfmDbioConnectDB.so library file that is created after the compilation.

    1. Compile the pfmDbioConnectDB.c file.

      [pfmtpqa@fwsol:/home2/pfmtpqa/ProFrame5.0/package/proframe/pfm_dev/src/pfmDbioConnectDB]$ make -f pfmDbioConnectDB.mk clean all

rm -f core pfmDbioConnectDB.o libpfmDbioConnectDB.so

cc        -DORACLE  -g -xarch=v9 -xmemalign=1i  -KPIC -xc99     -D_RND
-D_DEBUG -DUSE_TCACHE       -DTCACHE_ON        -DGLOBALCB
-DAUTOFREECB       -DTRACE            -DDEBUG       -I.
-I/home2/pfmtpqa/ProFrame5.0/package/proframe/pfm/inc
-I/home2/pfmtpqa/ProFrame5.0/release/pmap/inc
-I/home2/pfmtpqa/ProFrame5.0/release/pmap/src
-I/home2/pfmtpqa/ProFrame5.0/release/dbio/inc
-I/home2/pfmtpqa/ProFrame5.0/package/tmax/usrinc
-I/home2/pfmtpqa/ProFrame5.0/package/tmax
-I/home2/ora10g/oracle/product/10.2.0/client_1/precomp/public
-I/home2/ora10g/oracle/product/10.2.0/client_1/rdbms/public
-c pfmDbioConnectDB.c

`if test sun = "hpux" || test sun = "hpux_parisc" ; then echo "ld";
else echo "cc"; fi` -o libpfmDbioConnectDB.so pfmDbioConnectDB.o  `if
test sun != "hpux" && test sun != "hpux_parisc" ;  then echo "-g
-xarch=v9 -xmemalign=1i  -KPIC -xc99"; fi`  -xarch=v9 -xmemalign=1i
-B dynamic -xarch=v9 -KPIC -G -B dynamic -lc
-L/home2/ora10g/oracle/product/10.2.0/client_1/lib

[pfmtpqa@fwsol:/home2/pfmtpqa/ProFrame5.0/package/proframe/pfm_dev/src/pfmDbioConnectDB]$

    2. Update the libpfmDbioConnectDB.so library file.

      [pfmtpqa@fwsol:/home2/pfmtpqa/ProFrame5.0/package/proframe/pfm_dev/src/pfmDbioConnectDB]$ pfmdlupdate libpfmDbioConnectDB.so
-(pfmrel) mv /home2/pfmtpqa/ProFrame5.0/release/dbio/lib/libpfmDbioConnectDB.so
/home2/pfmtpqa/ProFrame5.0/release/lib/temp/libpfmDbioConnectDB.so_2008
0923203315 -

-(pfmrel) cp
/home2/pfmtpqa/ProFrame5.0/package/proframe/pfm_dev/src/pfmDbioConnectD
B/libpfmDbioConnectDB.so /home2/pfmtpqa/ProFrame5.0/release/dbio/lib -

-(pfmdlupdate) ln -s
/home2/pfmtpqa/ProFrame5.0/release/dbio/lib/libpfmDbioConnectDB.so
/home2/pfmtpqa/ProFrame5.0/package/tmax/tdlcall/mod/pfmDbioConnectDB.so -

(I) TDLUPDATE: pfmDbioConnectDB.48d8d3fb updated successfully[TDL0418]

-(pfmdlupdate) sucess : libpfmDbioConnectDB.so -

      The pfmdlupdate command moves files created with ProFrame library utility to a library directory and allows TDL by connecting to TDL directory ($TMAXDIR/mod) for library calls.

  19. To monitor the system, create apmmem. It loads ProFrame’s monitoring information to shared memory.

    The following creates apmmem.

    [pfmtpqa@fwsol:/home2/pfmtpqa]$ apmmemadmin –c
APMMEM ver. 2.4.0
This will create all APMMEM contents. Are you sure? [Y/N] y
APMMEM created.....

TRCBACKMEM created.....

EXTNMEM created.....

New all APMMEM contents initialized successfully.
WARNING : You must be restart your TP monitor(tmax, tuxedo etc..) to
monitor all transactions!!!

[pfmtpqa@fwsol:/home2/pfmtpqa]$

  20. Create TCache. It is a utility that caches database access information in shared memory while operating ProFrame system. It ensures ProFrame system performance.

    The following creates TCache with the following pfmtcacheadmin command.

    [pfmtpqa@fwsol:/home2/pfmtpqa]$ pfmtcacheadmin -c
TCACHE ver. 2.3.6
New TCACHE initialized successfully.
[pfmtpqa@fwsol:/home2/pfmtpqa]$

  21. Register ProFrame Server and service in Tmax.

    To register ProFrame Server and service, check the sample.m file in the $TMAXDIR/config directory. sample.m is a configuration file that is automatically created during Tmax installation. Users can rename this file.

    The following shows the *SVRGROUP, *SERVER, and *SERVICE sections to check. In this example, rename sample.m to tmconfig.m and then register ProFrame Server and service.

    *SVRGROUP
svg2    NODENAME="fwsol",
        DBNAME=ORACLE,
        OPENINFO=
"Oracle_XA+Acc=P/$DB_USER/$DB_PW+SqlNet=$EXTERNAL_SID+SesTm=60+LogDir=/
sw/pfm/ProFrame5.0/package/tmax/log/xalog",
        TMSNAME = tms_ora,
        TMSRECOVERY = N

*SERVER
TPFMIPPR       SVGNAME = svg1
TPFMADM02      SVGNAME = svg1
BONL02CN       SVGNAME = svg2
UONL01CN       SVGNAME = svg1, SVRTYPE=UCS
TPFMADM03      SVGNAME = svg1
PONL01CX       SVGNAME = svg2, MIN=0, MAX=1, LIFESPAN=IDLE_0

*SERVICE
SPFMIPPR       SVRNAME = TPFMIPPR
TESTSVC01      SVRNAME = BONL02CN
TESTSVC02      SVRNAME = BONL02CN
PFMADMSVC31   SVRNAME = TPFMADM03
PFMADMSVC11   SVRNAME = TPFMADM02

    Modify item values to appropriate ones in the *SVRGROUP section, and add the previous item values to the *SERVER and *SERVICE sections.

  22. The following are the steps for applying registered ProFrame Server and service. For more information about each command, refer to Tmax Getting Started Guide.

    1. Compile Tmax configuration file.

      [pfmtpqa@fwsol:/home2/pfmtpqa/ProFrame5.0/package/tmax/config]$ cfl -i 
fwsol.m
CFL is done successfully for node(fwsol)
[pfmtpqa@fwsol:/home2/pfmtpqa/ProFrame5.0/package/tmax/config]$ gst
SVC tables are successfully generated
GST is successfully done
      Command Description

      cfl

      Compiles Tmax configuration file.

      gst

      Creates tables based on Tmax configuration file.

    2. Restart Tmax server to apply the registered ProFrame Server and service.

      [pfmtpqa@fwsol:/home2/pfmtpqa/ProFrame5.0/package/tmax/config]$ tmdown
TMBOOT for node(fwsol) is starting:
Welcome to Tmax demo system: it will expire 2008/11/22
Today: 2008/9/23
        TMBOOT: TMM is starting: Tue Sep 23 21:04:38 2008
        TMBOOT: CLL is starting: Tue Sep 23 21:04:38 2008
        TMBOOT: CLH is starting: Tue Sep 23 21:04:38 2008
(I) CLH9991 Current Tmax Configuration: Number of client
handler(MINCLH) = 1
                Supported maximum user per node = 8040
                Supported maximum user per handler = 8040 [CLH0125]
        TMBOOT: TLM(tlm) is starting: Tue Sep 23 21:04:38 2008
        TMBOOT: TMS(tms_ora) is starting: Tue Sep 23 21:04:38 2008
        TMBOOT: TMS(tms_ora) is starting: Tue Sep 23 21:04:38 2008
        TMBOOT: SVR(TPFMIPPR) is starting: Tue Sep 23 21:04:38 2008
        TMBOOT: SVR(TPFMADM02) is starting: Tue Sep 23 21:04:38 2008
        TMBOOT: SVR(BONL02CN) is starting: Tue Sep 23 21:04:38 2008
        TMBOOT: SVR(UONL01CN) is starting: Tue Sep 23 21:04:38 2008
        TMBOOT: SVR(TPFMADM03) is starting: Tue Sep 23 21:04:38 2
      Command Description

      tmboot

      Starts Tmax server based on Tmax configuration file.

      tmdown

      Ends Tmax server.

    3. Confirm that ProFrame Server and service are registered.

      [pfmtpqa@fwsol:/home2/pfmtpqa/ProFrame5.0/package/tmax/config]$ $TMAXDIR/bin/tmadmin

      tmadmin is Tmax’s system management tool that checks Tmax server and service environment.

      [pfmtpqa@fwsol:/home2/pfmtpqa/ProFrame5.0/package/tmax/config]$ $TMAXDIR/bin/tmadmin

--- Welcome to Tmax Admin (Type "quit" to leave) ---


$$1 fwsol (tmadm): st -v
---------------------------------------------------------------------
 clh   svrname    (svri)   status   count   qcount   qpcount  emcount
---------------------------------------------------------------------
   0   TPFMIPPR   (   4)     RDY       0        0       0       0
   0   TPFMADM02  (   5)     RDY       0        0       0       0
   0   BONL02CN   (   6)     RDY       0        0       0       0
   0   UONL01CN   (   7)     NRDY      0        0       0       0
   0   TPFMADM03  (   8)     RDY       0        0       0       0


$$2 fwsol (tmadm): st -s

CLH 0:
---------------------------------------------------------------------
 svc_name   svr_name    count  cq_cnt  aq_cnt   q_avg    avg   status
---------------------------------------------------------------------
 SPFMIPPR    TPFMIPPR      0       0       0     0.000   0.000   RDY
 TESTSVC01   BONL02CN      0       0       0     0.000   0.000   RDY
 TESTSVC02   BONL02CN      0       0       0     0.000   0.000   RDY
 PFMADMSVC11 TPFMADM02     0       0       0     0.000   0.000   RDY
 PFMADMSVC31 TPFMADM03     0       0       0     0.000   0.000   RDY
      Command Description

      st –v

      Checks Tmax server environment.

      st –s

      Checks Tmax service environment.

      In the previous example, 'UONL01CN' is a residential batch and its server status is NRDY. That is, it can be confirmed that ProFrame Server and service are registered successfully.

      For information about ProFrame batch such as residential batch, refer to ProFrame Batch Programming Guide.

2.2. Installing Integrated Server

Integrated server manages versions of development tools and shared modules, history, and permissions, automatically creates sources, and analyzes resource impacts.

The installer provides default values. Since you cannot go to a previous step in a shell, change necessary values after the installation. However, you can go to a previous step up to a certain step by pressing <back> or <Enter>.

The following are the steps for installing the integrated server by using a binary file (ProFrame_C_5_0_Fix1_{OS_Type}_{Bit}.bin).

  1. Grant execute permission to the binary file.

    > chmod u+x ProFrame_C_5_0_Fix1_AIX_64.bin
    [pfm5qa2@tmaxi7:/data2/pfm5qa2]$ProFrame_C_5_0_Fix1_AIX_64.bin
Preparing to install...
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...

Launching installer...

Preparing CONSOLE Mode Installation...

===============================================================================
ProFrame_C_5.0_Fix#1             (created with InstallAnywhere by Macrovision)
-------------------------------------------------------------------------------

===============================================================================
Introduction
------------

APPLIES TO

- Product Name : ProFrame_C_5.0_Fix#1
- Platform : AIX 64bit
- DB : Tibero 5.0, Oracle 10g/11g
- JEUS Ver : JEUS 6.0 Fix#8
- TMAX Ver : Tmax5 SP2
- JAVA Ver : 1.5 over

It is strongly recommended that you quit all programs before continuing with
this installation.

Respond to each prompt to proceed to the next step in the installation.  If you
want to change something on a previous step, type 'back'.

You may cancel this installation at any time by typing 'quit'.



PRESS <ENTER> TO CONTINUE:

  2. Check the license agreement and then enter 'Y' and press <Enter>.

    ===============================================================================
License Agreement
-----------------

Installation and Use of ProFrame_C_5.0_Fix#1 Requires Acceptance of the
Following License Agreement:

ProFrame C 5.0 Fix#1
This Software is made by 'TmaxSoft Co.,Ltd.' and this software is distributed
under our license agreement.

Software End-User License Agreement

Product : ProFrame C 5.0 Fix#1
This is a legal agreement between you (either an individual or an entity) and
TmaxSoft, Incorporated.
By opening the  sealed software package and/or by using the software, you agree
to be bound by the terms of this agreement.

ProFrame C 5.0 Fix#1 Software License

1.  Grant of License:  This ProFrame C 5.0 Fix#1 Software License Agreement
("License") permits you to use one copy of the TmaxSoftware product Tmax, on
any single computer, provided the software is in use on only one computer at
any one time. If this package is a license pack, you may make and use
additional copies of the software up to the number of licensed copies
authorized.  If you have multiple licenses for the software, then at any time
you may have as many copies of the software in use as you have licenses.
The software is "in use" on a computer when it is loaded into the temporary
memory (i.e., RAM) or installed into the permanent memory (e.g., hard disk,

PRESS <ENTER> TO CONTINUE:

CD-ROM, or other storage device) of that computer, except that a copy installed
on a network server for the sole purpose of distribution to other computers is
not "in use".  If the anticipated number of users of the software will exceed
the number of applicable licenses, then you must have a reasonable mechanism or
process in place to ensure that the number of persons using the software
concurrently does not exceed the number of licenses.

2.  Copyright:  The software (including any images, applets, photographs,
animations, video, audio, music and text  incorporated into the software) is
owned by TmaxSoft or its suppliers and international treaty provisions.
Therefore,  you must treat the software like any other copyrighted material
(e.g., a book or musical recording) except that you may either (a) make one
copy of the software solely for backup or archival purposes, or (b) transfer
the software to a single hard disk provided you keep the original solely for
backup or archival purposes.  You may not copy the printed materials
accompanying the software, nor print copies of any user documentation provided
in "online"or electronic form.

3.  Other restrictions:  This license is your proof of license to exercise the
rights granted herein and must be retained by you.
You may not rent or lease the software, but you may transfer your rights under
this license on a permanent basis provided you transfer this license, the

PRESS <ENTER> TO CONTINUE:

software, and all accompanying printed materials, retain no copies, and the
recipient agrees to the terms of this license.  You may not reverse engineer,
decompile, or disassemble the software, except to the extent that the foregoing
restriction is expressly prohibited by applicable law.


TmaxSoft Co., Ltd.



DO YOU ACCEPT THE TERMS OF THIS LICENSE AGREEMENT? (Y/N):

  3. Choose an installation set. To install the integrated server, enter '2' and press <Enter>.

    ===============================================================================
Choose Install Set
------------------

Please choose the Install Set to be installed by this installer.

  ->1- Runtime
    2- Server
    3- All

ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS <ENTER> TO ACCEPT THE DEFAULT
   : 2

  4. Choose a Java directory. The Java home directory must be set in the environment variable ($JAVA_HOME) in advance.

    ===============================================================================
Choose Java Home Folder
-----------------------

Please Choose Java Home Folder ($JAVA_HOME):

Input Java Home Path (DEFAULT: /usr/java5):

  5. Choose an installation directory.

    Enter a desired directory or just press <Enter> to use the default value.

    ===============================================================================
Choose Install Folder(Input FrameWork Root)
-------------------------------------------

Where would you like to install?

  Default Install Folder: /data2/pfm5qa2/proframe5.0

ENTER AN ABSOLUTE PATH, OR PRESS <ENTER> TO ACCEPT THE DEFAULT
      :

  6. Enter basic ProFrame information such as PROJECT_ID and log and build server information.

    ===============================================================================
ProFrame Environment Setting
-----------------------------

Enter requested information

PROJECT_ID (DEFAULT: PRJ1):

PROJECT_ROOT (DEFAULT: /data2/pfm5qa2/proframe5.0):

LOGIN_TYPE (DEFAULT: 1):

LOGSERVER_IP (DEFAULT: 192.168.1.87):

LOGSERVER_PORT (DEFAULT: 8585):

BUILDSERVER_PORT (DEFAULT: 8586):
    Environment Variable Description

    PROJECT_ID

    Current project ID. Can be up to 6 bytes. It is the same as the ID to be selected when logging in Studio.

    PROJECT_ROOT

    Default project directory. It is usually the same as the installation directory.

    LOGIN_TYPE

    Server type to connect.

    • 1: ProFrame

    • 2: ProFrame Admin

    • 3: TPM

    • 4: WAS

    • 10: AP

    To access ProFrame Server, enter '1'. Currently, only '1' is used and other values (2, 3, 4, and 10) are not used.

    LOGSERVER_IP

    IP address of the server where a log server is installed.

    LOGSERVER_PORT

    Port number of the server to be used by a log server.

    BUILDSERVER_PORT

    Port number of the server to be used by a build server.

  7. Enter JEUS installation directory.

    It is automatically checked whether JEUS is installed in the entered directory. If JEUS does not exist in the entered directory, a window where you can change the directory or end the installation is displayed.

    ===============================================================================
Choose JEUS Installed Folder
-----------------------------

Where are been installed? (DEFAULT: /data2/pfm5qa2/proframe5.0/package/jeus)
   :

  8. Enter the integrated server information.

    ===============================================================================
Server Environment Setting
---------------------------

PFM_SERVER_IP(Locale) (DEFAULT: 192.168.1.87):

PFM_SERVER_PORT (DEFAULT: 8088):
    Environment Variable Description

    SERVER_IP

    IP address of a server where the integrated server is installed.

    SERVER_PORT

    Port number of a server used by the integrated server.

  9. For the integrated server’s DBMS connection (Datasource), choose a database and enter its information.

    ===============================================================================
Choose RIWS DB Vendor
---------------------

Enter requested information

    1- Tibero
  ->2- Oracle

ENTER THE NUMBER FOR YOUR CHOICE, OR PRESS <ENTER> TO ACCEPT THE DEFAULT:
   :


===============================================================================
RIWS oracle JDBC Data Source Setting
------------------------------------

Enter requested information

DB_SERVER_IP (DEFAULT: 192.168.1.87):

DB_SERVER_PORT (DEFAULT: 1521):

DB_SID (DEFAULT: orcl):

USER (RI) (DEFAULT: ri_user):

PASSWORD (RI) (DEFAULT: ri_pwd):

USER (WS) (DEFAULT: ws_user):

PASSWORD (WS) (DEFAULT: ws_pwd):
    Environment Variable Description

    DB_SERVER_IP

    DB server’s IP address.

    DB_SERVER_PORT

    DB server’s port number.

    DB_SID

    DB_SID.

    USER (RI)

    RI_DB’s connection account.

    PASSWORD (RI)

    RI_DB’s connection password.

    USER (WS)

    WS_DB’s connection account.

    PASSWORD (WS)

    WS_DB’s connection password.

  10. To use the integrated server’s DBMS, enter the full path to JDBC library.

    Since the installer does not provide the JDBC library, download it from each DBMS vendor.

    ===============================================================================
Input oracle JDBC Library File Full Path(Local)
-----------------------------------------------



Input JDBC library file full path(local) (DEFAULT: Based On Locale)
   : /data2/pfm5qa2/ojdbc14.jar

  11. Choose whether to create the integrated server’s database.

    Selecting '1' creates the integrated server’s database based on the information entered in previous steps. Selecting '2' only installs files and does not create a database. You can manually create a database.

    ===============================================================================
Create RIWS DB Schema
---------------------

Do you want to create a new RI/WS database schema?

  ->1- YES
    2- NO

ENTER THE NUMBER OF THE DESIRED CHOICE, OR PRESS <ENTER> TO ACCEPT THE
   DEFAULT:

  12. Check the entered information. If there is incorrect information, cancel the installation and start it again.

    ===============================================================================
Set Variables
-------------

LOCAL_HOST: tmaxi7
OS_ARCH: PPC
OS_VENDOR: aix
OS_BIT: 64
OS_VERSION: 6
LD_PATH: LIBPATH
USER_INSTALL_DIR: /data2/pfm5qa2/proframe5.0
PROJECT_ID: PRJ1
PRJROOT: /data2/pfm5qa2/proframe5.0
LOGIN_TYPE: 1
LOGSERVER_IP: 192.168.1.87
LOGSERVER_PORT: 8585
BUILDSERVER_PORT: 8586
JAVA_HOME: /usr/java5
USER_MAGIC_FOLDER_1: /data2/pfm5qa2/proframe5.0
USER_MAGIC_FOLDER_2: /data2/pfm5qa2/proframe5.0/package/jeus6
USER_MAGIC_FOLDER_3:

SERVER_IP: 192.168.1.87
SERVER_PORT: 8088
JEUS_BASE_PORT: 9736

JEUS_HOME: /data2/pfm5qa2/proframe5.0/package/jeus6
JEUS_HOME_FLAG: TRUE
RIWS_DB_IP: 192.168.32.123
RIWS_DB_SID: ORA10G
RI_DB_USERNAME: RIUSER
RI_DB_PASSWORD: RIPASSWD
WS_DB_USERNAME: WSUSER
WS_DB_PASSWORD: WSPASSWD
RIWS_DB_PORT: 1521
RIWS_DB_VENDOR: oracle
RIWS_DB_DS_CLASS: oracle.jdbc.pool.OracleConnectionPoolDataSource
RIWS_DB_DRIVER: oracle.jdbc.driver.OracleDriver
RIWS_DB_URL: jdbc:oracle:thin:@192.168.32.123:1521:ORA10G
RIWS_DB_JDBC_LIB_FULLPATH: /data2/pfm5qa2/ojdbc14.jar
CREATE_RIWS_DB_TABLE: 0

...

PRESS <ENTER> TO INSTALL:

  13. Check the installation summary. Pressing <Enter> starts the installation.

    ===============================================================================
Pre-Installation Summary
------------------------

Please Review the Following Before Continuing:

Product Name:
    ProFrame_C_5.0_Fix#1

Install Folder:
    /data2/pfm5qa2/proframe5.0

Install Set
    Server

Disk Space Information (for Installation Target):
    Required:  70,158,921 bytes
    Available: 107,532,849,152 bytes

PRESS <ENTER> TO CONTINUE:

  14. The progress bar shows the installation status.

    ===========================================================
Installing...
-------------

[===============|===============|===============|===============]
[---------------|---------------|---------------|---------------]

  15. If you select '1' in the step 11 to create the integrated server’s database, the following is the result after the installation. If an error occurs, manually create a database by using SQL in $PRJROOT/db_sql/RunTime.

    For BLOB data in the last column (CONTENT) of the DEV_TEMPLATE_INFO table, enter the contents in the file in $PRJROOT/db_sql/Template to the template management page in WebAdmin > COMMON SYSTEM > Template Mgmt.

    ===============================================================================
RIWS DB CREATE RESULT
---------------------

===============================================================================
Run Ant (RIWS_CREATE&INSERT)
===============================================================================

RI_TABLE_CREATE_STDOUT:
-----------------------
Buildfile: build.xml

prepare:

db-ws-create-schema:
      [sql] Executing resource: /data2/pfm5qa2/proframe5.0/db_sql/RIWS/03_PFM5C
_Create_WS_Table_Script_5.0.1.0_FULL.sql
[sql] 29 of 29 SQL statements executed successfully

db-ri-create-schema:
      [sql] Executing resource: /data2/pfm5qa2/proframe5.0/db_sql/RIWS/01_PFM5C
_Create_RI_Table_Script_5.0.1.1_FULL.sql
[sql] 179 of 179 SQL statements executed successfully

db-ri-insert-data:
      [sql] Executing resource: /data2/pfm5qa2/proframe5.0/db_sql/RIWS/02_PFM5C
_Insert_RI_Default_Data_5.0.1.1_FULL.sql
[sql] 1086 of 1086 SQL statements executed successfully

BUILD SUCCESSFUL
Total time: 9 seconds


RI_TABLE_CREATE_STDERR:
-----------------------


RI_TABLE_CREATE_STDEXITCODE:
----------------------------


===============================================================================
Run Ant (RIWS_SYNONYM)
===============================================================================

WS_GRANT_CREATE_STDOUT:
-----------------------
Buildfile: build.xml

prepare:

db-ri-create-synonym:
      [sql] Executing resource: /data2/pfm5qa2/proframe5.0/db_sql/RIWS/04_PFM5C
_Create_RI_Synonym_Script_5.0.1.1_FULL.sql
[sql] 2 of 2 SQL statements executed successfully

db-ws-create-synonym:
      [sql] Executing resource: /data2/pfm5qa2/proframe5.0/db_sql/RIWS/05_PFM5C
_Create_WS_Synonym_Script_5.0.1.1_FULL.sql
[sql] 15 of 15 SQL statements executed successfully

db-ri-create-grant:
      [sql] Executing resource: /data2/pfm5qa2/proframe5.0/db_sql/RIWS/06_PFM5C
_Create_RI_Synonym_Script_5.0.1.1_FULL.sql
[sql] 15 of 15 SQL statements executed successfully

BUILD SUCCESSFUL
Total time: 1 second


WS_GRANT_CREATE_STDERR:
-----------------------


WS_GRANT_CREATE_STDEXITCODE:
----------------------------


PRESS <ENTER> TO CONTINUE:

  16. ProFrame Server installation is complete.

    ===============================================================================
Installation Complete
---------------------

Congratulations. ProFrame_C_5.0_Fix#1 has been successfully installed to:

ProFrame: /data2/pfm5qa2/proframe5.0
Jeus : /data2/pfm5qa2/proframe5.0/package/jeus6

PRESS <ENTER> TO EXIT THE INSTALLER:

2.3. Installing both RunTime and Integrated Server

You can install RunTime and integrated server at the same time.

Use the same binary file: ProFrame_C_5_0_Fix1_{OS_Type}_{Bit}.bin. The process is the same as RunTime or integrated server installation process, except for that you must enter '3' in the Choose Install Set step.

===============================================================================
Choose Install Set
------------------

Please choose the Install Set to be installed by this installer.

  ->1- Runtime
    2- Server
    3- All

ENTER THE NUMBER FOR THE INSTALL SET, OR PRESS <ENTER> TO ACCEPT THE DEFAULT
   : 3

3. Modifying Configuration Files

The following describes about ProFrame configuration file.

3.1. Configuration Files

The following are configuration files related to integrated server installation.

$JEUS_HOME/webhome/app_home/WEB-INF/lib/PfmDevSvr.xml
$JEUS_HOME/config/{hostname}/JEUSMain.xml
$JEUS_HOME/config/{hostname}/{hostname}_servelt_engine1/WEBMain.xml

3.2. Configuration for Unit Tests

The TestFrameWorkConfig.jsp configuration file is used for unit tests of each service module (service and business modules). It is located in $JEUS_HOME/webhome/app_home/pfmdevsvr/webAdmin.

The following shows a part of TestFrameWorkConfig.jsp. To add a project, add a project condition to the if statement.

//---------------------------------------------------------
        String call_ip = null;
        String call_port = null;

        if(projectId.equals("PRJ1")) {
                call_ip = "192.168.1.1";
                call_port = "8786";
        } else {
                call_ip = "127.0.0.1";
                call_port = "1234";
        }

        final String DFLT_CALL_IP_ADDRESS    = call_ip;
        final String DFLT_CALL_PORT          = call_port;
        final String DFLT_CALL_SERVICE_NAME  = "SPFMIPPR";
//---------------------------------------------------------

The following describes each item.

Item Description

DFLT_CALL_IP_ADDRESS

IP address of a system where ProFrame Server is installed.

DFLT_CALL_PORT

Port number of Tmax server.

DFLT_CALL_SERVICE_NAME

Tmax service name for Input Pre-Processor (IPPR) server. Do not modify the value.

IPPR is Tmax server’s function that converts input messages to a structure defined by ProMapper.