Configuring Integration Server for Application Platform Projects
Use the following procedure to configure an Integration Server for your Application Platform projects.
Important: | Always stop the server before changing its configurations. Otherwise, unpredictable results may occur. |
To configure an Integration Server for an Application Platform project
1. In Designer, go to the Servers view and double-click the Integration Server you want to configure.
2. In the General Information section, specify values in the following fields:
In this field... | Specify... |
Server name | The name of the Integration Server, to which you publish projects. Default: webMethods Integration Server at host_name . |
Host name | The host name or address of the Integration Server, to which you publish projects. Do not change the default value. Integration Server does not support remote hosts. Default: localhost. |
3. Select a Runtime Environment.
Note: | The runtime environment includes an absolute directory path to the Application Platform installation, together with the relative paths to the platform bundles that represent the server libraries available in your project’s classpath. Designer uses this absolute path to locate the server profile when you attempt to start or stop the server. |
4. To edit the settings used when Designer executes operating system scripts that start or stop the server, click the Open Launch Configuration link.
5. After you complete the launch configuration, click OK.
6. In the Publishing section, select one of the following publishing settings:
Select this option... | To... |
Never publish automatically | Default. If you select this option, you must publish your project to the server manually. |
Automatically publish when resources change | If you select this option, your projects will be published automatically with a predefined time interval, in seconds, every time you update a project resource. You can configure the time interval of this setting. Default: 15 Note: | This option requires a lot of resources. |
|
Automatically publish when resources change | If you select this option, your projects will be published automatically after any project build event (for example clean, full, or incremental project build). Note: | This option requires a lot of resources. |
|
7. In the Server Properties section, specify values in the following fields:
For this setting... | Specify... |
Instance name for Integration Server | This field matches the instance name of Integration Server. Default: default |
Server Port | The HTTP port for the configured Integration Server. This port is used to verify the server startup sequence. Based on the port number you configure here, Designer uses the corresponding default user credentials to connect to Integration Server. Important: | If you change the user credentials in Integration Server, you must also update them in Designer. |
Default: 5555 |
Server Debug Port | The Java Platform Debugger Architecture (JPDA) debugger port configured for the JVM that Integration Server uses. The port value is sent to the startup scripts when Integration Server is started by Designer. During the server startup sequence if Designer cannot connect to the configured debugger port, the server still starts. However, any breakpoints will be ignored. For more information about JPDA, see the Oracle documentation. Default: 9191 |
Server JMX RMI Port | The Java Management Extensions Remote Method Invocation port used to execute a service for publishing bundles to the OSGi container. This port number is configured in Integration Server in a property file, located in the Software AG_directory \profiles\Instance_Name_for_Integration_Server\configuration\com.softwareag.platform.config.propsloader directory. Note: | If the port number is in use while installing Application Platform, the port number may change in the server configuration. If you are uncertain of the server state, use an operating system utility to see if the JMX port is in LISTEN mode. |
Note: | The default value matches JMX RMI port value, configured in Integration Server. |
Default: 8075 |
Server Connection Mode | Select an option for synchronizing the Servers view with the state of the external servers when you start Designer, or when a server is stopped or started outside of Designer. This list box has the following options:  Debug - Default. If you select Debug, Designer will automatically start debugging the servers in the Servers view. For example, if you restart Designer, the server instance in the Servers view will automatically start debugging. No Action - If you select No Action, Designer will not synchronize the state of the Servers view with the server. If Designer is started and a server is running, its Servers view will indicate the server is stopped. In this case you must execute the Start or Debug action in the Servers view. Also, if the server status changes while Designer is still running, the change will not be indicated in Designer. Run - If you select Run, Designer will automatically set the server status to started and you will not be able to debug applications remotely, while Designer is connected to the server. Note: | Since the server states are synchronized with a polling mechanism, there may be a short delay when the Servers view is updated. |
|
8. In the Timeouts section, specify values in the following fields:
In this field... | Specify... |
Start | Configure how long Designer should wait for the server to start before assuming failure. If the timeout is exceeded, you will see an error message in Designer. For more information, see . The default Start value is 300 seconds. |
Stop | Configure how long Designer should wait for the server to stop before assuming failure. If the timeout is exceeded, you will see an error message in Designer. For more information, see . The default Stop value is 60 seconds. |
Related Topics
