The launchClient command provides several parameters to control the Java 2 security manager. By default the launchClient command does not enable nor run with a Java 2 security manager. To enable the Java 2 security manager, add the following parameter to your launchClient command:
-CCsecurityManager=enableFor example:
launchClient myear.ear -CCsecurityManager=enable
Note: If the EAR file is a set of directories and subdirectories, then it is used in place and not expanded.
The J2EE application client run time sets the com.ibm.websphere.client.applicationclient.archivedir system property to the directory location of the EAR file. The client.policy file uses this system property to inform the security manager of the location of your application client code base and to assign the configured permissions to that code base. This activity occurs when the security manager is enabled. If the security manager is enabled at the time the Java code is started, then this system property is not set, the code base is unknown, and the permissions are not granted.