7-8 Programming Stand-alone Clients for Oracle WebLogic Server
usernameweblogicusername password-encrypted{Algorithm}PBEWithMD5AndDES{Salt}dWENfrgXh8U={Data}u8xZ968d
ElHcksoZYm2LQ6xVNBPpBGQpassword-encrypted saf-login-context
saf-remote-context
Use the ClientSAFEncrypt utility for all passwords with the same key-password
required by the remote contexts defined in the JMS SAF client configuration file. When a client starts using the JMS SAF client, it must supply the
same key-password that was provided to the ClientSAFEncrypt utility.
6.
Type quit to exit the ClientSAFEncrypt utility.
7.2.2.2 ClientSAFEncrypt Utility Syntax
The weblogic.jms.extensions.ClientSAFEncrypt utility encrypts cleartext strings for use with JMS SAF clients in order to access remote SAF contexts.
java [ -Dweblogic.management.allowPasswordEcho=true ] weblogic.jms.extensions.ClientSAFEncrypt [ key-password ]
weblogic.jms.extensions.ClientSAFEncrypt [ remote-password ]
7.2.3 Installing the JMS SAF Client JAR Files on Client Machines
WebLogic Server provides three JMS SAF client options:
■
weblogic.jar, see Section 2.2.3, WebLogic Install Client
■
wlfullclient.jar , see
Section 2.2.2, WebLogic Full Client
■
A thin client that uses the wlsafclient.jar, wljmsclient.jar, wlclient.jar
The required JAR files are located in the WL_HOME\server\lib subdirectory of the WebLogic Server installation directory, where WL_HOME is the top-level installation
directory for the entire WebLogic product installation for example, c:\Oracle\Middleware\wlserver_10.3\server\lib
. Oracle recommends using either the higher-performing WebLogic Full or Install client
unless a small jar size is of high importance. To use the wlfullclient.jar, install it to a directory on the client machine’s file system and add it to its CLASSPATH. Using
the wlfullclient.jar file also allows you to run the ClientSAFGenerate utility
Table 7–7 ClientSAFEncrypt Arguments
Argument Definition
weblogic.management.allow PasswordEcho
Optional. Allows echoing characters entered on the commandweblogic.jms.extensions.ClientSAFEnc
rypt expects that no-echo is available; if no-echo is not
available, set this property to true. key-password
The key to use when encrypting all remote passwords needed for the remote contexts defined in the JMS SAF
client configuration file. If omitted from the command line, you will be prompted to
enter a key-password. remote-password
Cleartext string to be encrypted. Multiple passwords for each remote context can be generated in one session.
If omitted from the command line, you are prompted to enter a remote-password.
Reliably Sending Messages Using the JMS SAF Client 7-9
on a client machine to generate a configuration file from an existing JMS SAF client configuration file, as described in
Section 7.2.1.2, Steps to Generate a JMS SAF Client Configuration File from a JMS Module.
When smaller JAR sizes are required for thin clients, the JMS SAF client requires installing the following JAR files to a directory on
the client machine’s file system and adding them to its CLASSPATH:
■
wlsafclient.jar
■
wljmsclient.jar
■
wlclient.jar The wljmsclient.jar has a reference to the wlclient.jar, so it is only necessary to put one
or the other JAR in the client machine’s CLASSPATH. For more information about deploying thin clients, see
Section 5.1, Overview of the Thin Client.
7.2.4 Modify Your JMS Client Applications To Use the JMS SAF Clients Initial JNDI Provider
