Websydian J2EE Architecture Deploying

Overview    Parts    Deploying    Background

• Requirements

• Pack Websydian Application

• Deploy Websydian Application

Requirements

It must be ensured that the necessary objects and files described in the following sections are available before successfully deploying a Websydian J2EE application

• Websydian run-time file
  This is the file WsydDwa21.jar found in the Websydian installation folder.
• Plex Java run-time
  This is the file ObRun.jar found in the Plex installation folder.
• Application jar file
  A jar file containing the Plex generated Websydian application. The jar file must contain all the functions called using local function call from the Websydian application. That is non-server functions, eventhandlers, pagegenerators etc.
• Third party run-time files
  All third party run-time files, .
• EJB Proxy (optional)
  If the server functions are accessed through the EJB Proxy then this file must also be deployed as part of the web application. For further information on deployment of the EJB Proxy read the Plex help. It is recommended deploying the EJB Proxy and required components as a stand-alone EJB and not as part of the Web Application.

Pack Websydian Application

Before the Websydian application can be deployed it must be packed as a J2EE web application, also known as a web application archive (WAR file). This can be done using the package tool supplied with the chosen J2EE server.
This section describes the general steps in packaging a WAR file. Please consult the white paper section at the Websydian support site for deployment details for specific J2EE servers.

1. Create a WAR file that contains the Websydian application.
2. Add a Web Component to the WAR file.
3. Configure the Web Component as a servlet using the following information:

   Servlet jar file	WsydDwa21.jar
   Servlet class file	com.websydian.pka.servlet.J2eeProxy
   Servlet initialization parameters	Name: servlet.propertyfile. Value: path to property file If this value is left blank, then the J2EE Proxy will look for the property file inside the WAR file in "WEB-INF/J2eeProxy.prop".
   Alias	Name used to access the servlet from a browser.

4. Add the following jar files to the web application library path:
   
   • ObRun.jar (Supplied with Plex).
   • Application jar file.
   • ObEJBProxy.jar (if the application connects to the backend server using the EJB Proxy, supplied with Plex).
5. Remember to specify a web context for the web application. The web context is the first part of the URL path that the user uses to access the Websydian application. The URL will look like this: http://<hostname>/<webcontext>/<servletalias>. So if the alias specified in 3) is /myservlet, the web context is /mytestapp, and the host name is www.myserver.com then the final URL will be http://www.myserver.com/mytestapp/myservlet.

When the Websydian application is deployed please make sure that the following files also are copied to the J2EE server.

Deploy Websydian Application

The Websydian application can be deployed to the J2EE server using the WAR file generated in the previous section. For details on how to do this for specific J2EE servers please refer to the manual of the chosen J2EE server. Also check the white papers at the Websydian support site (http://www.websydian.com).