Integration Server 10.15 | Integration Server Administrator's Guide | Running Multiple Integration Server Instances | Creating a New Integration Server Instance
 
Creating a New Integration Server Instance
 
Obtaining and Applying Updates from Update Manager
Use the create command to create a new Integration Server instance.
Before creating a new instance, review the information in Guidelines for Running Multiple Integration Server Instances on the Same Machine and About Creating a New Integration Server Instance.
*To create a new Integration Server instance
1. Navigate to the following directory:
Integration Server_directory \instances
2. Run the instance script as follows:
is_instance.bat/sh create
-Dinstance.name=instance_name
-Dadmin.password=Administrator_password
-Dadmin.changeOnLogin=change_password
-Dprimary.port=primary_port_number
-Dinstance.ip=default_bind_address
-Ddiagnostic.port=diagnostic_port_number
-Dsecure.port=secure_port_number
-Djmx.port=jmx_port_number
-Dlicense.file=license_file_location
-Dinstall.service=install_service
-Ddb.alias=database_alias_name
-Ddb.type=database_type
-Ddb.username=database_username
-Ddb.password=database_password
-Ddb.url=database_URL
-Dpackage.list=package_list
-Dsum.install.dir=SUM_installation_location
-Dsum.image.location=SUM_image_location
-Dsum.server=fix_server_URL
-Dsum.empower.user=empower_user
-Dsum.empower.password=empower_password
Where
Specify
instance_name
A unique name for the new instance.
Administrator_password
Optional. The password to use for the Administrator user. If you do not set the Administrator user password here, then the Administrator user password defaults to the value provided during installation of Integration Server.
change_password
Optional. Whether the Administrator user password must be changed upon successful log in to the new instance. Set to yes to require the password to be changed. Otherwise, set to no. If you do not specify a value for admin.changeOnLogin, the new instance defaults to the change password on log in value set during Integration Server installation. That is, if the person installing Integration Server selected the option requiring the Administrator user password be changed on initial successful log in, a new Integration Server instance will require that as well.
primary_port_number
Optional. A default HTTP port number for the new instance. The port number must be unique for each Integration Server instance. The default value is 5555.
default_bind_address
Optional. Default IP address to which to bind ports on this instance of Integration Server. Specify a bind address if your machine has multiple IP addresses and you want to use the same port number across different instances of Integration Server on the machine. In this case, each instance must specify a different bind address. If you do not specify a default bind address, the port listens to all network interfaces which prevents the same port number from being used on multiple instances.
Note:Integration Server uses the supplied default_bind_address value as the value of the watt.server.inetaddress configuration property.
diagnostic_port_number
Optional. A default diagnostic port number for the new instance. The port number must be unique for each Integration Server instance. The default value is 9999.
secure_port_number
Optional. A default HTTPS port number for the new instance. The port number must be unique for each Integration Server instance. The default value is 5543.
jmx_port_number
Optional. A default JMX port number for the new instance. The port number must be unique for each Integration Server instance. The default value is 8075.
license_file_location
Optional. The location of your Integration Server license file.
The script copies the license file from the specified location to IntegrationServer/instances/instance_name/config/licenseKey.xml file.
This parameter is optional; however, if a license file location is not specified, the Integration Server instance will shut down after 30 minutes.
Note:
If the location name contains spaces, you must surround the name of the location with quotation marks (” ”). For example:
-Dlicense.file=”license file location”
install_service
Optional. Whether to register the service for the instance. The default is false.
Note:
This option is valid only for Windows platforms.
database_alias_name
Optional. The alias name for the database. The default value for embedded database is Embedded Database Pool and JDBC_POOL_ALIAS for external database.
database_type
Optional. The type of database. Specify one of the following databases:
*sqlserver - Microsoft SQL Server
*oracle - Oracle
*db2 - DB2
These values are not case-sensitive. If this parameter is left unspecified, the new Integration Server instance uses the embedded IS internal database, which is the default.
database_username
Optional. User name to connect to the database.
database_password
Optional. Password of the database user.
database_URL
Optional. The connection URL for the database.
For example:
jdbc:wm:oracle://​<server>:<1521|port>;​serviceName=<value>[;<option>=<value>...]
package_list
Optional. A comma-separated list of packages to add to the server instance. For example, WmPRT,WmTN.
The packages that you specify must be part of the webMethods Integration Server package repository. Software AG Installer installs packages in the package repository, which is located under the Software AG_directory \IntegrationServer\packages directory.
Specify all to add all non-predefined packages in the webMethods Integration Server package repository located in the Integration Server_directory \packages directory. For a list of predefined packages, see Predefined Packages.
Note:
If you want the server instance to use components or services contained in other packages, you must add the packages to the Integration Server instance. For example, if you want the server instance to use webMethods Deployer, webMethods API Gateway, or webMethods Application Platform, you must add the WmDeployer, WmAPIGateway, or WmAppPlat packages respectively to the Integration Server instance.
SUM_installation_location
Optional. The absolute path to the Software AG Update Manager installation, specifically the path to the SAGUpdateManager directory. If you do not specify a value, the script looks for Update Manager in the current Integration Server installation directory.
SUM_image_location
Optional. Absolute path to the location of the Update Manager installation image. Update Manager can install fixes from an installation image. If you do not specify a value, the script looks for Update Manager itself, as opposed to an image, in the current Integration Server installation directory.
For more information about creating installation images, see the Using Software AG Update Manager documentation.
fix_server_URL
Optional. URL of the server from which to download fixes. If you do not specify a value, the script looks for a fix server URL in the Update Manager cache.
empower_user
Optional. User name for connecting Update Manager to Empower. If you do not supply a empower_user , the script looks in the Update Manager cached for credentials that Update Manager previously used to connect to Empower. For more information about connecting to Empower from Update Manager, see Using Software AG Update Manager.
empower_password
Optional. Password for connecting Update Manager to Empower. If you do not supply empower_password , the script uses the cached credentials which Update Manager previously used to connect to Empower. For more information about connecting to Empower from Update Manager, see Using Software AG Update Manager.
Note:
If you specify empower_user, you must also specify empower_password.
3. Optionally, add packages to the server instance after it is created. For instructions, see Updating Packages on a Server Instance.
4. Start the Integration Server instance by running the startup.bat/sh file located in the Software AG_directory \profiles\IS_instance_name\bin directory.
Note:
The startup.bat/sh and shutdown.bat/sh scripts contained in the Integration Server_directory \instances\instance_name\bin directory are deprecated. Software AG recommends the use of the scripts contained in the Software AG_directory \profiles\IS_instance_name\bin directory. If you will manage Integration Server through Command Central, you must use the scripts located in the Software AG_directory \profiles\IS_instance_name\bin directory.
Note:
If you added the package WmAppPlat, which is for webMethods Application Platform, the new Integration Server instance includes a configured instance of Tomcat. This Tomcat instance uses ports 8072 and 8074 as the default HTTP and HTTPS ports, respectively. These default ports conflict with the ports used by Tomcat on the default instance of Integration Server. You must use Command Central to change the default HTTP and HTTPS port numbers for Tomcat on the new instance of Integration Server. For more information about creating an Integration Server instance with webMethods Application Platform, see the webMethods Application Platform User’s Guide.