Configuring IBM BPM endpoints to match your topology
Before you begin
- The commands must be run on the deployment manager node.
- If the deployment manager is stopped, use the wsadmin -conntype none option to run the commands in disconnected mode.
- If the deployment manager is running, you must connect with a user ID that has WebSphere Application Server configurator privileges. Do not use the wsadmin -conntype none option.
Start the wsadmin scripting client from the deployment_manager_profile/bin directory. The setBPMVirtualHost, setBPMDefaultVirtualHost, and setBPMEndpoint commands do not write to a log file, but the wsadmin scripting client always writes a profile_root/logs/wsadmin.traceout log file where you will find exception stack traces and other information.
About this task
It is important to identify the different entry points in your network, such as load balancers and web servers, for external and internal clients. For example, generally, the protocol, host name, and port number of the entry point server must be used in any generated links that are served to clients. Sometimes the endpoints can be defined as a static URL, but in more complex topologies it might be necessary to use a dynamic strategy, such as extracting the information from the header of the request.
In simple topologies, the defaults should work without any changes. Generally, a production environment requires some changes to the defaults. For example, if you have a web server for external clients, see Customizing IBM BPM to work with a web server.
More complex topologies and ones that include multiple deployment environments require more targeted configuration of specific objects.
Procedure
To configure the endpoints, complete the following actions: