Creating a New Integration Server Instance
Use the create command to create 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
-Dprimary.port=primary_port_number
-Ddiagnostic.port=diagnostic_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
Where... | Specify... |
instance_name | A unique name for the new instance. |
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. |
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. |
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. |
|
db.alias | Optional. The alias name for the database. The default value is JDBC_POOL_ALIAS. |
db.type | The type of database used by the new server instance. Specify one of the following databases:  sqlserver - Microsoft SQL Server oracle - Oracle db2 - DB2 These values are not case-sensitive. The default is the embedded IS internal database. |
db.username | The user name assigned to the Integration Server database. |
db.password | The password of the Integration Server database user. |
db.url | The connection URL for the database. |
package_list | Optional. A comma-separated list of packages to add to the server instance. For example, WmPRT,WmTN. Note: | This option does not accept white-space characters (or blank spaces). |
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 Mediator, or webMethods Application Platform, you must add the WmDeployer, WmMediator, or WmAppPlat packages respectively to the Integration 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 |
Example: when executing on Command Central:
To create the new instance for an installed
Integration Server with instance name “is-instance2”, diagnostic port “8083”, and primary port “8081” in the installation with alias name “productionNode2”:
sagcc create instances productionNode2 integrationServer
instance.name=is-instance2 diagnostic.port=8083
primary.port=8081
db.alias=sql_server db.type=SQL
db.username=sa db.password=password@1234
db.url="jdbc:wm:sqlserver://10.60.72.87:1433;databaseName=SQL_DB"
Examples: when executing on Platform Manager
To create the new instance for an installed
Integration Server with instance name “is-instance2”, diagnostic port “8083”, JMX port “10058”, and primary port “8081”:
sagcc create instances integrationServer instance.name=is-instance2
diagnostic.port=8083 jmx.port=10058 primary.port=8081
db.alias=sql_server db.type=SQL
db.username=sa db.password=password@1234
db.url="jdbc:wm:sqlserver://10.60.72.87:1433;databaseName=SQL_DB"
To create the new instance for an installed
Integration Server using the instance data in the instance-settings.properties file, located it in the current directory:
sagcc create instances integrationServer -i instance-settings.properties
To create the new instance for an installed
Integration Server using the instance data in the instance.settings.xml file, located in the current directory:
sagcc create instances integrationServer -i instance-settings.xml
