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.

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

Verifying that user_setenv.sh calls repra_env.sh (EAServer)

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

Verify that user_setenv.sh contains this 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 (WebLogic)

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

Locate the script file that starts the server. Typically, the file is in the domain directory and called startWebLogic.sh.

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

To modify the file to call repra_env.sh, open the file with any text editor. For example:

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

Then add the new line that calls repra_env.sh just above the line that starts the server. For example, before your edits the text reads:

$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, the text includes the lines in boldface:

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

Starting EAServer

From the command line , enter:
```
cd $JAGUAR/bin
serverstart.sh -jdk14
```
The server is started when “Accepting connections” appears 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
- Forced 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.
To start the server, 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
```
Execute WLSStart.sh from the RepConnector directory to finish the WebLogic installation process.

See the WebLogic documentation for more information.