| Instructional Deployment Examples |  |
| This appendix contains several examples to deploy Web UI. Deploy Web UI on IBM WebSphere Express v6 Before you begin the deployment of Web UI, consult the IBM WebSphere v6 documentation and make sure that you have: An HTTP Server up and running (for example IBM HTTP Server or IIS) IBM WebSphere v6 up and running Make sure that the HTTP Server is able to connect to the IBM WebSphere installation (plug-in setup). You can use the following procedure to do the following: Deploy Web UI for the first time (first installation). Deploy a new Web UI version in an existing environment ( Web UI upgrade). Note Before you start an upgrade, copy the webtopProperties.xml and smartlink.properties files from the < installation-directory>\webtop\config directory to a directory that will not be overwritten by the new installation. After the upgrade, you can restore the files. To deploy Web UI, take the following steps: Start the IBM WebSphere Administrative Console. Open the Applications node. Click Install New Application. Install New Application In the next screen, locate the webtop.war file, and determine the <webtop-root> by filling the Context Root field. New Application Parameters Click Next. In the next screen also click Next. In the "Application Security Warnings" screen click Continue. The following screen contains a 4-step wizard. Click Next to proceed to step 2. Step 2 is an important step. In this setup you must ensure that the Web UI module is also configured in the plug-in configuration file. Select the Web UI module (checkbox) and select the web server in the list box. Click Apply. Then click Next. Map modules to servers Click Next at step 3. Click Finish. Click on the "Save to Master Configuration" link. Click Save. The deployment is now finished. Start the web application. Click on "Enterprise Application". Select the Web UI web application and click Start. You can access the Web UI through the following URLs: http://<hostname>:<port>/<webtop-root>/servlet/admin, for administrator login http://<hostname>:<port>/<webtop-root>/servlet/login, for user login using BaanLogin or Rexec authentication http(s)://<hostname>:<port>/<webtop-root>/servlet/ssologin, for user login using Infor Single Sign On ( Infor SSO ) authentication. By logging on, users can access multiple applications. To use Infor SSO, various settings must be defined. For details, refer to Appendix D, "Prerequisites for using Infor Single Sign On". http(s)://<hostname>:<port>/<webtop-root>/servlet/fslogin, for user login using Federation Services authentication. By logging on, users can access multiple applications. Federation Services authentication is handled by Active Directory Federation Services (ADFS). Depending on ADFS configuration settings users can be logged on automatically based on their Windows credentials. To use Federation Services authentication, various settings must be defined. See Configuring Federation Services for ERP LN with Web UI. Deploy Web UI and Report Viewer on Tomcat Directory structure To keep the Tomcat application "clean", install your applications in a directory structure outside the Tomcat file hierarchy. For example, in Linux, use the following structure:
/opt/webapps | Parent directory.
/opt/webapps/webtop | Directory for the Web UI application.
/opt/webapps/config | Directory for the configuration files, and user profiles, of Web UI.
/opt/webapps/reportviewer | Directory for the Report Viewer application.
/opt/webapps/warfiles | Directory for the warfiles, "webtop.war" and "reportviewer.war."
2. In Windows, use a similar structure: C:\webapps C:\webapps\webtop C:\webapps\config C:\webapps\reportviewer C:\webapps\warfiles To deploy the Report Viewer and Web UI Create the directories mentioned previously, and put the warfiles in the "warfiles" directory. Manually unzip the warfiles into their application directories: For Linux:
       cd /opt/webapps/webtop
       $JAVA_HOME/bin/jar xf /opt/webapps/warfiles/webtop.war
       cd /opt/webapps/reportviewer
       $JAVA_HOME/bin/jar xf /opt/webapps/warfiles/reportviewer.war
   For Windows:
       cd C:\webapps\webtop
       %JAVA_HOME%\bin\jar.exe xf c:\webapps\warfiles\webtop.war
       cd C:\webapps\reportviewer
       %JAVA_HOME%\bin\jar.exe xf c:\webapps\warfiles\reportviewer.war
3. Create a configuration file "webtop.xml" to specify a new context for Tomcat, and save it in the "/opt/webapps", or "C:\webapps", directory. The file must contain the following:
       <Context docBase="/opt/webapps/webtop">
         <Parameter name="WebtopAdminPassword"
           value="TopSecret"
           override="false"/>
         <Parameter name="WebtopConfigPath"
           value="/opt/webapps/config"
           override="false"/>
         <Logger className="org.apache.catalina.logger.FileLogger"
           prefix="localhost_webtop."
           suffix=".txt"
           timestamp="true" />
       </Context>
4. Note: The paths in this example are in Linux style. For Windows, change them accordingly. The "context path" that Tomcat uses is derived from the file name: If you use the default name "webtop.xml", Tomcat will find your application at the "http://<hostname>:<port>/webtop" URL. If you plan to have multiple versions of Web UI on the same server, you can use a "context path" other than "/webtop", such as "/webtop8_7". In this case, you must rename your configuration file to "webtop8_7.xml". The URL to access the Web UI application changes accordingly to "http://<hostname>:<port>/webtop8_7", for example. The value of the "WebtopAdminPassword" parameter specifies the password you need to logon to the Infor ERP LN Web UI Administration Console ("http://servername:portnr/webtop/servlet/admin"). Change it to an appropriate value. To specify a new context for Tomcat, create a configuration file "reportviewer.xml", and save it in the "/opt/webapps", or "C:\webapps", directory. The file must contain the following:
       <Context docBase="/opt/webapps/reportviewer">
         <Logger className="org.apache.catalina.logger.FileLogger"
           prefix="localhost_reportviewer."
           suffix=".txt"
           timestamp="true"/>
       </Context>
Note: The paths in this example are in Linux style. For Windows, change them accordingly. It is recommended not to change the name of the configuration file. Web UI expects the Report Viewer to be present at the context path "/reportviewer". If you decide to use another configuration file name (and therefore another context path), you must use the Report Viewer page in the Web UI Administration Console to change the location where Web UI expects to find the Report Viewer: Start the Web UI Administration Console and open the Report Viewer page. In the Virtual directory of Report Viewer application field, enter the new context path (without the leading "/"), and click Submit. Copy both context files ("webtop.xml" and "reportviewer.xml") into the "conf/Catalina/localhost" directory inside your Tomcat installation. Note: On Windows, you can find the Tomcat installation in a location such as "C:\Program Files\Apache Software Foundation\Tomcat 6.0.29". On Linux, the administrator might have chosen a location such as "/opt/tomcat6.0.29" or "/usr/share/tomcat6.0.29". Stop and restart Tomcat to ensure the applications are deployed. Related topics Install Method 1 – Deploy Web UI to a Servlet Container |