Skip to end of metadata
Go to start of metadata

This document describes how to deploy a Nexaweb Java or Ajax application with Nexaweb Platform server. To deploy Nexaweb Java or Ajax applications with IIS.net, PHP or any other Java EE or HTTP server, see that server's documentation.
 

Nexaweb Server is a collection of Servlet components that live inside a J2EE web application. You deploy a Nexaweb-enabled application the same way that you deploy any other J2EE application.  You package your application either in a Web Application Resource (WAR) file, or an Enterprise Application Resource (EAR) file for deployment.

 

Helpful Tip

There is no need to install Nexaweb Platform to the deployment server, simply deploy the WAR file.  Everything needed is there.

 

There is no need to install Nexaweb Platform to the deployment server, simply deploy the WAR file.  Everything needed is there.

In addition, following is a list of the set of permissions that are required for Nexaweb applications to function properly on all application servers.  

Most application servers' java.policy files include all of these permissions. However, some application servers ship with Sun Application server's java.policy stricter than most (notably Sun Java System Application Server) and you must edit the policies to ensure that the permissions listed below are set:

permission java.lang.RuntimePermission   "createClassLoader";
permission java.lang.RuntimePermission   "getClassLoader";
permission java.lang.RuntimePermission   "setContextClassLoader";
permission java.lang.RuntimePermission   "loadLibrary.*";
permission java.util.PropertyPermission  "*", "read,write";
permission java.net.SocketPermission     "*", "connect,accept,resolve";
permission java.io.FilePermission        "<<ALL FILES>>", "read,write";

The following permission is specific to Sun Java System Application Server. 

permission org.apache.naming.JndiPermission "*";

If after deployment, attempting to run a Nexaweb application causes errors on the client, such as missing JAR files (jvm-detector.jar not found), restart the application server.

The following are suggestions to troubleshoot the cause of application errors:

  1. View the Nexaweb Server Management Console to ensure that the server has started correctly.
  2. Examine the application server log files.
  3. Examine the browser Java console.
  4. Change the default log level from "info" to "debug" inside nexaweb-server.xml and run the Nexaweb server in debug mode.
  5. Trace traffic between the browser and the application server by setting up a TCP tunnel.  Use the <nexaweb-platform-sdk>/bin/tcptunnel.bat script or any other tcp monitoring tool.

Troubleshooting

  • System property permissions
  • ClassLoader permissions
  • Socket permissions
  • File system permissions.
  • Permissions Required for specific Application Servers

Note: The server policies are typically in Java policy file format, although some applications may provide GUI access to the policies.

  • No labels