Installing and deploying RepConnector in GUI mode

1. Insert the RepConnector CD into your CD drive.

2. Mount the CD.

3. Change to the directory where you have mounted the CD, and execute setupRC.bin (setupRC.exe on Windows) to start installation.

To install either the RepConnector runtime component or RepConnector Manager:

To install the RepConnector runtime component using InstallShield:

1. Enter or browse for the name of the directory where the selected application server is installed.

   For example, if you are installing RepConnector with EAServer, the default location is:

   • On Windows, %SYBASE%\EAServer

   • On UNIX, $SYBASE/EAServer

   Click Next.

2. If you are installing on BEA WebLogic Server, enter the WebLogic information:

   • Domain name – your WebLogic domain name.

   • Server name – your WebLogic server name.

   • Hostname – your machine name.

   • Port number – your WebLogic port number.

   • User name – your WebLogic user name.

   • Password – your WebLogic user password.

3. InstallShield tries to connect to the application server by sending a ping. If the ping is successful, the installation proceeds; if it is not, you see:

   Ping to the server failed. Verify that the server is
   running, and that you have entered valid information
   

   To troubleshoot the error:

   • Verify that the server is running and ready to accept connections.

   • If the server is running, verify that the information you entered in the previous step (step 2, page 9) is correct. See your system administrator if you cannot verify this information.

     If the server is not running, restart it.

   • If the server is running, the information in the InstallShield wizard is correct, and there is no other apparent reason for the failure, ask your Sybase representative to call Sybase Technical Support.

4. In the preview window, verify the size of the installation. If the installation is larger than the space you have available, see your system administrator to reassess the requirements.

5. The RepConnector runtime component is installed, then deploys to the application server.

   If you have an existing RepConnector installation, InstallShield asks if you want to overwrite that installation. Click Yes to overwrite, or cancel.

6. The Sybase Software Asset Management (SySAM) License Server window allows you to designate where RepConnector will find its licenses. Specify whether the licenses are obtained from a license server (a served license) or not (an unserved license).

   For information about served and unserved licenses, and about choosing the best license server for your environment, see Chapter 2, “Administering License Servers” in the Sybase Software Asset Management Users Guide.

   If you click Yes, you must know the host name of the machine where the license manager is running, and the port number if you have used a non-default port number.

   If you click No, you will be using unserved licenses. Download and install the license file.

7. Next, specify whether to configure your server for e-mail notification. When configuration is enabled, designated users receive information about license management events requiring attention.

   Provide the following information:

   • SMTP server host number

   • SMTP server port number

   • E-mail return address

   • Recipient e-mail addresses

   • Message severity that triggers e-mail messages

8. Select Next to complete the installation.

start-server.sh -arch64

1. Stop the BEA WebLogic Server.

2. Modify the startWebLogic.sh start-up script that resides in the domain’s bin directory to check for repra_env.sh and call it if it exists. Make this change after the setDomainEnv.sh call.

   • On AIX, Linux, and Solaris, this is the portion of the startWebLogic.sh start-up script that you need to modify:

     # Call setDomainEnv here.DOMAIN_HOME=" BEA_installation_directory/bea10/user_projects/domains/mydomain"
     . ${DOMAIN_HOME}/bin/setDomainEnv.sh $*
     if [ -f /BEA_installation_directory/bea10/repra/bin/repra_env.sh ]
     then
           . /BEA_installation_directory/bea10/repra/bin/repra_env.sh
     fi
     

   • On HP Itanium, this is the portion of the startWebLogic.sh start-up script you need to modify to check for repra_env.sh and call it if it exists, and to start Weblogic in 64-bit mode:

     # Call setDomainEnv here.DOMAIN_HOME=" BEA_installation_directory/bea10/user_projects/domains/mydomain"
     . ${DOMAIN_HOME}/bin/setDomainEnv.sh $*
     

     JAVA_OPTIONS=”-d64”
     if [ -f /BEA_installation_directory/bea10/repra/bin/repra_env.sh ]
     then
           . /BEA_installation_directory/bea10/repra/bin/repra_env.sh
     fi
     

   BEA_installation_directory is the path to your BEA installation directory.

3. Start the BEA WebLogic Server.

4. Run the WLSStart.sh file under the RepConnector home directory.

1. Stop the BEA WebLogic Server.

2. Modify the startWebLogic.cmd start-up script to check for repra_env.bat and call it if it exists. Make this change after the setDomainEnv.cmd call.

   The portion of the startWebLogic.cmd start-up script that you need to modify:

   @REM Call setDomainEnv here.
   set
   DOMAIN_HOME=BEA_installation_directory\bea10\user_projects\domains\
   mydomain
   for %%i in ("%DOMAIN_HOME%") do set DOMAIN_HOME=%%~fsi
   call "%DOMAIN_HOME%\bin\setDomainEnv.cmd" %*
   if exist BEA_installation_directory\BEA10\repra\bin\repra_env.bat CALL
   BEA_installation_directory\BEA10\repra\bin\repra_env.bat
   

   BEA_installation_directory is the path to your BEA installation directory.

3. Start the BEA WebLogic Server.

4. Run the WLSStart.bat file, which is located in the RepConnector home directory.