You must configure the development environment before you use IBM® Business Automation
Workflow to create and deploy case solutions. You use the
development environment to create, modify, and test solutions before you move them into a production
environment. You can use the command line to configure the development environment.
About this task
Configuring the development domain includes configuring Case Builder and Case Client. You must
create a profile for each development environment instance that you are configuring.
Procedure
To configure the development environment:
-
Run the BPMConfig command to create the profiles for your development
environment.
If you have already created the dmgr and node profiles for your development environment, skip
to the next step.
-
Change the current directory to the
dmgr_profile_root/CaseManagement/DE_name/profiles/ICM_dev
directory.
-
Referring to Development environment tasks and files, edit the property values in the configuration XML files
that you generated:
-
Use a text editor or XML editor to open one of the configuration XML files that you
generated.
-
Replace each occurrence of
****INSERT VALUE****
with a value that is
appropriate for your site.
To change the default value to a blank value, replace
<value>****INSERT
VALUE****</value>
with
<value />
. See the descriptions in the
file for more information.
-
Replace empty values that have the format
<value />
with a value that is
appropriate for your site.
Use the format
<value>my_value</value>.
-
Verify that the default values for the remaining properties are correct for your site.
-
Verify that the task is enabled for each required task. Set the enabled
attribute value in the <configuration> element to true in any
configuration XML file that you edit if you want to run the configuration task.
When a task is disabled, the execute command skips the task. For example,
the registerexternaldataurl.xml file has the enabled
attribute value in the <configuration> element set to false by default,
and the task will be skipped.
-
Save your edits and close the XML file.
-
Repeat as needed until you edit all the required files.
Important: You must provide values for all of the entries in the
websphereapplicationserver.xml file, the
contentengineserver.xml file, and the
contentnavigatorserver.xml file before you can run any of the tasks.
-
If you are running Linux on POWER Little Endian (LE), modify the
install_root/CaseManagement/configure/comfigmgr.ini file to
point to JDK 1.8 by making the following change:
-vm
/opt/install_root/java_1.8_64/bin
- Optional:
Add encrypted passwords to the XML files by running the storePasswords
command for the profile.
Tip: If you do not add passwords to the XML files, you are prompted for the passwords
when you run the task for each file.
For example, the following command stores all the passwords in the profile named
myprofile1:
configmgr_cl storepasswords -profile myprofile1
-
Change to the install_root/CaseManagement/configure
directory and run all of the tasks in the development profile by using the following command:
configmgr_cl execute -profile myprofile
[-silent] [-force]
For more information about the syntax, see
execute command.
Note: On AIX, if IBM SDK is updated to version 8.0.6.25 or later, the Eclipse launcher might be
unable to load libjgskit.so
and libjgsk8iccs_64.so
. You must
export the LIBPATH variable before you run the configmgr_cl
command. To export LIBPATH, use the following command, where
<baw_install_root> is your Business Automation Workflow installation path:
LIBPATH=$LIBPATH:<baw_install_root>/java/jre/lib/ppc64:<baw_install_root>/java/jre/lib/icc
.
- You can check the task status by running the checkStatus command. For
example
-
Restart the application server.
What to do next
You must add at least one user to the default project area. Users cannot log into Case Builder until they are added to a project area.