This wizard creates the directory structure for a JSP application generated by the JSP Generator. It copies all necessary infrastructure files into the application directory. Execute the script from the directory path JSPGenerator\Utilities\Setup directory subfolder of the Component Enabler installation folder.
The SetupJSP.vbs script prompts for the following input:
Output Directory: This is the CE Output directory (for example, C:\NGEN_CE\classes).
Package Prefix: Specify the package prefix (for example, com.unisys).
Destination Directory: Tomcat Destination directory (for example, C:\Tomcat6\webapps).
Application Name: Specify the application name to be deployed in the Tomcat server (for example, sample).
Bundle Name: Specify the Bundle Name ( jsp).
Number of Languages for the system: Specify the number of languages (for example, 1)
Confirmation of the locale identifiers: Press YES to use the locale identifiers.
Language Number – Specify the language number (for example, 1033 for English).
The following tasks are performed by the script depending on the information being provided:
Creates the output directory structure.
Infrastructure files, which are required by the generated JSP application is copied into the appropriate folders being created.
The Ispec is copied into the application folder and prefixed by {PackagePrefix}.{ApplicationName}.{BundleName}.
The default.jsp page is initialized as appropriate.
The script, SetupJSP.vbs updates the ce.properties file with the following properties.
ce.properties: This file identifies host connection parameters and other runtime settings.
Application Name
Bundle Name
Package Prefix
The SetupJSP.vbs creates the directory structure in the Tomcat server.
The Application root contains a separate \langn directory for each language you support. The language directories contain the css files and JSP Pages. There is a separate directory for each language on your system. Each language directory also holds a copy of additional files that are used, for example, for displaying errors. You must have a copy of these in each language directory to allow you to translate any displayed text into the appropriate language.
The following section describes the contents of the Application root and language directories in more detail.
Application root directory
global.jsp contains the startup and shutdown routines for each session. You must customize this file with the logon details for your system.
Default.jsp is used as the default page for your application.
Page2.jsp sets the values in fields, transmits transactions to Agile Business Suite, performs some error checking, and redirects the Ispec from the host application to the correct generated JSP Form.
MenuAL.js is a JavaScript library that implements the right-click or context-sensitive menus on the JSP Pages.
FatalErr.jsp creates the HTML Form that the users see when a fatal error occurs. It displays the problem, and it should be customized to provide information to the user on how to report the problem. There is only one version of this file, because it is not always possible to detect which language version is being used when a fatal error occurs. Therefore, the file should repeat the information in all the languages the system uses.
langn directories
The language directories contain the JSP Pages and .css files for each of the Ispecs that you generate. In addition, they contain the following files, which must be translated and tailored for each language.
Note: You must have an understanding of HTML before you attempt to alter the JSP Pages. It is also an advantage if you have knowledge of JavaScript, but this is not essential.
Close.htm is a HTM document that is called when the system sends a close message to the client workstation. It displays a simple information message to the user and has a button, which, when selected, closes that instance of the browser.
Console.html is a HTML document that implements the two frames required to create a console. This page does not require any changes.
Console-in.jsp creates the information shown in the top frame of Console.htm. It displays the console messages sent by the host. This Page does not require any changes.
Console-out.html is a HTML document shown in the bottom frame of Console.html. It submits the commands to Command.jsp. You need to translate the contents of this Page for the languages you support.
Command.jsp contains the code that sends the commands to the host application. This Page must not be altered.
Language.jsp shows a list of languages available for the system. You should translate the header and button labels in this Page.
Multierr.jsp creates the Page that is displayed when multiple errors are returned from the host application. The Page that caused the errors is also displayed; therefore, you might switch between forms. When you have corrected all the errors, click Close to close the page. The label on the Close button should be translated.
SelectIspec.jsp is generated along with the JSP Pages and lists all the Ispecs in the bundle. Since SelectIspec.jsp is regenerated every time when an Ispec is added or removed from the Bundle, it should be retranslated before deploying for your locale.