Database Reference
In-Depth Information
•
Change the
ADCServerName
and
ADCServerPort
properties in the
BAMServerConfig.xml
to the correct values of the Active Data Cache
Server
•
In
BAMWebConfig.xml
, the
ServerName
and
ServerPort
need to be
changed to point to the actual BAM web server host and port (or the load
balancer)
Using ICommand to import/export BAM data
objects
Oracle BAM comes with a command-line utility to manage BAM artifacts and
data models by interacting with the BAM Active Data Cache. In this section,
you will learn how to use ICommand to export BAM data objects and their con-
tents, which can then be imported into another environment. This is very handy
in scenarios where you want to migrate data objects from one BAM instance to
another (for example, test environment to production). Before running the ICom-
mand utility, ensure that the
JAVA\HOME
environment variable is pointing to a
valid JDK home directory.
Configuring ICommand properties
BAM ICommand uses BAM server configuration details in
BAMICommandCon-
fig.xml
located in the
$MW_HOME/Oracle_SOA1/bam/config
directory for
executing the export/import tasks. To configure ICommand, you need to modify
the following two properties in
BAMICommandConfig.xml:
•
ADCServerName:
This is the BAM server hostname. You can use localhost
as the server name if ICommand is executed on the same host as the BAM
server.
•
ADCServerPort:
This is the BAM server listening port. By default, it is
9001
. If you have changed the listening port of the BAM server, this property
needs to be updated accordingly.
