The instructions below are located on Primavera v 5.0 CD1, under the \Install directory.
OVERVIEW
========
Primavera Group Server version 5.0 facilitates the use of the
HTTP(S) protocol. The GroupServer.war file is a J2EE-compliant
servlet that allows client communications to occur over the
HTTP protocol between the Timesheet client and the Group Server
servlet. This Web archive file (WAR) must be installed
on a Java application server, such as Tomcat. The servlet runner
(Java application server) can be configured to secure
these communications over HTTPS.
NOTE: If the Primavera Group Server and Java application server
do not reside on the same machine, you must edit the WEB.XML
file. The WEB.XML file is contained within the GroupServer.war
file. Editing this file is described in the Configuring the
Servlet section, later in this document.
INSTALLING PRIMAVERA GROUP SERVER TO USE HTTP
=============================================
1. Shut down any existing Primavera Group Server services.
2. Run the Setup wizard from the root folder on the Primavera CD-ROM.
NOTE: The steps to install the Primavera Group Server to use HTTP are
also documented with illustrations in the Primavera Administrator’s
Guide. Refer to the section, Installing the Primavera Group Server
and Timesheets Files, in Part 2.
3. Click Next on the Welcome dialog box.
4. Choose the components to install. Mark both checkboxes to install the
Primavera Group Server and Timesheets files on the same server.
5. Click Browse to specify a destination for the Web files.
The files will be installed in a folder named \GroupServer\en
at the selected location.
If you are installing over an earlier version of the Group Server, your
existing Web files will not be overwritten. Instead, the new ones will
appear in the \en subfolder below the old Web files.
6. Select the database type. The database must already be installed and
configured.
7. Specify the database connection parameters.
The database user name must be a privileged user (privuser).
If connecting to Oracle, an Oracle DSN need not be predefined. Enter
the Oracle Service Name, which may have been defined using Oracle’s
Net8 Easy Config tool, or you can refer to your TNSNAMES.ORA file
located in \Oracle_Home\Network\Admin.
If connecting to Microsoft SQL Server, type the SQL Server database
machine name, which is the name of the computer on which the Microsoft
SQL Server database is running. In the Database Schema Name field, type
the name of the database specified when the Microsoft SQL Server
database was created, such as PMDB.
8. Choose HTTP(S) as the protocol to connect to the Primavera Group Server.
Click Browse to specify a destination folder for deploying the
GroupServer.war file.
By default, the GroupServer.war installs to the inetpub\wwwroot folder. However,
you should specify the location that your Java application server uses
for storing Web applications.
NOTE: Depending on the Web server you are using, you may need to expand the GroupServer.war file manually.
See the Java application server’s documentation for more information.
9. Specify the URL for the Group Server servlet, which depends on
the Java application server being used and its configuration.
For normal transmission using the HTTP protocol, enter http and the
port number to which you have configured your Java application server
to service http requests. Use the following format:
http://<Java app server>/GroupServer/GroupServer.
The URL for a default Tomcat installation is
http://<my_tomcat_server_name:8080>/GroupServer/GroupServer.
Note that some Java application servers (e.g., IBM’s WebSphere)
are case-sensitive.
For secure transmission using the HTTPS protocol, enter https and the
port number to which you have configured your Java application server
to service https requests. The default port on Tomcat is 8443. For
example, specify the secure URL as,
https://<my_server_name:8443>/groupserver/groupserver.
NOTE: This URL can be changed after setup completes by editing the
erps8x6.html file in the GroupServer/en Web site folder.
From the erps8x6.html file:
// *** Configurable variables.
// *** May be changed by the system administrator.
var ServerName=”;
var ServerPortNum=9002;
var DebugLevel=0;
var Protocol=’http’; // This should say ‘http’ for HTTP OR HTTPS, or,
// ‘socket’ for a traditional socket install.
var url=’http://my_server_name:8080/groupserver/groupserver’;
// Or “var url=’https://my_server_name:8443/groupserver/groupserver’;” if you want to use HTTPS.
10. Enter the port number.
Specify the port number used by the Primavera Group Server. By default
the port is 9002. This number is used to create a Windows socket
(Winsock) connection between the Primavera Group Server and the Java
application server. If your organization uses a firewall, this port must
be opened for Internet use.
NOTE: If you use a port number other than 9002, you must edit the WEB.XML
file, as described later in this document.
11. Enter the URL for Java Web Start (JAWS)
To allow users to launch Timesheets via Java Web Start, you have to
enter the URL for the JAWS Web server. Enter the server IP address,
and change the folders if necessary.
11. Click Next to begin the installation.
Setup installs the Group Server and associated web site.
12. Click Test to test the connection.
If errors are reported, you can modify the connection string and retry
the connection. If connecting to Oracle through ODBC:
Provider=OraOLEDB.Oracle;Data Source=OracleServiceName
If connecting to Microsoft SQL Server through ODBC:
Provider=SQLOLEDB; Data Source=Machine Name; Initial Catalog=DatabaseSchemaName
DEPLOYING THE WAR FILE
======================
To deploy the war file to Tomcat, simply copy the groupserver.war
file to the webapps directory and start the application server.
When installing to WebSphere the application name is appended with an “_war”.
This needs to be changed manually to “GroupServer” in the Administrative Console.
Please refer to your Tomcat, WebLogic or WebSphere documentation for detailed
information about deploying webapps to these application servers.
CONFIGURING THE SERVLET
=======================
Once the GroupServer.war file has been expanded, you must edit
the WEB.XML file if either of the following conditions exists:
- the Primavera Group Server and Java application server do NOT
reside on the same machine
and/or
- the Primavera Group Server is NOT using port number 9002.
The WEB.XML file is located in the \groupserver\web-inf folder.
Configure the server and port number to point to the Group Server.
This is the location of the TPGS service that is configured during
the initial setup. From the WEB.XML file:
<init-param>
<param-name>server</param-name>
<param-value>TPGS_server_name</param-value>
</init-param>
<init-param>
<param-name>port</param-name>
<param-value>9002</param-value>
</init-param>
Some Java application servers do not expand WAR files to
deploy them. In this case, the WAR file must be manually expanded
so that the WEB.XML file can be configured.
KNOWN ISSUES
============
1. To enable clients to connect via HTTPS, the SSL certificate
must be installed on each client. This can usually be
accomplished by having the clients browse to the servlet URL
directly, for example, https://my_server_name/groupserver/groupserver,
and then select to view and install the SSL certificate. Also
securing the Group Server website (index.html) with the same
certificate will allow clients to attach seamlessly.
2. The GroupServer.war file has been fully tested under Weblogic 8.1.4 Express ISV, WebLogic 8.1 SP4, Tomcat 5.0.28 and
WebSphere v6.0.
3. If the main help file (Timesheets.htm) does not display properly
for a secure Web site when using Internet Explorer, deselect the
options “Use PCT 1.0″ and “Use TLS 1.0″ from Tools-> Internet
Options-> Advanced-> Security. Then, close the browser and log in
again.
|