Introduction

EMu is designed to allow multiple installations to coexist. Each installation is placed in a directory within the user emu's home directory. The name of this directory typically reflects the client system being installed. The client name may be any name, thus allowing test and production environments to be set up for the same system. Typically the client name is an acronym for the client organisation. In the notes below clientname refers to the name of the client directory for the current installation.

The term ~emu is used to refer to the user emu's home directory. This is normally /dev/fs/C/home/emu.

Requirements

• Microsoft Windows Services for UNIX, version 3.5.
• Texpress, version 8.1.003 or greater.
• TexAPI, version 3.1.009 or greater.
• EMu Server version 3.2.01 or greater.

Installation Notes (EMu Server - emu)

1. Log in to the Windows machine as local user emu
2. Start a Korn Shell with Start>Programs>Windows Services for UNIX>Korn Shell
3. Enter cd  ~emu
4. The install bundle must be unarchived into a new temporay directory.
   It is recommended to use a new temporary directory named ~emu/clientname/install.
   Enter mkdir  -p  clientname/install
5. Enter cd  clientname/install
6. Obtain the appropriate EMu server version bundle via the KE EMu Server hyperlink above.
   Save the release bundle file in the ~emu/clientname/install temporary directory.
7. Extract the client release by using the name of the actual release file.
   Enter sh  emu-clientname-yymmddv.sh
   The EMu release will be extracted.
8. Enter .  ./.profile
9. Enter bin/emuinstall  clientname. The EMu installation script will commence.
   As part of the installation you will be prompted to enter the emu password.
   The password is required for the cron maintenance task scheduler to function correctly.
10. Enter cd  ~emu/clientname
11. Enter cp  .profile.parent  ../.profile
12. Enter cd  ..
13. Enter vi  .profile-local
14. Add a single line client clientname to the file and save it. If a default client is already registered then you may leave the existing value.
15. Enter .  ./.profile
16. Enter client  clientname
17. Enter cd  etc
18. View the config.sample file.
    If  you wish to alter some of these settings to suit the client then:
    Enter cp  config.sample  config
    Enter vi  config
    edit as appropriate, then save the file.
    Be careful to set EMUSMTPSERVER to the hostname of your mail server machine.
19. Enter cd  ..
20. Enter emubldlinks
21. Enter emulutsrebuild
22. Removal of the the temporary directory (and its contents) is recommended:
    Enter \rm  -fr  install

In order to allow easier upgrades of Texpress (without having to update the etc/opts file) all Texpress options are now set in the client specific .profile-local file. When installing EMu 3.1 you will have to add all Texpress options required for the installation. In particular the dateorder, dateformat, timeformat, latitudeformat, longitudeformat, tmppath and loadmemory settings should be examined. Please see Texpress options for a list of acceptable values.

1. Enter vi  .profile-local and add the KE Texpress options to the file. An example file is:
   TEXPRESSOPTS="${TEXPRESSOPTS} dateorder=mdy dateformat='dd MMM yyyy'"
   export TEXPRESSOPTS
2. Enter client  clientname
3. Any other client specific setting can be set at this time (eg shell specific settings, etc).
4. Enter exit to close the Korn Shell window.
5. Log out.

Installation Notes (EMu Server - Administrator)

1. Log in as Administrator.
2. Start a Korn Shell with Start>Programs>Windows Services for UNIX>Korn Shell.
3. Enter vi  /etc/services
4. Add new services to the end of the file and save the file.
   Each line must be terminated with a CTRL+M character so that Windows programs interpret the file correctly.
   To enter a CTRL+M in vi type CTRL+V then CTRL+M.
   emu          20000/tcp^M
   emutrain     20001/tcp^M
   emutest      20002/tcp^M
   emuweb       30000/tcp^M
   emuwebtrain  30001/tcp^M
   emuwebtest   30002/tcp^M
   You should also add client specific services.
   To determine the port and webport required please view the EMu Ports document.
   emuclientname       port/tcp^M        (replace port with port number)
   emuwebclientname    webport/tcp^M     (replace webport with port number)
5. Enter vi  /etc/inetd.conf
6. Add the following line to the end of the file (you must expand [emu]):
   emuclientname stream tcp nowait NULL /dev/fs/C/home/emu/clientname/bin/emurun emurun texserver -a[emu] -i -L -t60
   If you also want the emu service to connect to your emuclientname then add the line:
   emu stream tcp nowait NULL /dev/fs/C/home/emu/clientname/bin/emurun emurun texserver -a[emu] -i -L -t60 
7. Save the file. You will need to restart inetd for the changes to take effect.
8. Enter ps  -ef  |  grep  inetd to determine the process id number pid for the inetd process.
9. Enter kill  -HUP  pid.
10. Enter cd  /etc/rc2.d
11. Enter vi  S99emu and add the following lines to the file:
    #!/bin/sh
    #
    # KE EMu startup
    #
    PATH=/bin:/usr/contrib/bin
    case $1 in
            start)
                    /dev/fs/C/home/emu/clientname/bin/emuboot
                    ;;
            stop)
                    ;;
            *)
                    echo "usage: $0 start|stop"
                    ;;
            esac
            exit 0
12. Save the file.
13. Enter chmod  755  S99emu
14. Enter ./S99emu  start
15. Enter exit to close the Korn Shell window.
16. In order to test the startup script it is recommended that you reboot the server machine and confirm that all EMu services start correctly.
    Output from scripts run when booting is found in /var/adm/log/init.log.
    Error messages are placed in /var/adm/log/messages.