Configuring Integration Server and My webMethods Server for Business Console

Administering and Monitoring Business Processes : Working with webMethods Business Console : Administering Business Console : Configuring Integration Server and My webMethods Server for Business Console

Only users with administrator privileges can specify the Integration Server and Task Engine for Business Console.

Specify the values for the following fields in the Administer Business Console menu option in the administration menu:

Field

Specify...

Integration Server URL

URL of the Integration Server that Business Console must connect to. For example, http://localhost:5555.

Make sure that Process Engine is configured in the Integration Server.

Note:

In the URL, if you specify a machine name or IP address, make sure you configure the remote My webMethods Server to allow access to Business Console. See the instructions in Configure a Remote My webMethods Server to Allow Access to Business Console .

Task Engine URL

URL of the Task Engine that Business Console must connect to. For example, http://localhost:8585.

Make sure you have configured following with the Task Engine:

My webMethods Server

My webMethods

Monitor

Note:

In the URL, if you specify the machine name or IP address, make sure you configure the remote My webMethods Server to allow access to Business Console. See the instructions in Configure a Remote My webMethods Server to Allow Access to Business Console .

Configure a Remote My webMethods Server to Allow Access to Business Console

If you want to connect Business Console to a remote My webMethods Server, configure the remote My webMethods Server to allow access to Business Console as shown below:

1. In the remote My webMethods Server installation, open the MWS\server\default\deploy\portal.war\WEB-INF\web.xml file for edit. The Cross-origin filter contains:

<filter>
<filter-name>cross-origin</filter-name>
<filter-class>org.eclipse.jetty.servlets.CrossOriginFilter</filter- class>
</filter>

<filter-mapping>
<filter-name>cross-origin</filter-name>
<url-pattern>/cometd/*</url-pattern>
</filter-mapping>

2. Change the Cross-origin filter to:

<filter>
  <filter-name>cross-origin</filter-name>
  <filter-class>org.eclipse.jetty.servlets.CrossOriginFilter</filter-class>

  <init-param>
    <param-name>allowedMethods</param-name>
    <param-value>GET,POST,HEAD,OPTIONS</param-value>
  </init-param>
  <init-param>
    <param-name>allowCredentials</param-name>
    <param-value>true</param-value>
  </init-param>
  <init-param>
    <param-name>chainPreflight</param-name>
    <param-value>false</param-value>
  </init-param>
</filter>
<filter-mapping>
  <filter-name>cross-origin</filter-name>
  <url-pattern>/cometd/*</url-pattern>
  <url-pattern>/rest/*</url-pattern>
</filter-mapping>

Contact Support | Community | Feedback