DOC

NETWORK

By Jeanette Taylor,2014-04-23 22:41
15 views 0
NETWORK

Notes on the PHOENICS 3.5 Network Version ( using FLEXlm licensing)

    1.0 Overview

PHOENICS 3.5 is now provided with a floating licence capability. This means that any

    number of users on a network can have PHOENICS installed, and FLEXlm will control the

    number of simultaneous runs of PHOENICS.

In order to run PHOENICS

? Controlling FLEXlm daemons must be running on a Server

? A FLEXlm licence file must be on this Server and on the Users' PCs

    ? PHOENICS directories (all or some) must be on this Server and Users' PCs

Three CDROMS are supplied, labelled PHOENICS 3.5, SERVER and USER.

PHOENICS may be installed on each Users' PC, or only on a Server. The former method is

    required if compilation and rebuilding of PHOENICS modules is to be performed. See

    section 1.1 or 1.2 (as appropriate) for further information.

The FLEXlm End Users Guide is available as an Adobe Acrobat file

    \phoenics\d_flexlm\enduser.pdf on the SERVER CD.

1.1 PHOENICS on each PC

This is required for recompilable PHOENICS and is optional for non-recompilable

    PHOENICS.

    ? One PC, designated by the user as a Server, will need to have two FLEXlm daemons

     running continuously. A copy of the FLEXlm licence file, and a batch file to start the

     daemons will also be on this Server.

    ? Each PC which is to run PHOENICS will have the complete PHOENICS directory

     structure installed. A copy of the FLEXLM licence file will also be on each PC, and will

     be identical to that on the Server.

Go to section 2.1 for instructions on this method of installation.

1.2 PHOENICS on the Server

This method is to be used for non-recompilable PHOENICS.

? One PC, designated by the user as a Server, will need to have two FLEXlm daemons

     running continuously. The complete PHOENICS directory structure and the FLEXlm

     licence file will also be on this Server.

? Each PC which is to run PHOENICS will have only two PHOENICS directories

     installed. The FLEXlm licence file will also be on each PC, and will be identical to that

     on the Server. The Server must be visible to each PC, and the disk drive letter (e.g. h:)

     of the Server hard disk as seen by each User PC will be used by PHOENICS when

     running on each PC.

     Go to section 2.2 for instructions on this method of installation.

2.1 Installing Recompilable PHOENICS on each PC

a) Install PHOENICS on each designated PC on the network

    ? Place delivery PHOENICS 3.5 CDROM in drive, and follow on-screen instructions

     If the Server is also to be used to run PHOENICS then it should be installed

     there in a similar manner

b) Install FLEXlm directory on the Server

    ? Place delivery SERVER CDROM in drive, and follow on-screen instructions

c) Modify FLEXlm licence file on the Server with the IP address

    ? Run program ' winipcfg ' on Server to obtain the IP address of the Server

    ? Replace the text 'this_host' on the SERVER line in \phoenics\d_flexlm\phoenics.lic

     with this IP address.

     The SERVER line will now look something like this (the user's IP address will be

     different)

     SERVER 192.168.1.155 ANY

    ? Copy this temporary phoenics licence file from the Server to \phoenics\d_allpro on

     the Users' PCs on which PHOENICS is to run

     This temporary licence file will allow use of PHOENICS for a short initial period

d) Start the FLEXlm daemons on the Server

    ? Run the batch file \phoenics\d_flexlm\start.bat

     These daemons control the licence management, e.g. how many Users are

     authorised, what program options are valid etc, and must always be running when

     PHOENICS is being used.

e) Run PHOENICS on the designated PCs

    ? Click on the PHOENICS-VR icon on the User PC desktop

2.2 Installing Non-recompilable PHOENICS on a Server

a) Install PHOENICS on the Server

    ? Place delivery PHOENICS 3.5 CDROM in drive, and follow on-screen instructions

b) Install minimum PHOENICS on each User PC

    ? Place delivery USER CDROM in drive, and follow on-screen instructions

    ? Edit the file \phoenics\d_allpro\config, and replace all occurrences of the test drive

     letter I: (which precede the string \phoenics) with the Server drive letter (e.g. h:)

    ? Edit the file 'phoenics\d_allpro\cham.ini' such that the same drive letter ( h in

     this example) is set as the POLIS drive, as follows

     [POLIS]

     drive = h

    ? Edit the file 'phoenics\d_priv1\vre.bat' and replace the single occurrence of the test

     drive letter I: with the Server drive letter (e.g. h:)

c) Modify FLEXlm licence file on the Server with the IP address

    ? Run program ' winipcfg ' on the Server to obtain the IP address of the Server

    ? Replace the text 'this_host' on the SERVER line in \phoenics\d_flexlm\phoenics.lic

     with this IP address.

     The SERVER line will now look something like this (the User's IPaddress will be

     different)

     SERVER 192.168.1.155 ANY

    ? Copy this temporary phoenics licence file phoenics.lic from the Server to

     \phoenics\d_allpro on the Users' PCs on which PHOENICS is to run

     This temporary licence file will allow use of PHOENICS for a short initial period

d) Start the FLEXlm daemons on the Server

    ? Run the batch file \phoenics\d_flexlm\start.bat

     These daemons control the licence management, e.g. how many Users are

     authorised, what program options are valid etc, and must always be running

     when PHOENICS is being used.

    e) Run PHOENICS on User PC

    ? Create a PHOENICS icon on the desktop, as in PHOENICS Documentation TR110

     Appendix B2, Troubleshooting. The target should be the satexe.exe program on the

     Server (e.g. h:\phoenics\d_satell\d_windf\satexe); it should start in a local directory

     such as \phoenics\d_priv1.

Obtaining a long-term FLEXlm Licence File for PHOENICS

After installation on the network PHOENICS can be run on any designated PC for a limited

    initial period as indicated in \phoenics\d_allpro\phoenics.lic. This is usually one month.

The user will need to obtain from CHAM a longer term licence tailored to the network Server.

    In order to provide this CHAM will need the HOSTID of the Server.

1) Obtain the HOSTID of the Server

    ? Run the program \phoenics\d_flexlm\lmhostid on the Server

    ? Send the full HOSTID displayed by this program, together with the IP address of the

     Server, on an Unlocking Request Form to bmz@cham.co.uk, with a request for a

     Network licence file.

     CHAM will then supply a new FLEXlm licence file 'phoenics.lic', which incorporates

     the HOSTID and IP address of the Server. The IP address in the licence file can

     subsequently be changed by the user, but the HOSTID value can not be modified.

2) Install FLEXlm Licence file

    ? Copy this PHOENICS licence file 'phoenics.lic' to directory \phoenics\d_flexlm on

     the Server, and to directory \phoenics\d_allpro on each Users' PC

Report this document

For any questions or suggestions please email
cust-service@docsford.com