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.bat file. The location for repra_env.bat is:
For EAServer, %JAGUAR%\repra\bin, where %JAGUAR% is the location of the EAServer installation.
For WebLogic, %BEA_HOME%\repra\bin, where %BEA_HOME% is the location of the WebLogic Server installation.
Most environment variables are already set correctly for your environment in repra_env.bat. However, you must also verify that the environment variable for your messaging system is set properly and that repra_env.bat is called by the batch file that starts your application server.
Whenever you modify repra_env.bat,
you must restart your application server for the new values to take
effect.
Use the following procedures to set up and verify your RepConnector environment on Windows.
If you are using WebLogic, verify that the BEA_HOME environment variable is set to the path of your WebLogic installation.
Verifying that user_setenv.bat calls repra_env.bat for
EAServer
Go to EAServer\bin.
Right-click user_setenv.bat and select Edit.
Verify that user_setenv.bat contains the following line:
if exist "%JAGUAR%\repra\bin\repra_env.bat" CALL "%JAGUAR%\repra\bin\repra_env.bat"
Modifying the server-starting batch file to call repra_env.bat for WebLogic
See your BEA documentation for the details about the WebLogic installation.
Locate the batch file that you use to start your server. Typically, the file is in your domain directory and is called startWebLogic.cmd.
For example, the file could be: C:\BEA\user_projects\domains\mydomain\startWebLogic.cmd
Modify the file to call repra_env.bat, and apply repra_env.bat environment variable settings to the server environment. Add the new line 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 exist C:\BEA\repra\bin\repra_env.bat CALL C:\BEA\repra\bin\repra_env.bat %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
You can restart EAServer at the command line or from Sybase Central, using Jaguar Manager.
From the command line:
To shut down EAServer, enter:
%JAGUAR%\bin\jagtool -h <server's hostname> -n <servers port number> -u <admin user> -p <admin password> shutdown
To start EAServer, enter:
cd %JAGUAR%\bin serverstart.bat -jdk14
From Sybase Central:
To shut down EAServer, in Jaguar Manager, right-click the server in the Servers folder.
Select Shutdown.
The server shuts down.
To start the server, select Start | Programs | Sybase | EAServer 5.2 | Jaguar Server (jdk1.4).
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:
Select Start | All Programs | BEA WebLogic Platform 8.1 | User Projects | mydomain | Start Server
You can start the WebLogic server from the Start menu
only if you have added the shortcut to the Windows system registry
when you created the server with the WebLogic Configuration wizard.
See the WebLogic documentation for more information.
Double-click the server-starting batch file.
From the command line, enter:
cd <the domain directory> startWebLogic
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, enter:
http://localhost:7001/console
