VERIFIED SOLUTION i
X

How to deploy Serviceweb2.war on Websphere

UPDATED: October 18, 2017


Deploying Serviceweb2.war under Websphere:

 

Installing ServiceWeb2 under Websphere 8.5.5

Before installing the ServicedWeb2.war file, the war file must have its web.xml file modified

before it is deployed to Websphere 8.5.5.

1. Modify the war file to update the WEB-INF/web.xml for hostname and port.

These are the Vault hostname and the port the e2serverd listens on. You can use a tool

like 7zip to update the web.xml in the war file directly. The configuration parameters are

organized as context parameters within the web.xml file.

 

2. Connect to the websphere admin console using a web browser.

3. Select Applications > New Application.

4. Select New Application > New Enterprise Application.

5. For Path to the new application, select Local File system and navigate to the

ServiceWeb2.war file you modified. Click Next.

6. For How do you want to install the application?, select Fast Path, Click Next.

7. At Select Installation Options, click Next.

8. For Map modules to Servers, select ServiceWeb2. Click Next.

9. For Map Virtual hosts for Web modules, select ServiceWeb2. Select a host and click

Next.

10. For Map context roots for Web Modules, enter /ServiceWeb2 for Context Root. Click

Next.

11. At Metadata for modules, click Next.

12. At Summary, click Finish.

13. Wait for the installation to complete and then save the changes.

14. Start the ServiceWeb2 application.

ServiceWeb2 configuration parameters

The following is a list of the available configuration (i.e. context) parameters.

Note: The context parameter names are case-sensitive and have to be specified exactly as

shown below.

hostname

The hostname for the Rendering Engine that the ServiceWeb2 application will connect to.

Defaults to “localhost”.

 

Example:

<Parameter name="hostname" value="somehost.somedomain.com"

override="false"/>

port

The port number for the Rendering Engine that the ServiceWeb2 application will connect to.

Defaults to 6003.

Example:

<Parameter name="port" value="8003" override="false"/>

 

forcepdf

If set to true, all documents viewed in the browser interface will be rendered to and displayed

as PDF. Defaults to false.

Example:

<Parameter name="forcepdf" value="true" override="false"/>

maxresults

The maximum number of search results to display per page. Defaults to 20.

Example:

<Parameter name="maxresults" value="25" override="false"/>

outputformat

The image output format to which documents are rendered to for display in the browser

interface. Defaults to GIF. Valid values are GIF or PNG.

Example:

<Parameter name="outputformat" value="PNG" override="false"/>

log4jconfigfile

If non-null, use this absolute file path (on the same filesystem as the Servlet container) as the

Log4j configuration file. Defaults to null (i.e. unspecified).

Example:

<Parameter name="log4jconfigfile"

value="D:\e2-ServiceWeb2\myLog4jConfig.xml" override="false"/>

ssltruststorepath

If non-null, use this as the SSL truststore for verifying the identity of the SSL-enabled

Rendering Engine that the ServiceWeb2 application will connect to. If this parameter is

specified, then the ssltruststorepassword must also be specified.

Example:

<Parameter name="ssltruststorepath"

value="C:\Some\Path\to\e2vault-server.jks" override="false" />

 

ssltruststorepassword

If non-null, use this as the password to access the SSL truststore for verifying the identity of

the SSL-enabled Rendering Engine that the ServiceWeb2 application will connect to. If this

parameter is specified, then the ssltruststorepath must also be specified.

Example:

<Parameter name="ssltruststorepassword" value="ChangeThisPassword"

override="false" />

 

 

Environment Details

Product Feature: Server

Operating System: AIX

Database: Not stated

Configuration: WebSphere
 

Downloads

  • No Downloads