The business rules manager is installed as an enterprise application for WebSphere Process Server, so that you can manage business rules during run time. You can install it using the administrative console or optionally, you can use a .jacl script for Windows, Linux, or iSeries.
Before you begin
Security role required:You must be logged in as administrator or configurator to install the business rules manager.
Steps for this task
- To install the business rules manager from the administrative console, select the Install business rules manager check box on the Business Rules Manager Configuration page.
- From within the administrative console, expand Servers and click Application Server.
- Click the name of your server.
- On the Configuration page, under Business Integration, expand Business Rules and click Business Rules Manager Configuration.
- Under General Properties, select the Install business rules manager check box.
- In the Context root field, either accept the default context root of br/webclient or type a custom context root for the business rules manager URL.
- Click OK.
- Optional: If you want to install the business rules manager manually using the command line (instead of using the administrative console), you must first make sure that WebSphere Process Server is started. Go to theWPS_HOME/bin directory open the shell or command prompt for your operating system and run the specific installation command for your operating system.
- For Windows, run: wsadmin.bat -f installBRManager.jacl [-s servername -n nodename | -cl clustername] -c cellname -r rootname -a applicationname.
- For Linux, run: ./wsadmin.sh -f ./installBRManager.jacl [-s servername -n nodename | -cl clustername] -c cellname -r rootname -a applicationname.
- For iSeries, run: wsadmin -f ./installBRManager.jacl [-s servername -n nodename | -cl clustername] -c cellname -r rootname -a applicationname.
where:
- servername
- The name of the application server.
The pair of arguments "-s servername" is required in the Network Deployment configuration if a cluster is not specified.
- nodename
- The name of the installation node.
The pair of arguments "-n nodename" is required in the Network Deployment configuration if a cluster is not specified.
- clustername
- The name of the cluster where you want to install the application.
The pair of arguments "-cl clustername" is required in the Network Deployment configuration if a server name and a node name are not specified.
Note: You must either specify the node and server or specify the cluster. Do not specify both.
- cellname
- The name of the installation cell.
The pair of arguments "-c cellname" is optional.
- rootname
- The name of the application root directory.
The pair of arguments "-r rootname" is optional. If missing, the default value of rootname is "br/webclient."
- applicationname
- The name of the application.
The pair of arguments "-a applicationname" is optional. If missing, the default value of applicationname is "BusinessRulesManager".
Note: If WebSphere Process Server is configured in a single-server environment, all of these pairs of arguments are optional. If WebSphere Process Server is configured for a Network Deployment environment, one of the following argument pairs is required:
- either -s servername and -n nodename
- or -cl clustername
The other argument pairs are optional.
Note: Missing arguments will take the following default values:
- "server1" = servername
- "br/webclient" = rootname
- "BusinessRulesManager" = applicationname
Last updated: Wed 06 Dec 2006 07:08:08
(c) Copyright IBM Corporation 2005, 2006.
This information center is powered by Eclipse technology (http://www.eclipse.org)