Limitations with customer-supplied applets and Java

Start of changeIf a user runs a customer-supplied applet (that is, an applet written by your company or a third party) with a session (such as 3270 Display) launched from a Java Z and I Emulator for Web client, and if this applet requires any Java permissions, you are suggested taking one of the following actions to meet the security requirements of Java: Start of change
  • The applet must be archived in a signed Java .JAR file.
  • The permissions must previously have been granted on the workstation using the Java Policy Tool that is provided with the Java plug-in.
End of change End of change

If you do not meet the security requirements of Java, the applet silently fails.