Post-installation tasks for UNIX

RepConnector requires specific environment variable settings to run with your application server and target messaging systems. These environment variables are set in the repra_env.sh file, located as follows:

For EAServer: $JAGUAR/repra/bin
For WebLogic: $BEA_HOME/repra/bin

Most environment variables are already set correctly for your environment in repra_env.sh. However, you must verify that the environment variable for your messaging system is set properly. You must also verify that repra_env.sh is called by the batch file that starts your application server.

Whenever you modify repra_env.sh, you must restart your application server for the new values to take effect.

If you are using WebLogic, verify that the BEA_HOME environment variable is set to the path of your WebLogic installation.

Use the following procedures to set up and verify your RepConnector environment on UNIX.

Verifying that user_setenv.sh calls repra_env.sh for EAServer

Go to the EAServer/bin.
Edit user_setenv.sh using any command line editor.

Verify that user_setenv.sh contains the following line:

if [ -f $JAGUAR/repra/bin/repra_env.sh ]
   then
   . $JAGUAR/repra/bin/repra_env.sh
fi

Modifying the server-starting batch file to call repra_env.sh for WebLogic

See your BEA documentation for the details about the WebLogic installation.

Locate the script file that you use to start your server. Typically, the file is in your domain directory and called startWebLogic.sh.

For example, the file could be: /opt/BEA/user_projects/domains/mydomain/startWebLogic.sh

Modify the file to call repra_env.sh, and apply repra_env.sh environment variable settings to the server environment.

Open the file with any text editor. For example:

vi /opt/BEA/user_projects/domains/mydomain/startWebLogic.sh

Add the new line that calls repra_env.sh just above the line that starts the server. For example:

Before your edits:

$JAVA_HOME/bin/java $JAVA_VM $MEM_ARGS \
$JAVA_OPTIONS -Dweblogic.Name=$SERVER_NAME \
-Dweblogic.ProductionModeEnabled=$PRODUCTION_MODE \
-Djava.security.policy="$WL_HOME/server/lib/weblogic.policy" \
weblogic.Server

After your edits (see the lines in bold):

if [ -f /opt/BEA/repra/bin/repra_env.sh ]
then
            . /opt/BEA/repra/bin/repra_env.sh
fi

$JAVA_HOME/bin/java $JAVA_VM $MEM_ARGS \
$JAVA_OPTIONS -Dweblogic.Name=$SERVER_NAME \
-Dweblogic.ProductionModeEnabled=$PRODUCTION_MODE \
-Djava.security.policy="$WL_HOME/server/lib/weblogic.policy" \
weblogic.Server

Restarting EAServer

- From the command line:
  1. To shut down EAServer, enter:
```
$JAGUAR/bin/jagtool -h <server's hostname> -n <servers port number> 
                     -u <admin user> -p <admin password> shutdown
```
  2. To start EAServer, enter:
```
cd $JAGUAR/bin
serverstart.sh -jdk14
```
- From Sybase Central
  1. To shut down EAServer, in Jaguar Manager, right-click the server in the Servers folder.
  2. Select Shutdown.
    
    The server shuts down.
  3. To start the server, from the command line, enter:
```
cd $JAGUAR/bin
serverstart.sh -jdk14
```

The server is started when the Jaguar CTS console appears and shows “Accepting connections” on the last line.

Restarting WebLogic

Use your Web browser to log in to the WebLogic Server console. For example:
```
http://localhost:7001/console
```
From the console, log in to your WebLogic server using the user name and password of the admin user.
Go to <your domain name>/Servers/<your server name>.
Right-click the server, and from the drop-down list, select Start/Stop This Server.
On the next Web page, choose one of the shutdown options:
- Graceful Shutdown of This Server
- Force Shutdown of This Server
See the WebLogic Administrator's Guide from BEA for detailed information about shutdown options.
Click OK to shut down the server.
Locate the server-starting batch file that you modified in the previous procedure to apply to your environment.
To start the server, do one of the following:
- Double-click the server-starting batch file, or
- From the command line, enter:
```
cd <the domain directory>
startWebLogic.sh
```
Verify the server's running status from the command line console by checking for the following message:
```
Server started in RUNNING mode
```
If the server is in RUNNING mode, connect to the server from your browser by entering:
```
http://<hostname>:<serverport>/console
```
For example:
```
http://localhost:7001/console
```

See the WebLogic documentation for more information.