After you install the proxy and service execution components
on the proxy computer, you must configure the proxy to run services.
Location of proxy product options file
Use
the proxy product options file to set the proxy configuration properties.
The proxy product options file is located at
proxy_folder/eclipse.ini,
where
proxy_folder is the
folder to which the proxy was installed. The default proxy folder
depends on the operating system and on the user who installed the
proxy.
- Default proxy folder on Microsoft Windows computers:
- 32-bit: C:\Program Files\IBM Optim\proxy\
- 64-bit: C:\Program Files (x86)\IBM Optim\proxy\
- Default proxy folder on Linux or UNIX computers:
- Proxy installed by superuser: /opt/IBM/Optim/proxy/
- Proxy installed by user other than superuser: /home/username/IBM/Optim/proxy/,
where username is the name
of the user who installed the proxy
Configuring the proxy to use the executor
If you want to use the proxy to run services with the executor,
install the executor on the same computer as the proxy.
After
you install the executor, open the
executor_folder/eclipse.ini file
and look for the following line, where
executor_folder is
the folder of the executor. If this line exists, set the line to the
correct executor folder. You must always change this line if you install
the executor on a computer with a 64-bit version of Windows. If this line does not exist, add
the line to the file with the correct executor folder.
-Dcom.ibm.nex.executor.location=executor_folder
The
default executor folder depends on the operating system and on the
user who installed the executor.
- Default executor folder on Windows computers:
- 32-bit: C:\Program Files\IBM Optim\executor
- 64-bit: C:\Program Files (x86)\IBM Optim\executor
- Default executor folder on Linux or UNIX computers:
- Executor installed by superuser: /opt/IBM/Optim/executor
- Executor installed by user other than superuser: /home/username/IBM/Optim/executor,
where username is the name
of the user who installed the executor
Configuring the proxy to use the Optim pr0cmnd program
You can use
the proxy to run services with the Optim™ pr0cmnd
program as your service execution component. You must first install
and configure Optim on the
same computer as the proxy so that the pr0cmnd program is on the proxy
computer. You must also install on the proxy computer the database
client libraries for any relational database management systems that
the services use. The proxy computer must be able to access a database
that can be used to store the Optim Directory.
Use Optim to run at least one
service by itself to verify that the pr0cmnd program is configured
properly and ready to run services.
When you run a service
that uses the pr0cmnd command, the proxy uses the version of pr0cmnd
in the following folder by default:
- Default program folder on Windows computers:
- 32-bit: C:\Program Files\IBM Optim\RT\BIN
- 64-bit: C:\Program Files (x86)\IBM Optim\RT\BIN
- Default program folder on Linux or UNIX computers: /opt/IBM/Optim/rt/bin
If the pr0cmnd program is in a folder other than the default
folder, add the following argument to the end of the
proxy_folder/eclipse.ini file.
You must always add this argument if you install Optim on a computer with a 64-bit version of Windows.
-Dcom.ibm.nex.pr0cmnd.location=pr0cmnd_folder
- pr0cmnd_folder is the program
folder for the pr0cmnd program.
For example, the following line specifies
/opt/IBM/Optim/dist/bin as
the name of the program folder for the pr0cmnd program.
-Dcom.ibm.nex.pr0cmnd.location=/opt/IBM/Optim/dist/bin
Configuring the proxy to send services to Optim for z/OS
If
you can successfully run an Optim for z/OS® service from the designer,
you can run the same service without any further configuration of
the proxy. However, you might need to configure your network, firewalls,
and IBM® z/OS computer so that the proxy can successfully
send the service to the z/OS computer.
Setting the registry and repository locations
By
default, the proxy is set to use the registry and repository at http://localhost:8080/server/registry and http://localhost:8080/server/repository.
These locations are valid if the registry and repository are on a
management server that is installed on the proxy computer and that
uses port 8080. By default, WebSphere Application Server Community
Edition uses port 8080 for the management server. If the proxy and
the registry and repository are on different computers, you must set
the registry and repository locations for the proxy. You must also
set registry and repository locations if you deploy the management
server to an application server other than WebSphere Application Server
Community Edition.
Open the
proxy_folder/eclipse.ini file
and look for the following lines, where
registry_URL is
the location of the registry and
repository_URL is
the location of the repository. If these lines exist, set the lines
to the correct registry and repository locations. If these lines do
not exist, add the lines to the file with the correct registry and
repository locations.
-Dcom.ibm.optim.registry.url=registry_URL
-Dcom.ibm.optim.repository.url=repository_URL
For example, the following lines specify
http://mgmtserver1:8080/server/registry as
the registry location and
http://mgmtserver1:8080/server/repository as
the repository location.
-Dcom.ibm.optim.registry.url=http://mgmtserver1:8080/server/registry
-Dcom.ibm.optim.repository.url=http://mgmtserver1:8080/server/repository
Setting the host name and port for a proxy
If
the proxy computer is assigned IP addresses dynamically, set the host
name and port that are to be used by the proxy. To set the host name
and port for the proxy, add the following arguments to the end of
the
proxy_folder/eclipse.ini file.
-Dcom.ibm.optim.host.name=host_name
-Dcom.ibm.optim.host.port=host_port
- host_name is the host name
or IP address of the proxy.
- host_port is the port used
by the proxy.
For example, the following lines specify proxy_computer as the
host name of the proxy and 12000 as the port number used by the proxy.
-Dcom.ibm.optim.host.name=proxy_computer
-Dcom.ibm.optim.host.port=12000
Setting the shared library environment variable
When
you install the proxy on Linux or UNIX, set the shared library environment
variable to include the directory that contains the proxy libraries
(
proxy_folder/shared/bin).
Set the shared environment variable for each account that is used
to run the proxy. To set the shared library environment variable for
an account, add the following lines to the account login profile.
Setting the proxy to use the https protocol
You
can establish a trust relationship between a management server and
a proxy. Among other things, you must set the proxy to use the https
protocol to communicate with other components. The proxy uses the
http protocol unless you set the proxy to use the https protocol.
To set the proxy to use the https protocol, add the following argument
to the end of the
proxy_folder/eclipse.ini file.
-Dcom.ibm.optim.url.protocol=https
For
example, the following lines specify
https://mgmtserver1:8080/server/registry as
the registry location and
https://mgmtserver1:8080/server/repository as
the repository location.
-Dcom.ibm.optim.registry.url=https://mgmtserver1:8080/server/registry
-Dcom.ibm.optim.repository.url=https://mgmtserver1:8080/server/repository
-Dcom.ibm.optim.url.protocol=https
Configuring native data store (NDS) capabilities on
a proxy
To configure a proxy to run services that use native
data stores, install the relational database client software on the
proxy computer. Then, use a native data store location property to
specify the location of the native shared libraries that are installed
with the database client. Add the native data store location property
for the relational database system to the end of the proxy_folder/eclipse.ini file.
The
following list contains the name of the native data store location
property for each supported relational database system.
- DB2® for Linux, UNIX,
and Windows: com.ibm.nex.nds.rdbms.udb.location
- DB2 for z/OS: com.ibm.nex.nds.rdbms.db2.location
- Oracle: com.ibm.nex.nds.rdbms.oracle.location
- Informix®: com.ibm.nex.nds.rdbms.informix.location
For example, the proxy is installed on a Linux computer, and the native shared libraries
for DB2 for Linux, UNIX,
and Windows are installed
at
/opt/IBM/db2/V9.7/sqllib/lib32. To configure
the NDS capability for DB2 for Linux, UNIX, and Windows on
the proxy, add the following line to the end of the
proxy_folder/eclipse.ini file.
-Dcom.ibm.nex.nds.rdbms.udb.location=/opt/IBM/db2/V9.7/sqllib/lib32
Configuring the proxy to use the exact driver version
specified on all service requests
By default, the proxy
uses the JDBC driver that is specified on the service request or any
newer version of the same driver. The proxy uses the first such driver
that it finds in the repository. You can configure the proxy so that
the proxy uses only the version of the JDBC driver that is specified
on the service request. If the repository does not contain the version
that is specified on the service request, the proxy returns an error. To
configure the proxy so that the proxy uses only the exact driver version
that is specified, add the following line to the end of the
proxy_folder/eclipse.ini file:
-Dcom.ibm.nex.capability.driver.compatility.level=enforceExactVersionMatch
Configuring the proxy to use UTF-8 encoding in logs
If
you install the proxy on a computer that is set to a language that
requires the use of double-byte characters, configure the proxy to
use UTF-8 encoding in its log files. To configure the proxy to use
UTF-8 encoding, add the following line to the end of the
proxy_folder/eclipse.ini file.
-Dfile.encoding=UTF-8
On Windows computers, you must also
add the following line, where
encoding is
the character encoding that is used by the Windows computer. For example, use
MS932 for
Shift JIS encoding.
-Dconsole.encoding=encoding
Setting file permissions
If you install
the executor on a Linux or UNIX computer as a user other than
the superuser, file permissions on your home directory might restrict
users from using the executor. To correct this issue, complete either
of the following tasks.
- Ask the administrator to install the executor to /opt/IBM/Optim/executor.
- Set the file permissions to the folder to which the executor is
installed so that users can run the executor.