Scribd
Upload
1 views

PROCESS_DIRECTOR_Web_Application_System_Requirements_7.2.x

Uploaded by

misrak dagne
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
1 views

PROCESS_DIRECTOR_Web_Application_System_Requirements_7.2.x

Uploaded by

misrak dagne
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

PROCESS DIRECTOR 7.

Web Application System


Requirements
October 2015 – ReadSoft AB
The contents of this document are subject to change without notice.

Questions or comments about this document may be emailed to [email protected].

26102015.1010

ReadSoft AB (Head office) | Södra Kyrkogatan 4 | SE-252 23 Helsingborg | Sweden | Phone: +46 42 490 21 00 | Fax: +46 42 490 21 20
ReadSoft AG | Falkstrasse 5 | 60487 Frankfurt | Germany | Phone: +49 69 1539402-0 | Fax: +49 69 1539402-13
[email protected] | www.readsoft.com
Contents
Hardware requirements ........................................................................ 4

Software requirements .......................................................................... 5

Tested environments ............................................................................ 9

PROCESS DIRECTOR 7.2 Web Application System Requirements | page 3 of 9


Hardware requirements
The PROCESS DIRECTOR Web Application should run on its own server. However,
installation on systems running other applications is also possible.

The minimum hardware requirements are:

Item Requirement

RAM ReadSoft recommends about 30 MB per concurrent user session. Thus, if 100
users are logged on simultaneously, you can expect memory usage of around 3 GB.

Installation on a Virtual Machine is also possible and supported by ReadSoft.

For information about support for mobile devices, please contact your local ReadSoft
representative or the ReadSoft SAP Solutions Lab.

PROCESS DIRECTOR 7.2 Web Application System Requirements | page 4 of 9


Software requirements
The following table lists ReadSoft's recommended software as well as the minimum
requirements:

Item Recommendation Minimum requirement

Operating system Windows 7 Any operating system supported by the


other software components below.
Windows XP
Windows 2012 Server
Windows Server 2008 or
2008 R2
Windows Server 2003
Windows 2000

Web browser (No recommendation) Internet Explorer, Versions 7 to 10. For


PROCESS DIRECTOR Web Application
versions prior to 7.2 patch level 5, Version
10 must be run in compatibility mode (see
below).
Firefox, version 3 and later
Safari, version 4 and later
Chrome, version 4 and later

Java Runtime JRE 6 JRE 5


Environment
(JRE) JRE 7

Web application Apache Tomcat 6.0 J2EE compatible


server
Apache Tomcat 7.0 Java Servlet 2.4
SAP Netweaver CE from Java Server Pages (JSP) 2.0
version 7.1

Java Connector 2.1.10 2.1.10


(JCo)
3.0 (see below)

PROCESS DIRECTOR 7.2 Web Application System Requirements | page 5 of 9


Important: The parameter pd_suggest_jpa must be set to no for Netweaver
installations.

Note: If using a 64bit version of JRE, the other components must also be 64bit.

Note: The PROCESS DIRECTOR Web Application only works if PROCESS


DIRECTOR is installed. See the PROCESS DIRECTOR Installation Guide for
instructions on installing PROCESS DIRECTOR.

Known limitations with Internet Explorer 8


In Internet Explorer 8, the browser memory usage increases each time an attachment is
uploaded in the PROCESS DIRECTOR Web Application. This can lead to slow performance
if a large number of attachments are added.

PROCESS DIRECTOR and Internet Explorer 10


Internet Explorer Version 10 (IE10) should always run in compatibility mode for PROCESS
DIRECTOR Web Application versions prior to 7.2 patch level 5, otherwise the PROCESS
DIRECTOR Web Application may not display or work correctly. This mode can be set for a
specific server or site, so it is not necessary to enable it for all sites.

1. Open the PROCESS DIRECTOR Web Application in IE10.

2. Go to Tools > Compatibility View settings.

3. Click the Add button.

PROCESS DIRECTOR 7.2 Web Application System Requirements | page 6 of 9


Using JCo 3.0
With JCo3, if you deploy several instances of the Web Application on Tomcat, only the first
instance that connects to JCo3 after restarting Tomcat will work. This also applies if you
deploy one instance of the PROCESS DIRECTOR Web Application together with other web
applications such as MOBILE APPROVAL and INFO MAIL. If you wish to use multiple
instances or web applications, you must move the jcolayer library to the Tomcat main
library folder and remove it from all Web Application library folders.

1. Deploy all instances of the Web Application that you wish to use.

2. Start Tomcat.

3. After the WAR files are unpacked, go to the Tomcat/webapps/pdweb-app/WEB-INF/lib


folder of the newest Web Application and copy the jcolayer*.jar file to the
Tomcat/lib folder (the name of this file my vary; for example, it could be
jcolayerB030204.jar or jcolayer-1.0-SNAPSHOT.jar).

4. Remove the jcolayer*.jar file from the Tomcat/webapps/pdweb-app/WEB-INF/lib


folder of all deployed Web Application instances.

5. Restart Tomcat.

PROCESS DIRECTOR 7.2 Web Application System Requirements | page 7 of 9


Note: When using JCo 3.0, the maximum number of SAP connections specified in the
saplogon.properties file is not multiplied by 10 internally (unlike in JCo 2, where
maxconnections=10 actually means 100).

PROCESS DIRECTOR 7.2 Web Application System Requirements | page 8 of 9


Tested environments
Note: All tests with our web applications are performed within Microsoft Windows
environments only.

Item Tested with

Operating system  Windows 7


 Windows XP
 Windows Server 2008 R2, 2008 and 2003
 Windows 2000

Java Runtime Environment (JRE)  Java 5 (JRE 5)


 Java 6 (JRE 6)
 Java 7 (JRE 7)

Web application server  Apache Tomcat 6.0


 Apache Tomcat 7.0

SAP Java Connector (JCo)  2.1.10


 3.0

PROCESS DIRECTOR 7.2 Web Application System Requirements | page 9 of 9

You might also like