webMethods Integration Server Service Profiler (ISSPROF) v1.5

Full installation (continued):

1. Shutdown the Integration Server;
2. Edit the startup script;

   Important: For Integration Server v9.6 and above, the Service Profiler must be v1.4 or above.

   Save a copy of the file startup.shruntime.bat as startup.org.shruntime.org.bat, located in <wm_dir>/profiles/ISIS_<instance>/bin;

   Save a copy of the file(s) going to be edited, in the bin folder of profiles for your Integration Server instance:

   • Copy runtime.bat to runtime.org.bat
   • Copy service.bat to service.org.bat

   Important: Since v9.7 the startup.shbat shell script available from within the Integration Server instance file structure is being deprecated in favor of the startup script from within the profiles structure. This has already impact in some v9.x installations where some environment variables are no longer available. One of them is IS_DIR.

   To overcome that limitation we need to add a statement that sets the IS_DIR enviroment variable (what is being shown is just an example and you should use the path and instance name of your installation), at the point shown below with this style and as indicated.

   Edit the runtime.bat script file and costumize as indicated.

         ...
         :start
         rem =================================== Start ===================================
   
         Set IS_DIR=C:\SoftwareAG\IntegrationServer\instances\default
         Call "%IS_DIR%\serviceprofiler\bin\setenv.bat"
         ...
   

         #!/bin/sh
   
         if [ -z "$IS_DIR" ]; then
            IS_DIR="/opt/wm/v9-10_dev00/IntegrationServer/instances/default"
         fi
   
         DIRNAME=`dirname $0`
         LOGFILE=$DIRNAME/../logs/`basename $0`.out
         ...
   

   And also add the line...

         . "${IS_DIR}"/serviceprofiler/bin/setenv.shbat
   

         Call "%IS_DIR%\serviceprofiler\bin\setenv.bat"
   

   ... right before the structure that starts the Java in startup.sh, at the point shown below with this style and as indicated.

         ...
         . "${IS_DIR}"/serviceprofiler/bin/setenv.sh
   
         if [ "${USE_WRAPPER}" = "yes" ]; then
           if [ "$STARTUP_MODE" = "console" ]; then
             echo "Starting console mode using Tanuki Wrapper..."
             if [ "${BLOCKING_SCRIPT}" = "yes" ]; then
               ${WRAPPER_SCRIPT} console
             else
               nohup ${WRAPPER_SCRIPT} console > $LOGFILE 2>&1 &
             fi
           else
             echo "Checking is started..."
             ${WRAPPER_SCRIPT} status
   
             if [ "$?" -ne "0" ]; then
               echo "Starting daemon using Tanuki Wrapper..."
               ${WRAPPER_SCRIPT} start
             fi
           fi
         else
           echo "Starting as an application using Java because it is not set to use Tanuki Wrapper."
         ...
   

3. Integration Server running as Windows NT Service

   If the server is running as a Windows NT Service and to be able to set it up, the service.bat script needs to be edited and customized as indicated.

          ...
          :doConf
          set _WRAPPER_CONF="C:\SoftwareAG\profiles\IS_default\configuration\wrapper.conf"
   
          Set IS_DIR=C:\SoftwareAG\IntegrationServer\instances\default
          If "%1"=="-install"      Call "%IS_DIR%\serviceprofiler\bin\setenv.bat"
          If "%1"=="-installstart" Call "%IS_DIR%\serviceprofiler\bin\setenv.bat"
   
          :execCmd
          ...
   

   Important: If the Integration Server is already registered as a Windows NT Service you need to unregister it and register it again. The same is valid when uninstalling the tool.

4. Start the Integration Server;
5. Set the tool License Key.

   When the tool is first installed there is no License Key set and any attempt to perform an action will result in a License not set exception.

   Access the Service Profiler licensing page and set the License Key.

To use the Tanuki wrapper, the preparation scripts already create the necessary profile configuration settings and add them to the corresponding Integration Server intance custom_wrapper.conf. A copy of the file before the changes were made is saved with the name custom_wrapper.conf.beforeissprof.

Important: When installing webMethods updates (i.e., FIXes, Service Packs, etc.) the startup scripts may be overwritten thus disabling the Service Profiler startup. When this happens, just repeat all the script-editing steps.