3 Introduction

The intention of this operation manual is to provide system administrators sufficient background knowledge to install EWA net, configure it and handle usual problems and errors that may occur during EWA net setup, configuration and in daily operation. In order to do this an overview over the system architecture of EWA net and its core framework is given. The next sections describe general setup and configuration tasks. Additionally, details of some specific topics (like e.g. log information) are provided. A “Frequently Asked Questions” (FAQ) section completes this document.

However, it is not (and cannot be) the aim of this document to provide guidelines to resolve problems originating from third party components like problems setting up an application server or a database system on several Windows OS environments, configuring firewalls to allow user access, integrating EWA net in other environments (Web- or Application Servers other than the ones supported), running several versions of programs (e.g. several versions of the Java Runtime Environment) at the same time etc.

3.1 “EWA net Central” vs. “EWA net local”

EWA net is a server based, distributed application. There are two main differences in the application deployment which will be called “central” and “local” – you will notice these terms often within this document.

Central: this installation type means a centrally hosted server environment which is typically used not only for a single workshop but i.e. for a whole market as Internet based application. Installation and Updates will be performed by experienced system administrators. The server and database software is somehow more advanced (and typically needs separate licensing) then the software from the “local” environment.

Local: this type of installation typically refers to an installation within a local workshop. It has other needs for installation, maintenance and performance. Installation and Updates will be supported by automatic processes. And the software requirements are not as “challenging” as the ones for the “central” environment.

3.2 Target audience

This document has been written for system administrators with at least basic knowledge of

• Windows (incl. Server) operating systems
• Java and Java Runtime Environments. You should know what an exception is and how to follow a stack trace
• XML concepts and editing XML files
• SQL language in general

3.3 Definitions

Following definitions shall help to describe the installation from a more generic view. These definitions or properties do not have to be available as operating system variables. They shall just provide some kind of abstraction throughout this documentation.

The following text will refer to these definitions as [property].

Example:
A “[EWA_HOME]\config” path will have to be expanded by you for your local settings to i.e. “C:\EWA_net\config”.

3.4 Terms

This section lists some terms that are being used within this document.

4 System Software

4.1 Automatically installed system software

Following table gives more details about the system software that will be automatically installed and used by EWA net:

4.2 System software to be installed manually

5 System Overview

5.1 Application modules

The applications “EPC net, WIS net and ASRA net (EWA net)” consist of several components rather than of a monolithic program block. Most of these components are located on a server but there are also program modules needed on the client. All of these components base on Java technology.

5.1.1 EWA net core framework

The EWA net core framework consists of several services and components and runs on the J2EE application server. These components will be described in detail in the following sections. This framework is often simply refered as “EWA net Core”.

• Access Gateway
  The Access Gateway forms the central part of the EWA net Server. It receives all requests from web clients, checks their validity and communicates the request to the according application or component.
• access authorization Manager
  The access authorization Manager verifies current access authorizations. It receives requests from the Access Gateway servlet and sends a result object back to the servlet. Depending on your license that you got from Daimler this engine also controls your set of licenses in a “license pool” which allows sharing a restricted set of licenses between different users.
• HP Services
  The HP Services provide different functions, which can be accessed by all applications. It consists of one file based service - the Configuration service - and some other mainly database based services.
  • Configuration Service
    The Configuration Service receives requests from any component or application. It provides a mechanism to read corresponding configuration files on disk and to return information back to the receiver, so that the applications can configure themselves.
  • Access Gateway Service
    The Access Gateway Service gets requests from the Access Gateway servlet. It is able to read, store and delete user and session information into a database.
  • Accounting Service
    The Accounting Service gets requests from the EPC- and WIS net applications. It stores the current time and accessed documents for a certain user. This data could for example be used for billing.
  • Log Service
    The Log Service receives data from any application or component. Depending on the debug level different information is logged into the filesystem (or other data sinks), like error messages, warnings or debug information. The Log Service is also available in the clients to unify logs on the server side.
  • Profile Service
    The Profile Service reads, writes or overwrites sender specific data into a database. Using this service, applications are able to store certain objects, e.g. like a shopping basket.
  • HP User Management Service
    This special user management service runs standalone and is one of several options of an authentication and authorization method. For that it does not need any other external component such as StarTek-Info. It can be configured to run instead of using the StarTek-Info user management or any other external user management. Users and user related information are stored in a local database .

5.1.2 EWA net application components(Client software)

The following applications and components are integrated into the application server and form the EWA net application together with the EWA net core framework. These components are only explained in brief here. If more information is required, please refer to the according documentation.

• WIS net
  The WISnet system stands for ‘Workshop Information System’ and consists of a server application, client applications and a TransBase database. In general it is a retrieval system to extract all kind of service literature from Daimler vehicles.
• EPC net
  The Electronic Parts Catalogue for provides information on all possible parts of all kinds of Daimler vehicles. The architecture is similar to WISnet.
• EWANAPI (formerly called WISAPI)
  This application is a downwards compatible replacement of the WISAPI.exe program allowing interaction to the WIS net and EPC net client applications from i.e. Dealer Management Systems.

5.2 Workflow

Some components (Access Gateway, User Management, Accounting Service, etc.) are used by both applications (EPC net and WISnet).  The configuration of these components has to be done only once.

In the following picture a normal workflow for EWA net is shown:

Figure: Workflow for EWA net

The data flow within EWA net is as follows:

1. The user normally logs in to the system via a Web interface. This interface communicates with the server (User Management) to validate the user data. Depending on the configuration the user data is checked against the own database ( default after installation).
2. If the user data are accepted a ticket (valid session info) is generated and the (Java-) Client-Application is started where this ticket is passed as a startup parameter.
3. The Client-Application does not communicate directly to the server-side business logic of the application. Instead the requests are pre-processed by the Access Gateway, which checks the ticket (Session information) and passes the request to the server logic of EPC or WISnet if the ticket is valid.
4. The Access Gateway gets information about several user data (as user specific application configuration, information access rights etc.) from the User management and also sends this information to the server logic. Therefore, it is necessary to always set up the User management database even if user authentication is handled by another directory service (e.g. Corporate directory).

Apart from User profiles and User configuration this database is also used to store log entries for error detection (if configured) and user specific access information for billing purposes.

In order to manage User information, a Web user interface is offered. It provides an easy way to add and delete users and licence information in the database. This interface is described in a separate document.

5.3 Clustering and loadbalancing

See the chapter about advanced system configuration for clustering and loadbalancing information.

5.4 Database replication

Different DBMS options are being used within the EWA net environment. The Transbase DBMS is typically being used as read-only database (for WIS net and EPC net) where there should be no need for database replication. The Transbase DBMS currently does not support replication mechanisms.

For the user management database storing user related information, a third instance of Transbase DBMS is being used. As the "local" EWA net is mainly aimed for small workshop environments it should be sufficient to run this database without clustering.

C-JDBC might be a helpful tool allowing at least read-only clustering even of the not-clustering-aware Transbase DBMS. Testing C-JDBC together with EWA net was however not part of the scope. See http://c-jdbc.objectweb.org

6 Requirements

6.1 Delivery Media

For the installation to take place, you need at least following items:

• A set of DVDs containing EWA net and the EPC net database files (typically 2 DVDs (9) for an official set of DVDs, or 3 DVDs (4.7) for pilot versions)
• A set of DVDs containing EWA net (typically 1 DVD (9) for an official release, or 2 DVDs (4.7) for a pilot version)
• The correct access authorization key(s) for the software from Daimler AG. You will be able to install the software components before you’ve got the access authorization keys, but you will be enforced to enter the access authorization keys before setting up the databases. And the system will not run without the databases being set up.

6.2 Software   

As mentioned in the previous chapter the EWA net server and client components are completely based on Java.

The components on the client side are started by means of “Java Web Start”. Starting with Java 2 (jre-packages 1.4 and above) “Java Web Start” is part of the “Java Runtime Environment” installation.

Apart from a Web-Browser (like Internet Explorer) and a working JRE (which in turn includes Java WebStart) there are no other software requirements on the client side. Installation of the EWA net client components is done automatically via “Java Web Start”.

On the server side a Web-Server, a Servlet Container (or J2EE Application Server), an installed user database, the EWA net core framework and the applications including the according application databases need to be installed.

For EWA net “central” Tomcat or Websphere serves as Web- and Application server. MS SQL is used as the database for user information. Web-Archives (.war) files contain the program logic for the Access Gateway, User management, WIS net and EPC net. Program modules within these Web-Archives are being executed by the servlet container (Webspere) each time a request is sent by a user.

For EWA net “local” TomCat serves as Web- and Application server. TransBase is used as the database for user information. Web-Archives (.war) files contain the program logic for the Access Gateway, User management, WIS net and EPC net. Program modules within these Web-Archives are being executed by the servlet container each time a request is sent by a user.

Additionally, two Transbase databases are being used, one for WIS net and another one for EPC net.

Other services and programs used for instance by EPC FP and WIS classic (like the access authorization Service, Program Manager etc.) are not required for EWA net.

Since some of the mentioned server components do only run on a Windows environment, it is necessary to use Windows as the server side operating system.

6.2.1 Application server / Database server machine

[EWA-HOME]\client-apps\jre\jre.exe

6.2.2 Client machines

The client machines will not be covered by the installation process. But in order to allow execution of the client software, following software must be installed on the client systems:

[EWA-HOME]\client-apps\jre\jre.exe

6.3 Hardware

The hardware requirements for the EWA net servers have to take two things into account.

• The above mentioned software requirements.
• The number of users accessing EWA net.

This section is intended to give a general reference that has to be adjusted individually for the environment the individual setup is intended to run in. For detailed and more recent requirements please check the Rollout Plan provided by Daimler AG.

Table: EWA net Server Hardware

Table: EWA net Client Hardware

Five default configuration types have been defined:

1. Central/Big, EDC approved:
   Limited PAI 3.0 platform compliance; central installation at the EDC/ADC for large number of users with a network connection to the EDC/ADC; PAI-compliant application server and write database
2. Central/Big, non-EDC installation:
   Central installation for large number of users connected via Internet, Intranet, Extranet, VPN; custom application server and write database
3. Central/Small:
   Central installation for limited number of users connected via Internet, Intranet, Extranet, VPN; modified standard EWA net server installation (extended database)
4. Local/Big:
   Workshop-central server for local LAN clients and workshop subsidiaries; standard EWA net server installation, modifications for failure safety possible; no Internet connection
5. Local/Medium-Small:
   Standard EWA net installation on single PC or Workshop server (PC); no Internet connection

The following hardware configurations have been defined:

Since EWA net does not differ to other Web applications in this respect the same guidelines apply.  As a general rule it can be said that the amount of system memory is more important than the power of the CPU.

6.4 Network

• Fixed IP Addresses (no DHCP) for the application server and system database machine are recommended to be used to prevent problems with name resolving.
• Open ports like specified below:

7 Installation

This chapter covers the installation steps for the application server, the database and the EWA net core framework (including Access Gateway and User management).

7.1 EWA net “local”

7.1.1 Run the installer

EWA net local will be installed on the local hard disk of the server containing all application components for the local environment. If a previous local version was already installed, the installer will stop when called in such an environment and ask you to make use of the Update program "AdminTool" (you will learn about this later on).

Installation

Login to Windows as Administrator or user who is part of the Administrators group.

Take your DVD of the EWA net DVD release set and execute the setup file from

[DVD-DRIVE]:\ewa\setup.exe

In our example installation our path was set to “C:\EWA_net”. If you use a different path for your installation, the given command and configuration examples need to be adopted to your folder structure. By default the installer suggests the installation into the Windows standard program files folder - which is perfect for "local" EWA net installations.

During the installation you get the information what steps are installed at this time.

The installation should finish without any error messages.

7.1.2 Check the services

After the installation you will find some new links within the Favorites of your Internet Explorer

With the EWA Admin Tool you should now check the services.

The tab "Core" must display two green traffic lights, the traffic lights in the tabs "EPC net" and "WIS net" will remain dark until you installed the database content.

7.1.3 Register the access authorization(s)

For licensing open the EWA net website (use the favorite in Internet Explorer to do so. If you performed an standard installation, you might also click here).
You will be asked for a username and password. On an initial installation these values will be

Admin Username = admin
Admin Password  = admin

Note:
You will immediately be asked to change your password now. Ensure you remember what you enter here.

Under the Button “Administration/Server Management/Server access authorization” you will find the input fields for the StartKey.

7.1.4 Add a first Group and first User

Please refer to the UserManagement manual to setup users and groups to be able to work with the system. To complete the basic installation you don't need to do this right now.

7.2 Install database content from DVDs

Retrieval Database content installation (for WIS net and EPC net) as well as whole EWA net system updates will be performed by the EWA Admin Tool. This is a windows executable that gives you an administrative interface to some system tasks like services control, software update, database clean up, ...

You will find this tool after installation in the “Favorites” in the folder “EWA net” of your Internet Explorer.

For detailed information please refer to the corresponding EWA Admin Tool documentation. ‎It describes in detail how to install new database content for both EPC net and WIS net.

7.4 Quick check of the installation

7.4.1 Check on the server

In order to verify whether all components have been correctly installed and configured it is now time to reboot your system. After having rebooted, start the Internet Explorer.

In order to check the  functionality of the administration go to the following URL:

http://localhost:9000/EWA-net

or use the “EWA net” Favorite in “EWA net” folder of the Internet Explorer. You should see the EWA net start page. Log in as administrator - this is currently the only user being setup in the system.

The default Admin user name and password are set by the installers to:

• User name : admin
• Password  : admin

7.4.2 Check on the client

If you want to check whether your clients are well prepared to perfectly run EWA net, please assure the following manually steps have been completed as there are no automatic installation steps for the client:

• Assure that a “ping <servername>” command to your EWA net server is successful from the clients you want to run EWA net on, where <servername> has to be replaced by the name of your EWA net system server.
• Assure that your Proxy settings in Internet Explorer are correct and you can access the EWA net server when pointing it to http://<servername>:9000/EWA-net
• Install the correct Java Runtime Environment from Sun Microsystems. Use the one provided on the delivery media of EWA net or assure that a supported JRE is already installed.
  You can easily find out about this feature if you open the Internet Explorer, log in as administrator and go to the "Download" section.
  
  A small Active/X script will check your client for a supported Java Runtime. If - due to security restrictions - this code cannot be executed, please check your Software control panel for the correct Java Runtime.
• If you need to install a JRE, please simply download and install the one provided in the "Download" section of EWA net.
  
• Assure that you do not install any other Java Runtime after installing the one for EWA net.
• To easily determine whether also your WebStart Environment is setup correctly, click onto the EWANAPI "Download / Install" button to make the EWANAPI client installer run.
  
  If it shows its GUI correctly, just close that installer and you will be fine. Nothing happened on the client. If the test failed, you should open the WebStart Control Panel and see that the Proxy configuration matches your environment.

Congratulations!

You have successfully setup a standard EWA net server. To configure the system to your needs (i.e. make use of a different authentication system), please refer to the chapters about EWA net configuration and advanced configuration to make the best out of your installation.

8 EWA net Configuration

Many of the settings below can easily be configured via the administrative Web interface of EWA net. But there is even more that can be performed by modifying the underlying XML files.

Important Note:
As mentioned earlier you should have reasonable experience and a good understanding of XML before you start editing the files mentioned below. You may easily make your EWA net server fail to start even with small syntactical errors in the files.

8.1 EWA net Application Server Settings

Note:
Some basic settings described here (like email Server, access authorization reminder, feedback,...) can also be modified by a user with System Administrator user role from within EWA net's server administration masks.

8.1.1 core_cfg.xml

The behavior of the AccessGateway and each HP Service can be configured in the [EWA_HOME]\config\core_cfg.xml file.

Example:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<xml>
    <SECTION name="Services">
        <SECTION name="MailService">
            <!-- Parameter emailEnabled: Set this to "true" or "false" if the Email Service is active and -->
            <!--                         sending Emails.                                                  -->
            <PARAMETER name="emailEnabled">true</PARAMETER>
(...)
</xml>

Table: core_cfg.xml

8.1.2 license.xml

Location: [EWA_HOME]\config\license_cfg.xml

This configuration file contains the server access authorizations for EPC net and WIS net of the EWA net application server.

Example:

<?xml version="1.0" encoding="UTF-8"?>
<xml>
<SECTION name="Licenses">
     <PARAMETER name="wis">J9GF4AXXXXXXX...</PARAMETER>
     <PARAMETER name="epc">ZYVND3XXXXX...</PARAMETER>
</SECTION>
</xml>

Table: Section "Licenses"

Note:
If your server run several redundant LAN adapters you might get server access authorizations for each of these LAN adapters and add those access authorizations comma or semicolon separated here to support high availability.

8.1.3 um_cfg.xml (and um_batch_cfg.xml)

These files are located at [EWA_HOME]\config\um_cfg.xml

These configuration files contains all configuration concerning user management. The file um_cfg.xml is used for online authentication whereas um_batch_cfg.xml contains the configuration for batch calls as they are used for instance by “EWANAPI.exe”. Within the config files it is defined which authentication mode to use and what the connection parameters to the authentication / authorization datastores look like.

Example:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<xml>
    <SECTION name="General">
        <!-- Type of user management; valid Entries are: StarTekInfo, HPUserManagement -->
        <PARAMETER name="userManagementService">HPUserManagement</PARAMETER>
(...)
</xml>

Table: Section "General"

Contents of section “CorporateDirectory”:

• The following section “CorporateDirectory” is only used, if in the previous section “CorporateDirectory” was selected as authentication mode.
• All data is issued by those persons within Daimler, who are responsible for the Corporate Directory

Table: Section "CorporateDirectory"

Contents of section “LDAP"

• The following section “LDAP only used, if in the “General” section “LDAP” was selected as authentication mode.

Table: Section "LDAP"

For more information about the LDAP configuration, please see the chapter about User Management configuration.

8.1.4 additional_downloads_cfg.xml

This is an optional file which will neither be installed by the installer nor be updated or modified by any software installation process. Thus if you want to integrate your own download sections within EWA net's download section please follow this short description and have a closer look into an example file which will show you how to customize your environment in respect to download options.

The configuration file will be read each time the download page will be shown so you may customize it without the need of restarting the EWA net server.

The file must be created and stored within the [EWA_HOME]\config folder with the given name additional_downloads_cfg.xml.

The basic structure of the file is as this:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<xml>
    <!-- Section to enter further downloads to the download area -->
    <SECTION name="AdditionalDownloads">
    ....
    </SECTION>
</xml>

What we have created up to now is an extension of the downloads section with exactly 0 new entries. So we need to add the subsections which will show up inside the download area. We add an enumeration of sections called "AdditionalDownload_x" where x is a number from 1 to the number of sections you want to add.

Example:

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<xml>
    <!-- Section to enter further downloads to the download area -->
    <!-- UserRoleForApplication can take more than one value, the roles should be comma separated -->
    <!-- The valid values for UserRoleForApplication are: ServerAdmin, WorkshopAdmin, WorkshopUser -->
    <!-- The default value for UserRoleForApplication is WorkshopUser, WorkshopAdmin, ServerAdmin -->
    <SECTION name="AdditionalDownloads">
        <!-- Start your enumeration with value "_1" and enumerate your keys from there -->

        <SECTION name="AdditionalDownload_1">
            <!-- Description can be provided multiple times if you want to specify descriptions in different languages -->
            <!-- But then ensure there is at least one default text without "locale=" specification -->
            <PARAMETER name="Description" locale="en">This text will show up in anglish &lt;br&gt;if browser requests english</PARAMETER>
            <PARAMETER name="Description" locale="de">Dieser Text erscheint in Deutsch wenn der Anwender Deutsch als Sprache eingestellt hat</PARAMETER>
            <PARAMETER name="Description">This is the default text which will show for all other browser languages. We better use English here :)</PARAMETER>
            <!-- Location to download, absolute path or, by use of URL-Rewriting, a relative EWA net Server reference -->
            <PARAMETER name="URLofDownload">http://www.hp.com</PARAMETER>
            <PARAMETER name="LinkText" locale="en" >Have a closer look on the HP Page i.e. for Driver Updates</PARAMETER>
            <PARAMETER name="LinkText" locale="de" >HP Download Seite</PARAMETER>
            <PARAMETER name="LinkText">HP Download Page</PARAMETER>
            <!-- User Role that has access to this download. If not specified, all users may have access to it -->
            <PARAMETER name="UserRoleForApplication">WorkshopUser, WorkshopAdmin, ServerAdmin</PARAMETER>
        </SECTION>

        <SECTION name="AdditionalDownload_2">
            <PARAMETER name="Description">The link for the EWANAPI Installer provided here again</PARAMETER>
            <!-- Location to download, absolute path or, by use of URL-Rewriting, a relative EWA net Server reference -->
            <PARAMETER name="URLofDownload">/EWA-net/ewanapi_installer.jnlp</PARAMETER>
            <!-- Shall we include/do we need to include session information in the URL? Default: false -->
            <PARAMETER name="URLdoRewriting">true</PARAMETER>
            <PARAMETER name="LinkText">EWANAPI Installer (again)</PARAMETER>
        </SECTION>

        <SECTION name="AdditionalDownload_3">
            <PARAMETER name="Description">Download and run a setup located at [EWA_HOME]\downloads\test\Setup.exe</PARAMETER>
            <!-- Location to download, absolute path or, by use of URL-Rewriting, a relative EWA net Server reference -->
            <PARAMETER name="URLofDownload">/EWA-net/download/downloads/test/Setup.exe</PARAMETER>
            <!-- Shall we include/do we need to include session information in the URL? We MUST use session information to allow access to download below the "downloads" directory-->
            <PARAMETER name="URLdoRewriting">true</PARAMETER>
            <PARAMETER name="LinkText">Some sample Setup</PARAMETER>
        </SECTION>

    </SECTION>
</xml>

Following parameter tags can be used:

• Description:
  This element may occur several time and can be localized by specifying a respective "locale" attribute. If no "locale" attribute is given, this text will be chosen as fallback to be displayed as description text in the download area. If the browser provides a preferred locale and a description with this locale can be found it will be used in favor of the fallback description. See the example above.
• URLofDownload:
  This is a URL which shall be referred to. You may want to redirect to another, external URL i.e. just to point to a different location, to open up an HTML document from a different location, make the user download a file from an external source.
  Or you may want to publish your own downloads within the [EWA_HOME]\downloads directory.
  If you want to do the latter, just create a subdirectory below the downloads directory, i.e. downloads\test. Inside this directory you may want to publish a file called Setup.exe. You may then simply create a URL now which then always begins with /EWA-net/download/downloads and then gets extended by the directory structure below the downloads directory. In the given example the resulting URL would look like this:
  /EWA-net/download/downloads/test/Setup.exe
• URLdoRewriting:
  This is basically optional and by default (if not given) set to "false". Valid values are "true" and "false".
  If you want to allow users to download from the EWA net "downloads" directory you must set this value to "true". EWA net does not allow anonymous downloads for security reasons!
• LinkText:
  This is the text that will shown instead of the pure URL. It can be localized in the same way as the Description. It will show up in the right column within the download overview.
• UserRoleForApplication:
  This is also an optional field. If not given, unrestricted access is given to all EWA net users. Following values may be used for restriction:
  - ServerAdmin: Only Server administrators may access this URL
  - WorkshopAdmin: Only Workshop admins may access this URL.
  - WorkshopUser: Only normal Workshop users may access this URL.
  You can combine the user roles by separating them via a colon like this: WorkshopUser, WorkshopAdmin

The example from above will result in a download area extension like this:

8.2 Feedback

8.2.1 Introduction

EWA net is offering you in a joint effort with the project Customer Support & Feedback (XSF) a new approach in delivering your feedback (corrections of documentation, improvements, handling problems etc.) to the proper parts of the After Sales organization. The problem areas generally occurring in the workshop are clearly defined by so called event categories.

The implementation will happen in three phases which will decrease your handling time by automatically collecting context information (e.g. FIN, motor number, part number etc.) and increase step by step your ability to track the processing of your question within the organization.

1. In the first phase EWA net offers in default configuration automatically generated Faxes. But you can also choose an E-Mail solution which will send your questions to either a pre-defined central Mail address (recommended solution) or alternatively you can configure special Mail-addresses.
   
   Recommended Feedback modes: email, fax
    
2. In the second phase (starting from 01-July-2006) EWA net will be able to automatically open a ticket in the central XSF-System if you have Internet Access. The access to XSF will be limited to certain event categories. In XSF you can track the status of your ticket. Fax and E-Mail are still possible.
   
   Recommended Feedback modes: email, fax, email-or-fax, XSF-email, XSF-fax
    
3. In the third phase (starting from 01-April-2007) all categories (including MB parts) will be exclusively handled via XSF. Fax is still available as an alternative if you have no Internet Access.
   
   Recommended Feedback modes: xml-post,  (email), fax

8.2.2 Technical decision tree

The following decision tree shall help you to find the best mode for feedback:

8.2.2.1 Feedback Channel: Fax

8.2.2.1.1 Preconditions

This type of Feedback channel provides the lowest level of integration and process benefit, but is the one that is expected to work almost everywhere - this is why it has been chosen as default configuration. Please choose this channel in case

• you do not have permanent internet access on the side of the EWA net server.

• you do not know where you could send Feedback generated emails to or no process has been setup.

In this case the only feasible option to be used is fax. This mode will automatically assemble all the relevant context information from the client applications (EPC net, WIS/ASRA net), create a printout with feedback information from the client and allow this printout to be faxed. The printed fax will contain the correct fax number to send this fax to.

8.2.2.1.2 Configuration

Steps to be performed on the server side for this configuration are:

1. Go to the [EWA_HOME]\config directory

2. core_cfg.xml: Set the feedback "Modus" parameter to fax.

3. Make a copy of the file feedbackRecipients.xml as faxRecipients.xml.  This should be done to avoid that a software update will override the file.

4. Edit the file and change the default value of the parameter <fax> to the value of your choice where you want/must send your feedback information to.
   Example: <fax>+49 (711) 17-12345</fax>

5. core_cfg.xml:
   Set the feedback file reference parameter "RecipientsConfigFile" to the new filename you have chosen to create above like this:
   <PARAMETER name="RecipientsConfigFile">faxRecipients.xml</PARAMETER>

6. Restart your EWA net server and give feedback a try.

8.2.2.2 Feedback Channel: Email

8.2.2.2.1 Preconditions

This type of Feedback channel provides a better integration and process benefit, but can only be used if some preconditions can be met. Please choose this channel in case

• you do have permanent internet access on the server side.

• you have access to an SMTP server - a correctly working EWA net Email configuration is needed and will allow you to test this.

• the SMTP standard TCP/IP port 25 is correctly configured in any firewalls on the way to the SMTP server.

If these requirements can be met you may choose  email as your Feedback Channel. This mode will automatically assemble all the relevant context information from the client applications (EPC net, WIS/ASRA net) and create a feedback email in a specific format. Users will not have.

8.2.2.2.2 Configuration

Steps to be performed on the server side for this configuration are:

1. Go to the [EWA_HOME]\config directory

2. core_cfg.xml: Set the feedback "Modus" parameter to email.

3. Ensure that the EWA net email service (Parameter "MailService" is up and running and setup correctly. You may test it via the "Messaging" option of EWA net.

4. Email recipients - option 1:
   If your country is setup in the global Daimler Email router for Feedback (please get in contact with your MPC about that) you may simply use the functionality of that email router by setting the property "FeedbackEmail" in the core_cfg.xml to the value: test.gspsupport@daimler.com

5. Email recipients - option 2:
   If you want to setup your own Email routing to different locations you may want to make use of the advanced features of EWA net's Feedback. In this case please make a copy of the file feedbackRecipients.xml as emailRecipients.xml and adjust the file core_cfg.xml:
   Set the feedback file reference parameter "RecipientsConfigFile" to the new filename you have chosen like this:
   <PARAMETER name="RecipientsConfigFile">emailRecipients.xml</PARAMETER>.
   Edit the file according to the description of the feedbackRecipients.xml file.

6. Restart your EWA net server and give feedback a try.

8.2.2.3 Feedback Channel: Email-or-Fax

8.2.2.3.1 Preconditions

This type of Feedback channel is an automatic switch between Fax and Email depending on the setup of your feedbackRecipients.xml file which works like a decision matrix. Basically the same preconditions as for email and fax (see above) apply here.

Basically you will only want to do this if you have the full responsibility of different fax channels and you are not able to use the global email router or one single fax number for feedback.

If these requirements can be met you may choose  email-or-fax as your Feedback Channel mode.

8.2.2.3.2 Configuration

Steps to be performed on the server side for this configuration are:

1. Go to the [EWA_HOME]\config directory

2. core_cfg.xml: Set the feedback "Modus" parameter to email-or-fax.

3. Ensure that the EWA net email service (Parameter "MailService" is up and running and setup correctly. You may test it via the "Messaging" option of EWA net.

4. As you want to setup your own Email and Fax routing to different locations you will want to make use of the advanced features of EWA net's Feedback. In this case please make a copy of the file feedbackRecipients.xml as recipients.xml and adjust the file core_cfg.xml:
   Set the feedback file reference parameter "RecipientsConfigFile" to the new filename you have chosen like this:
   <PARAMETER name="RecipientsConfigFile">recipients.xml</PARAMETER>.
   Edit the file according to the description of the feedbackRecipients.xml file.

5. Restart your EWA net server and give feedback a try.

8.2.2.4 Feedback Channel: XSF-email

8.2.2.4.1 Preconditions

You may use this option only once the XSF project has reached phase 2 (planned for 01-July-2006) and you received an official Go! to use XSF features - please reconfirm with you local MPC.

This type of Feedback channel is an automatic switch between XSF functionality and Email as a fallback depending on the setup of a fixed central decision matrix feedbackTransfer.xml file provided by Daimler (for the selection whether XSF can be used for a specific event type or the email functionality shall be chosen) and the file feedbackRecipients.xml  which in case of the email fallback selects the appropriate email address.

Summary of requirements:

• XSF project has reached phase 2

• Server has permanent Internet access (needed for email)

• Email Service of EWA net is correctly configured and working

• Clients have permanent Internet access on ports 80 and 443 (needed to send data via XSF channel).

• Check whether users have access rights to TIPS. Please apply for additional rights for XSF. If access rights do not exist at all, please check with your local MPC if you are already registered with the GSSN.

If all these requirements can be met you may choose  XSF-email as your Feedback Channel mode.

8.2.2.4.2 Configuration

Steps to be performed on the server side for this configuration are:

1. Go to the [EWA_HOME]\config directory

2. core_cfg.xml: Set the feedback "Modus" parameter to XSF-email.

3. Ensure that the EWA net email service (Parameter "MailService" is up and running and setup correctly. You may test it via the "Messaging" option of EWA net.

4. As you will want to setup your own Email routing to different locations you will want to make use of the advanced features of EWA net's Feedback. In this case please make a copy of the file feedbackRecipients.xml as emailRecipients.xml and adjust the file core_cfg.xml:
   Set the feedback file reference parameter "RecipientsConfigFile" to the new filename you have chosen like this::
   <PARAMETER name="RecipientsConfigFile">emailRecipients.xml</PARAMETER>
   Edit the file according to the description of the feedbackRecipients.xml file.
   
   

5. Restart your EWA net server and give feedback a try.

8.2.2.5 Feedback Channel: XSF-fax

8.2.2.5.1 Preconditions

Like the option XSF-email you may use this option only once the XSF project has reached phase 2 (planned for 01-July-2006) and you received an official Go! to use XSF features - please reconfirm with you local MPC.

This type of Feedback channel is an automatic switch between XSF functionality and Fax as a fallback depending on the setup of a fixed central decision matrix feedbackTransfer.xml file provided by Daimler (used for the selection whether XSF can be used for a specific event type or the fax  functionality shall be chosen) and the file feedbackRecipients.xml  which in case of the fax fallback selects the appropriate fax number.

Summary of requirements:

• XSF project has reached phase 2

• XSF project has not yet reached phase 3 - where the preferred channel will be the direct use of the XSF application.

• Clients do have physical access to a printer.

• Clients have permanent Internet access on ports 80 and 443 (needed to send data via XSF channel).

• Check whether users have access rights to TIPS. Please apply for additional rights for XSF. If access rights do not exist at all, please check with your local MPC if you are already registered with the GSSN.

If all these requirements can be met you may choose  XSF-fax as your Feedback Channel mode.

8.2.2.5.2 Configuration

Steps to be performed on the server side for this configuration are:

1. Go to the [EWA_HOME]\config directory

2. core_cfg.xml: Set the feedback "Modus" parameter to XSF-fax.

3. As you will want to setup your own Fax  routing to different locations you will want to make use of the advanced features of EWA net's Feedback. In this case please make a copy of the file feedbackRecipients.xml as faxRecipients.xml and adjust the file core_cfg.xml:
   Set the feedback file reference parameter "RecipientsConfigFile" to the new filename you have chosen like this:
   <PARAMETER name="RecipientsConfigFile">faxRecipients.xml</PARAMETER>.
   Edit the file according to the description of the feedbackRecipients.xml file.

4. Restart your EWA net server and give feedback a try.

8.2.2.6 Feedback Channel: xml-post

8.2.2.6.1 Preconditions

This option may only be used once the XSF project has reached phase 3 (planned for 01-April-2007) and you received an official Go! to use XSF features - please reconfirm with you local MPC.

This type of Feedback channel allows full integration of EWA net's Feedback module with the XSF project.

Summary of requirements:

• XSF project has reached phase 3

• Clients have permanent Internet access on ports 80 and 443 (needed to send data via XSF channel).

• Check whether users have access rights to TIPS. Please apply for additional rights for XSF. If access rights do not exist at all, please check with your local MPC if you are already registered with the GSSN.

If all these requirements can be met you may choose  xml-post as your Feedback Channel mode.

8.2.2.6.2 Configuration

Steps to be performed on the server side for this configuration are:

1. Go to the [EWA_HOME]\config directory

2. core_cfg.xml: Set the feedback "Modus" parameter to xml-post.

3. Restart your EWA net server and give feedback a try.

8.2.2.7 Advanced features of the feedbackRecipients.xml

As described above the standard software setup of EWA net provides a simple, but useful feedbackRecipients.xml file which contains a global fax number and a global email address for you to be used unless you need more advanced features. This file will be updated by the software installation processes and thus might override any changes you have made within it.

Therefore it is highly recommended (as described above) that once you start editing it you make a copy of it in the config folder of EWA net and update the reference to the file within the core_xfg.xml file's parameter "RecipientsConfigFile". This ensures that your changes will not be destroyed by a software update.

The file initially looks like this:

<?xml version="1.0" encoding="ISO-8859-1"?>
<feedback-recipients xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="feedbackRecipients.xsd">
    <default preferred="fax">
        <email>test.gspsupport@daimler.com</email>
        <fax>+49-711-17-0</fax>
    </default>
</feedback-recipients>

You may want to simply change the default values for the recipients of fax or email by editing the fax or email elements.

But there is more that you can do with this file. The file may serve as an advanced decision matrix on the following attributes:

1. Country:
   This is the top level decision in the decision tree. It represents the country of the workshop of the current user. Country numbers are a Daimler/GSP definition and 3 digits in length (i.e. 200 for Germany). A list of all valid country numbers can be looked up in the file country_codes.xml.
   This feature allows country specific email addresses and/or fax numbers.

2. Workshop:
   The second level in the decision tree is the number of the Workshop the current user belongs to.

3. Feedback Event Category:
   This is the bottom level in the decision tree for the selected category of feedback that shall be provided. Following values are valid:
   A1: Datacard
   C1: Parts Query (EPC net)
   C2: Passenger Car Accessories
   D1: TIPS
   D2: Work Documentation (WIS net)
   D3: Operation Item (ASRA net)
   D4: Damage Codes
   E1: System Problems
   
    

To explain in more detail what the flexibility of this file is all about let's do a simple example:

 <?xml version="1.0" encoding="ISO-8859-1"?>
<feedback-recipients xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="feedbackRecipients.xsd">
    <country code="839" preferred= "email">
        <!-- we come here only if country of current user's workshop is Japan -->
        <category code="C1" preferred= "fax">
            <!-- we come here only if the user selected "Parts Query" in Feedback as event category --> 
            <email>feedback1@dcx.jp</email>
            <fax>+81 (1) 1234</fax>
        </category> 
        <!-- We are in Japan, but no further criteria was matching -->
        <default preferred= "email">
            <email>feedback2@dcx.jp</email>
            <fax>+81 (1) 12345</fax>
        </default>
    </country> 
    <!-- we come here if nothing of the above matches -->
    <default preferred= "fax">
        <email>feedback@daimler.com</email>
        <fax>+49 (711) 12345</fax>
    </default>
</feedback-recipients>

Let's go through this example and explain the different options:

Toplevel we define a country element with code "839" which means that this is country "Japan". When Feedback steps down the decision tree it compares the users country code with the one it finds here. Assuming now the user is in Japan. Then feedback remembers that in case of the email-or-fax mode email is the preferred choice via the preferred attribute. The next level of decision was to check for workshop. But this optional level is omitted so feedback steps further down and checks the event category that the user has chosen. Assuming now he has pressed the Feedback button inside the EPC net client or has pressed the "Parts Query - EPC net" button on the feedback mask, Feedback will match this against the given code "C1" here - and this code really represents the "Parts Query" event category. Feedback now remembers at this point that in case of email-or-fax the preferred Feedback channel will be email. Feedback has resolved the information it needs and will work in the following way:

• Configured Feedback channel is "email" or "XSF-email":
  The given email (feedback1@dcx.jp) will be used and an email will be sent to this address.
• Configured Feedback channel is "fax" or "XSF-fax":
  The given fax number (+81 (1) 1234) will be used and be printed into the fax form.
• Configured Feedback channel is "email-or-fax":
  Feedback uses the information from the last read attribute "preferred" to determine which channel now to use. In our example from above the dynamically selected channel would have been "fax" and the information from the respective element would have been chosen.

Let's continue with this example. Assuming the user is in Japan, but would have chosen a different category - not the "Parts Query". Then feedback would have stepped into the "default" element within this workshop element and would have resolved the information from there.

Assuming the user is one located in Germany then already on the top level of the decision tree Feedback would have stepped into the global "default" section (the one at the bottom of the file) as no other matching workshop could be found. It would have resolved the information from there.

More advanced features:

• The "code" attribute of the XML elements country,  workshop and category allow you to specify multiple codes at once by separating them with a blank.
  Examples: <workshop code="000000 A302X C2020" preferred="fax">
  <country code="200 557" preferred="fax">
  <category code="C1 C2 D1 D2 D3 D4" preferred="email">
• The "email" element allows to specify more then one email address (if needed): just separate them by colons.
  Example: <email>email1@daimler.com,email2@dcx.com</email>

An even more complex configuration that could be used for example multi-country servers of EWA net may look like this:

<?xml version="1.0" encoding="ISO-8859-1"?>
<feedback-recipients xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="feedbackRecipients.xsd">

    <country code="200 557">
    <!-- we come here only if country of current user's workshop is Germany or Austria -->

        <workshop id="000000 A030X2">
            <category code="A1 C1" preferred= "fax">
                <email>feedback1@dcx.de</email>
                <fax>+49 (711) 17-12345</fax>
            </category>
            <category code="C2" preferred= "email">
                <email>feedback2@dcx.de</email>
                <fax>+49 (711) 17-123456</fax>
            </category>
            <!-- used for Austria or Germany and workshop either "00000" or "A030X2" but other feedback event category -->
            <default preferred= "fax">
                <email>feedback3@dcx.de</email>
                <fax>+49 (711) 17-12347</fax>
            </default>
        </workshop>

        <!-- used for all other workshops within Germany and Austria -->
        <category code="A1 C1" preferred= "fax">
            <email>feedback4@dcx.de</email>
            <fax>+49 (711) 17-12348</fax>
        </category>

        <default preferred= "fax">
            <email>feedback5@dcx.de</email>
            <fax>+49 (711) 17-12349</fax>
        </default>
    </country> 

    <country code="839" preferred= "email">
        <!-- we come here only if country of current user's workshop is Japan -->
        <category code="C1" preferred= "fax">
        <!-- we come here only if the user selected "Parts Query" in Feedback as event category --> 
            <email>feedback1@dcx.jp</email>
            <fax>+81 (1) 1234</fax>
        </category> 
        <!-- We are in Japan, but no further criteria was matching -->
        <default preferred= "email">
            <email>feedback2@dcx.jp</email>
            <fax>+81 (1) 12345</fax>
        </default>
    </country> 

    <!-- we come here if nothing of the above matches, so this is the "catch all" block -->
    <default preferred= "fax">
        <email>feedback@daimler.com</email>
        <fax>+49 (711) 12345</fax>
    </default>
</feedback-recipients>

<?xml version="1.0"?>
<!-- <!DOCTYPE export SYSTEM "wisconfig.dtd"> //-->
<WISCONFIGURATION>
    <SECTION name="imagecache">
        <!-- Size is given in Megabyte -->
        <PARAMETER name="maximumsize">128</PARAMETER>
    </SECTION>
    <SECTION name="pool">
        <SECTION name="co">
            <SECTION name="db">
                <PARAMETER name="driver">oracle.jdbc.driver.OracleDriver</PARAMETER>
                <PARAMETER name="url">jdbc:oracle:thin:@(DESCRIPTION=(ADDRESS_LIST=(ADDRESS=(PROTOCOL=TCP)(HOST=53.74.251.22)(PORT=1521)))(CONNECT_DATA=(SID=COL)(SERVER=DEDICATED)))</PARAMETER>
                <PARAMETER name="user">wisnet</PARAMETER>
                <PARAMETER name="password">wisnet</PARAMETER>
            </SECTION>
            <SECTION name="schema">
                <PARAMETER name="german">CASEONLINE_D</PARAMETER>
                <PARAMETER name="english">CASEONLINE_E</PARAMETER>
                <PARAMETER name="config">CO_STWS</PARAMETER>
            </SECTION>
            <PARAMETER name="size">5</PARAMETER>
            <PARAMETER name="pingstatement">select count(*) from dual</PARAMETER>
        </SECTION>
        <SECTION name="db">
            <PARAMETER name="driver">transbase.jdbc.Driver</PARAMETER>
            <PARAMETER name="url">jdbc:transbase://localhost:2054/wisnet</PARAMETER>
            <PARAMETER name="user">tbadmin</PARAMETER>
            <PARAMETER name="password"></PARAMETER>
            <PARAMETER name="size">5</PARAMETER>
            <PARAMETER name="pingstatement">select count(*) from Config</PARAMETER>
        </SECTION>
    </SECTION>

    <SECTION name="client">
        <!-- Java heap size of client in MB, default is 64 MB -->
        <PARAMETER name="heapsize">128</PARAMETER>
    </SECTION>

    <SECTION name="server">
        <PARAMETER name="codebase">WIS-net/html</PARAMETER>
        <PARAMETER name="helpbase">http://localhost:9000/WIS-net/online-help/html</PARAMETER>
        <PARAMETER name="languagebase">http://localhost:9000/WIS-net/html/resources</PARAMETER>
        <PARAMETER name="gateway">http://localhost:9000/EWA-net/ewa-net</PARAMETER>
        <PARAMETER name="language_preset">en</PARAMETER>
        <!-- debugLevel is on of ALERT, ERROR, WARNING, INFO or DEBUG -->
        <PARAMETER name="debugLevel">INFO</PARAMETER>
        <PARAMETER name="useMultiline">false</PARAMETER>

        <!-- Network/server version -->
        <PARAMETER name="webetmbase">http://localhost:9000/WIS-net</PARAMETER>

        <PARAMETER name="client_font_directory">c:\temp\</PARAMETER>
        
        <!-- activate/deactivate collection of performance data for statistic page -->
        <PARAMETER name="collectPerformanceData">true</PARAMETER>
        <PARAMETER name="datacardUrl">http://localhost:9000/EPC-net/datacardapi</PARAMETER>
    </SECTION>
    <SECTION name="casedirect">
        <PARAMETER name="rootdir">C:\temp</PARAMETER>
        <PARAMETER name="webserver">http://53.74.251.21:8080</PARAMETER>
        <PARAMETER name="proxyserver"></PARAMETER>
        <PARAMETER name="proxyport">80</PARAMETER>

        <SECTION name="cookie">
            <SECTION name="1">
                <PARAMETER name="path">/caseonline</PARAMETER>
                <PARAMETER name="name">caseonline_rechte</PARAMETER>
                <PARAMETER name="value">14634</PARAMETER>
                <PARAMETER name="domain">.daimlerchrysler.com</PARAMETER>
            </SECTION>
            <SECTION name="2">
                <PARAMETER name="path">/caseonline</PARAMETER>
                <PARAMETER name="name">caseonline_passwort</PARAMETER>
                <PARAMETER name="value">stws</PARAMETER>
                <PARAMETER name="domain">.daimlerchrysler.com</PARAMETER>
            </SECTION>
            <SECTION name="3">
                <PARAMETER name="path">/caseonline</PARAMETER>
                <PARAMETER name="name">caseonline_login</PARAMETER>
                <PARAMETER name="value">stws</PARAMETER>
                <PARAMETER name="domain">.daimlerchrysler.com</PARAMETER>
            </SECTION>
            <SECTION name="4">
                <PARAMETER name="path">/caseonline</PARAMETER>
                <PARAMETER name="name">caseonline_login</PARAMETER>
                <PARAMETER name="value">stws</PARAMETER>
                <PARAMETER name="domain">u10grz02.grz.mbcase.daimlerchrysler.com:8091</PARAMETER>
            </SECTION>
            <SECTION name="5">
                <PARAMETER name="path">/caseonline</PARAMETER>
                <PARAMETER name="name">caseonline_sprache</PARAMETER>
                <PARAMETER name="value">000</PARAMETER>
                <PARAMETER name="domain">u10grz02.grz.mbcase.daimlerchrysler.com:8091</PARAMETER>
            </SECTION>
        </SECTION>


    </SECTION>

    <!-- needed for G.07 configuration -->
    <SECTION name="caseonline">
        <SECTION name="mappings">
            <SECTION name="fzgart_table">
                <PARAMETER name="1">P</PARAMETER>
                <PARAMETER name="2">P</PARAMETER>
                <PARAMETER name="3">T</PARAMETER>
                <PARAMETER name="4">T</PARAMETER>
                <PARAMETER name="6">N</PARAMETER>
                <PARAMETER name="8">O</PARAMETER>
                <PARAMETER name="9">U</PARAMETER>
            </SECTION>
        </SECTION>
    </SECTION>

    <SECTION name="setup">
        <SECTION name="caseonline">
            <PARAMETER name="allowed">true</PARAMETER>
            <!-- true = merge WIS and CO docs, false = only show CO doc even if both exist -->
            <PARAMETER name="merge_wis">true</PARAMETER>
            <SECTION name="sync">
                <PARAMETER name="mainswitch">1</PARAMETER>
            </SECTION>
        </SECTION>
        <SECTION name="damagecode">
            <!-- Set to true to enable one-click navigation in damage code -->
            <PARAMETER name="oneclick">true</PARAMETER>
        </SECTION>
        <SECTION name="casedirect">
            <PARAMETER name="allowed">true</PARAMETER>
        </SECTION>
        <SECTION name="asra">
            <PARAMETER name="defaultJoborderFileName">C:\temp\MBCASE\joborder\joborder.txt</PARAMETER>
        </SECTION>
        <SECTION name="infotypes">
            <PARAMETER name="sti_code">-1</PARAMETER>
            <PARAMETER name="sti_name">F_WS_P_INFO_L_STI</PARAMETER>
            <PARAMETER name="structure">1;2,3,4|5;6,7,8,9,10,11|12;13,14|15;16,17,18,19,20,21,22,26,27|22;23,24,25|28;29,30,31,32,33</PARAMETER>
        </SECTION>
        <SECTION name="tasks">
            <PARAMETER name="task_id">1|2|3</PARAMETER>
            <PARAMETER name="tasks_rb">F_WS_P_INFO_SL_REPAIR|F_WS_P_INFO_SL_FUNCTIONALITYDESCRIPTION|F_WS_P_INFO_SL_DIAGNOSIS</PARAMETER>
            <PARAMETER name="tasks2dpyinfotypes">2,8,10|3,13|8,9,21,22,23,24,25</PARAMETER>
        </SECTION>
        <SECTION name="paperformat">
            <PARAMETER name="paperformat_names">A3|A4|Letter|Legal</PARAMETER>
            <PARAMETER name="paperformat_rb">F_SETUP_P_WS_PRINT_SL_A3|F_SETUP_P_WS_PRINT_SL_A4|F_SETUP_P_WS_PRINT_SL_LETTER|F_SETUP_P_WS_PRINT_SL_LEGAL</PARAMETER>
            <PARAMETER name="A3">29.7cm*42cm</PARAMETER>
            <PARAMETER name="A4">20.9cm*29.1cm</PARAMETER>
            <PARAMETER name="Letter">8.5in*11in</PARAMETER>
            <PARAMETER name="Legal">8.5in*14in</PARAMETER>
        </SECTION>
        <SECTION name="feedback">
            <PARAMETER name="subject">WIS Online Feedback Mail</PARAMETER>
            <PARAMETER name="fromuser">insert@sender.here.de</PARAMETER>
            <SECTION name="recipients">
                <PARAMETER name="CAT0">insert@recipient.here.de</PARAMETER>
                <PARAMETER name="CAT1">insert@recipient.here.de</PARAMETER>
                <PARAMETER name="CAT2">insert@recipient.here.de</PARAMETER>
                <PARAMETER name="CAT3">insert@recipient.here.de</PARAMETER>
            </SECTION>
            <SECTION name="hostconfig">
                <PARAMETER name="smtphost">danetis.is.danet.de</PARAMETER>
                <PARAMETER name="smtpuser">bpf</PARAMETER>
                <PARAMETER name="smtppassword">sagichnicht</PARAMETER>
            </SECTION>
        </SECTION>
        <SECTION name="fonts">
            <SECTION name="MODERN">
                <PARAMETER name="PLAIN.W32">Arial</PARAMETER>
                <PARAMETER name="BOLD.W32">Arial Bold</PARAMETER>
                <PARAMETER name="ITALIC.W32">Arial Italic</PARAMETER>
                <PARAMETER name="BOLD-ITALIC.W32">Arial Bold Italic</PARAMETER>

                <PARAMETER name="PLAIN.20.W32">MS Gothic</PARAMETER>
                <PARAMETER name="BOLD.20.W32">MS Gothic</PARAMETER>
                <PARAMETER name="ITALIC.20.W32">MS Gothic</PARAMETER>
                <PARAMETER name="BOLD-ITALIC.20.W32">MS Gothic</PARAMETER>

                <PARAMETER name="PLAIN.28.W32">MS Song</PARAMETER>
                <PARAMETER name="BOLD.28.W32">MS Song</PARAMETER>
                <PARAMETER name="ITALIC.28.W32">MS Song</PARAMETER>
                <PARAMETER name="BOLD-ITALIC.28.W32">MS Song</PARAMETER>

                <PARAMETER name="PLAIN.39.W32">SimSun</PARAMETER>
                <PARAMETER name="BOLD.39.W32">SimSun</PARAMETER>
                <PARAMETER name="ITALIC.39.W32">SimSun</PARAMETER>
                <PARAMETER name="BOLD-ITALIC.39.W32">SimSun</PARAMETER>

                <PARAMETER name="PLAIN.86.W32">Gulim</PARAMETER>
                <PARAMETER name="BOLD.86.W32">Gulim</PARAMETER>
                <PARAMETER name="ITALIC.86.W32">Gulim</PARAMETER>
                <PARAMETER name="BOLD-ITALIC.86.W32">Gulim</PARAMETER>

                <PARAMETER name="PLAIN.87.W32">Arial Unicode MS</PARAMETER>
                <PARAMETER name="BOLD.87.W32">Arial Unicode MS</PARAMETER>
                <PARAMETER name="ITALIC.87.W32">Arial Unicode MS</PARAMETER>
                <PARAMETER name="BOLD-ITALIC.87.W32">Arial Unicode MS</PARAMETER>

                <PARAMETER name="PLAIN.88.W32">Arial Unicode MS</PARAMETER>
                <PARAMETER name="BOLD.88.W32">Arial Unicode MS</PARAMETER>
                <PARAMETER name="ITALIC.88.W32">Arial Unicode MS</PARAMETER>
                <PARAMETER name="BOLD-ITALIC.88.W32">Arial Unicode MS</PARAMETER>
            </SECTION>
            <SECTION name="CLASSIC">
               <PARAMETER name="PLAIN.W32">Arial</PARAMETER>
               <PARAMETER name="BOLD.W32">Arial Bold</PARAMETER>
               <PARAMETER name="ITALIC.W32">Arial Italic</PARAMETER>
               <PARAMETER name="BOLD-ITALIC.W32">Arial Bold Italic</PARAMETER>

               <PARAMETER name="PLAIN.20.W32">MS Gothic</PARAMETER>
               <PARAMETER name="BOLD.20.W32">MS Gothic</PARAMETER>
               <PARAMETER name="ITALIC.20.W32">MS Gothic</PARAMETER>
               <PARAMETER name="BOLD-ITALIC.20.W32">MS Gothic</PARAMETER>

               <PARAMETER name="PLAIN.28.W32">MS Song</PARAMETER>
               <PARAMETER name="BOLD.28.W32">MS Song</PARAMETER>
               <PARAMETER name="ITALIC.28.W32">MS Song</PARAMETER>
               <PARAMETER name="BOLD-ITALIC.28.W32">MS Song</PARAMETER>

               <PARAMETER name="PLAIN.39.W32">SimSun</PARAMETER>
               <PARAMETER name="BOLD.39.W32">SimSun</PARAMETER>
               <PARAMETER name="ITALIC.39.W32">SimSun</PARAMETER>
               <PARAMETER name="BOLD-ITALIC.39.W32">SimSun</PARAMETER>

               <PARAMETER name="PLAIN.86.W32">Gulim</PARAMETER>
               <PARAMETER name="BOLD.86.W32">Gulim</PARAMETER>
               <PARAMETER name="ITALIC.86.W32">Gulim</PARAMETER>
               <PARAMETER name="BOLD-ITALIC.86.W32">Gulim</PARAMETER>

               <PARAMETER name="PLAIN.87.W32">Arial Unicode MS</PARAMETER>
               <PARAMETER name="BOLD.87.W32">Arial Unicode MS</PARAMETER>
               <PARAMETER name="ITALIC.87.W32">Arial Unicode MS</PARAMETER>
               <PARAMETER name="BOLD-ITALIC.87.W32">Arial Unicode MS</PARAMETER>

               <PARAMETER name="PLAIN.88.W32">Arial Unicode MS</PARAMETER>
               <PARAMETER name="BOLD.88.W32">Arial Unicode MS</PARAMETER>
               <PARAMETER name="ITALIC.88.W32">Arial Unicode MS</PARAMETER>
               <PARAMETER name="BOLD-ITALIC.88.W32">Arial Unicode MS</PARAMETER>
            </SECTION>
            <PARAMETER name="HELVETICA.PLAIN.W32">Arial</PARAMETER>
            <PARAMETER name="HELVETICA.BOLD.W32">Arial Bold</PARAMETER>
            <PARAMETER name="HELVETICA.ITALIC.W32">Arial Italic</PARAMETER>
            <PARAMETER name="HELVETICA.BOLD-ITALIC.W32">Arial Bold Italic</PARAMETER>
            <PARAMETER name="TIMES.PLAIN.W32">Times New Roman</PARAMETER>
            <PARAMETER name="TIMES.BOLD.W32">Times New Roman Fett</PARAMETER>
            <PARAMETER name="TIMES.ITALIC.W32">Times New Roman Kursiv</PARAMETER>
            <PARAMETER name="TIMES.BOLD-ITALIC.W32">Times New Roman Fett Kursiv</PARAMETER>
            <PARAMETER name="TIMES_ROMAN.PLAIN.W32">Times New Roman</PARAMETER>
            <PARAMETER name="TIMES_ROMAN.BOLD.W32">Times New Roman Fett</PARAMETER>
            <PARAMETER name="TIMES_ROMAN.ITALIC.W32">Times New Roman Kursiv</PARAMETER>
            <PARAMETER name="TIMES_ROMAN.BOLD-ITALIC.W32">Times New Roman Fett Kursiv</PARAMETER>
            <PARAMETER name="SWISS.PLAIN.W32">Arial</PARAMETER>
            <PARAMETER name="SWISS.BOLD.W32">Arial Bold</PARAMETER>
            <PARAMETER name="SWISS.ITALIC.W32">Arial Italic</PARAMETER>
            <PARAMETER name="SWISS.BOLD-ITALIC.W32">Arial Bold Italic</PARAMETER>
            <PARAMETER name="TYPEWRITE.PLAIN.W32">Courier New</PARAMETER>
            <PARAMETER name="DEFAULT.PLAIN.W32">Courier New</PARAMETER>
            <PARAMETER name="COURIER.PLAIN.W32">Courier New</PARAMETER>
            <PARAMETER name="COURIER.BOLD.W32">Courier New Fett</PARAMETER>
            <PARAMETER name="ARIAL.PLAIN.W32">Arial Narrow</PARAMETER>
            <PARAMETER name="ARIAL.BOLD.W32">Arial Fett</PARAMETER>
            <PARAMETER name="SYMBOLS.PLAIN.W32">Symbols</PARAMETER>
            <PARAMETER name="SYMBOLS.PLAIN.W32.offset">61440</PARAMETER>
            <PARAMETER name="GREEK.PLAIN.W32">Greek</PARAMETER>
            <PARAMETER name="GREEK.PLAIN.W32.offset">61440</PARAMETER>
            <PARAMETER name="GREEK.BOLD.W32">Greek Bold</PARAMETER>
            <PARAMETER name="GREEK.BOLD.W32.offset">61440</PARAMETER>
            <PARAMETER name="GREEK.ITALIC.W32">Greek Italic</PARAMETER>
            <PARAMETER name="GREEK.ITALIC.W32.offset">61440</PARAMETER>
            <PARAMETER name="GREEK.BOLD-ITALIC.W32">Greek Bold Italic</PARAMETER>
            <PARAMETER name="GREEK.BOLD-ITALIC.W32.offset">61440</PARAMETER>
            <PARAMETER name="MATH~A.PLAIN.W32">Math A</PARAMETER>
            <PARAMETER name="MATH~A.PLAIN.W32.offset">61440</PARAMETER>
            <PARAMETER name="MATH~B.PLAIN.W32">Math B</PARAMETER>
            <PARAMETER name="MATH~B.PLAIN.W32.offset">61440</PARAMETER>
            <PARAMETER name="MATH~EXT;.PLAIN.W32">Math Ext.</PARAMETER>
            <PARAMETER name="MATH~EXT;.PLAIN.W32.offset">61440</PARAMETER>
            <PARAMETER name="LOGOC0.PLAIN.W32">MB Service</PARAMETER>
            <PARAMETER name="LOGOC0.PLAIN.W32.offset">0</PARAMETER>
            <PARAMETER name="LOGO1C0.PLAIN.W32">MB Laenderkennzeichen</PARAMETER>
            <PARAMETER name="LOGO1C0.PLAIN.W32.offset">0</PARAMETER>
            <PARAMETER name="LOGO1C41.PLAIN.W32">MB Diktogramme</PARAMETER>
            <PARAMETER name="LOGO1C41.PLAIN.W32.offset">61440</PARAMETER>
            <PARAMETER name="LOGO1C356.PLAIN.W32">MB Fahrzeuge</PARAMETER>
            <PARAMETER name="LOGO1C356.PLAIN.W32.offset">0</PARAMETER>
            <PARAMETER name="LOGO1C357.PLAIN.W32">MB Pruefzeichen</PARAMETER>
            <PARAMETER name="LOGO1C357.PLAIN.W32.offset">0</PARAMETER>
            <PARAMETER name="LOGO1C360.PLAIN.W32">MB Kurzzeichen</PARAMETER>
            <PARAMETER name="LOGO1C360.PLAIN.W32.offset">61440</PARAMETER>
            <PARAMETER name="LOGO2C0.PLAIN.W32">AMS New Digital</PARAMETER>
            <PARAMETER name="LOGO3C0.PLAIN.W32">MB Bedienzeichen</PARAMETER>
            <PARAMETER name="LOGO3C0.PLAIN.W32.offset">61440</PARAMETER>
            <PARAMETER name="LOGO3C41.PLAIN.W32">MB Bedienzeichen S-Klasse</PARAMETER>
            <PARAMETER name="LOGO3C41.PLAIN.W32.offset">0</PARAMETER>
            <PARAMETER name="LOGO3C356.PLAIN.W32">MB Handkurzzeichen</PARAMETER>
            <PARAMETER name="LOGO3C356.PLAIN.W32.offset">0</PARAMETER>
            <PARAMETER name="LOGO3C357.PLAIN.W32">MB Digitalanzeige S-Klasse</PARAMETER>
            <PARAMETER name="LOGO3C357.PLAIN.W32.offset">61440</PARAMETER>
            <PARAMETER name="LOGO3C360.PLAIN.W32">MB Schweisszeichen</PARAMETER>
            <PARAMETER name="LOGO3C360.PLAIN.W32.offset">61440</PARAMETER>
            <PARAMETER name="LOGO3C361.PLAIN.W32">MB Bed. Zeichen W210</PARAMETER>
            <PARAMETER name="LOGO3C361.PLAIN.W32.offset">61440</PARAMETER>
            <PARAMETER name="FONT3C0.PLAIN.W32">MB Fahrzeuge II</PARAMETER>
            <PARAMETER name="FONT3C0.PLAIN.W32.offset">61440</PARAMETER>
            <PARAMETER name="FONT3C41.PLAIN.W32">MBFahrzeuge III</PARAMETER>
            <PARAMETER name="FONT3C41.PLAIN.W32.offset">0</PARAMETER>
        </SECTION>
        <SECTION name="image">
            <SECTION name="TIFF">
                <PARAMETER name="matcher">dcx.wis_online.common.image.TIFFMatcher</PARAMETER>
                <PARAMETER name="decoder">dcx.wis_online.common.image.TIFFDecoder</PARAMETER>
            </SECTION>
            <SECTION name="GIF">
                <PARAMETER name="matcher">dcx.wis_online.common.image.GIFMatcher</PARAMETER>
                <PARAMETER name="decoder">dcx.wis_online.common.image.GIFDecoder</PARAMETER>
            </SECTION>
            <SECTION name="JPEG">
                <PARAMETER name="matcher">dcx.wis_online.common.image.JPEGMatcher</PARAMETER>
                <PARAMETER name="decoder">dcx.wis_online.common.image.JPEGDecoder</PARAMETER>
            </SECTION>
            <SECTION name="DTW">
                <PARAMETER name="matcher">dcx.wis_online.common.image.dtwdecoder.DTWMatcher</PARAMETER>
                <PARAMETER name="decoder">dcx.wis_online.common.image.dtwdecoder.DTWDecoder</PARAMETER>
            </SECTION>
        </SECTION>
        <SECTION name="symptom">
            <SECTION name="appearance">
                <PARAMETER name="id">1|2|3|9|4|5|6|8|0</PARAMETER>
                <PARAMETER name="label.1">F_WS_P_SYMPTOM_CB_APPEARANCE_ACOUSTIC</PARAMETER>
                <PARAMETER name="label.2">F_WS_P_SYMPTOM_CB_APPEARANCE_OPTIC</PARAMETER>
                <PARAMETER name="label.3">F_WS_P_SYMPTOM_CB_APPEARANCE_SENSITIVE</PARAMETER>
                <PARAMETER name="label.9">F_WS_P_SYMPTOM_CB_APPEARANCE_ACOUSTIC_AND_SENSITIVE</PARAMETER>
                <PARAMETER name="label.4">F_WS_P_SYMPTOM_CB_APPEARANCE_LEAKY</PARAMETER>
                <PARAMETER name="label.5">F_WS_P_SYMPTOM_CB_APPEARANCE_SCENTING</PARAMETER>
                <PARAMETER name="label.6">F_WS_P_SYMPTOM_CB_APPEARANCE_MALFUNCTION</PARAMETER>
                <PARAMETER name="label.8">F_WS_P_SYMPTOM_CB_APPEARANCE_READABLE</PARAMETER>
                <PARAMETER name="label.0">F_WS_P_SYMPTOM_CB_APPEARANCE_UNASSIGNABLE</PARAMETER>
            </SECTION>
            <SECTION name="state">
                <PARAMETER name="id">1|2|5|3|4|8|6|7|9|0</PARAMETER>
                <PARAMETER name="label.1">F_WS_P_SYMPTOM_CB_STATE_DRIVING</PARAMETER>
                <PARAMETER name="label.2">F_WS_P_SYMPTOM_CB_STATE_SPEED</PARAMETER>
                <PARAMETER name="label.5">F_WS_P_SYMPTOM_CB_STATE_DRIVING_AND_SPEED</PARAMETER>
                <PARAMETER name="label.3">F_WS_P_SYMPTOM_CB_STATE_REV</PARAMETER>
                <PARAMETER name="label.4">F_WS_P_SYMPTOM_CB_STATE_OPERATING</PARAMETER>
                <PARAMETER name="label.8">F_WS_P_SYMPTOM_CB_STATE_REV_AND_OPERATING</PARAMETER>
                <PARAMETER name="label.6">F_WS_P_SYMPTOM_CB_STATE_DRIVING_AND_REV</PARAMETER>
                <PARAMETER name="label.7">F_WS_P_SYMPTOM_CB_STATE_DRIVING_AND_OPERATING</PARAMETER>
                <PARAMETER name="label.9">F_WS_P_SYMPTOM_CB_STATE_DRIVING_REV_AND_OPERATING</PARAMETER>
                <PARAMETER name="label.0">F_WS_P_SYMPTOM_CB_STATE_UNASSIGNABLE</PARAMETER>
            </SECTION>
            <SECTION name="environment">
                <PARAMETER name="id">1|2|7|3|8|4|0</PARAMETER>
                <PARAMETER name="label.1">F_WS_P_SYMPTOM_CB_ENVIRONMENT_WEATHER</PARAMETER>
                <PARAMETER name="label.2">F_WS_P_SYMPTOM_CB_ENVIRONMENT_ROAD</PARAMETER>
                <PARAMETER name="label.7">F_WS_P_SYMPTOM_CB_ENVIRONMENT_WEATHER_AND_ROAD</PARAMETER>
                <PARAMETER name="label.3">F_WS_P_SYMPTOM_CB_ENVIRONMENT_TEMPERATURE</PARAMETER>
                <PARAMETER name="label.8">F_WS_P_SYMPTOM_CB_ENVIRONMENT_WEATHER_AND_TEMPERATURE</PARAMETER>
                <PARAMETER name="label.4">F_WS_P_SYMPTOM_CB_ENVIRONMENT_FLUIDS</PARAMETER>
                <PARAMETER name="label.0">F_WS_P_SYMPTOM_CB_ENVIRONMENT_UNASSIGNABLE</PARAMETER>
            </SECTION>

        </SECTION>
        <SECTION name="markers">
            <PARAMETER name="anzieh.t">SIDS_ANZIEHMOMENTE</PARAMETER>
            <PARAMETER name="as.t">SIDS_AS_TABELLE</PARAMETER>
            <PARAMETER name="basdat">SIDS_BASISDATEN</PARAMETER>
            <PARAMETER name="bilder.t">SIDS_FIGURE</PARAMETER>
            <PARAMETER name="diag.t">SIDS_DIAGNOSE</PARAMETER>
            <PARAMETER name="fig">SIDS_FIGURE</PARAMETER>
            <PARAMETER name="aender.t">SIDS_AENDERUNGSHINWEISE</PARAMETER>
            <PARAMETER name="fuell.t">SIDS_FUELLMENGEN</PARAMETER>
            <PARAMETER name="hndwkz.t">SIDS_HDLSUEBL_WERKZEUGE</PARAMETER>
        </SECTION>
        <SECTION name="aggtypabk2bmart">
            <PARAMETER name="A">A</PARAMETER>
            <PARAMETER name="AG">G</PARAMETER>
            <PARAMETER name="MG">G</PARAMETER>
            <PARAMETER name="H1">HA</PARAMETER>
            <PARAMETER name="H2">HA</PARAMETER>
            <PARAMETER name="LG">L</PARAMETER>
            <PARAMETER name="P">P</PARAMETER>
            <PARAMETER name="V1">VA</PARAMETER>
            <PARAMETER name="V2">VA</PARAMETER>
            <PARAMETER name="VG">VG</PARAMETER>
            <PARAMETER name="T">T</PARAMETER>
            <PARAMETER name="M">M</PARAMETER>
            <PARAMETER name="L">L</PARAMETER>
            <PARAMETER name="G">G</PARAMETER>
            <PARAMETER name="HA">HA</PARAMETER>
            <PARAMETER name="VA">VA</PARAMETER>
        </SECTION>
        <SECTION name="snap">
            <PARAMETER name="sortclass_1">SORTCLASS.P</PARAMETER>
            <PARAMETER name="sortclass_1.id">1</PARAMETER>
            <PARAMETER name="sortclass_2">SORTCLASS.G</PARAMETER>
            <PARAMETER name="sortclass_2.id">2</PARAMETER>
            <PARAMETER name="sortclass_3">SORTCLASS.L</PARAMETER>
            <PARAMETER name="sortclass_3.id">3</PARAMETER>
            <PARAMETER name="sortclass_4">SORTCLASS.T</PARAMETER>
            <PARAMETER name="sortclass_4.id">4</PARAMETER>
            <PARAMETER name="sortclass_5">SORTCLASS.F</PARAMETER>
            <PARAMETER name="sortclass_5.id">6</PARAMETER>
            <PARAMETER name="sortclass_6">SORTCLASS.M</PARAMETER>
            <PARAMETER name="sortclass_6.id">6</PARAMETER>
            <PARAMETER name="sortclass_7">SORTCLASS.S</PARAMETER>
            <PARAMETER name="sortclass_7.id">6</PARAMETER>
            <PARAMETER name="sortclass_8">SORTCLASS.O</PARAMETER>
            <PARAMETER name="sortclass_8.id">8</PARAMETER>
            <PARAMETER name="sortclass_9">SORTCLASS.U</PARAMETER>
            <PARAMETER name="sortclass_9.id">9</PARAMETER>
            <PARAMETER name="sortclass_10">SORTCLASS.V</PARAMETER>
            <PARAMETER name="sortclass_10.id">3</PARAMETER>
            <PARAMETER name="sortclass_11">SORTCLASS.C</PARAMETER>
            <PARAMETER name="sortclass_11.id">1</PARAMETER>
            <PARAMETER name="sortclass_12">SORTCLASS.K</PARAMETER>
            <PARAMETER name="sortclass_12.id">9</PARAMETER>
        </SECTION>
    </SECTION>

    <SECTION name="services">
        <!--  Licence string for application "Damage Code Standalone"
             (Position 63 to 72 will be used for country code which should
             be 0, meaning international)
         -->
        <PARAMETER name="damageCodeLicence">01111110001000000111100000000011111111111111111111111111111111100000000000011110</PARAMETER>
    </SECTION>
</WISCONFIGURATION>

<config>
<param name="gateway">EWA-net/ewa-net</param>
<param name="applicationMode">HPSERVICE</param>
<param name="clientMainClass">com.proquest.epc.view.impl.MBEPCApplication</param>
<param name="dbDriver">transbase.jdbc.Driver</param>
<param name="SPECIAL_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/SPECIALFILES</param>
<param name="COMM_URL">pooling:50:null:10000:null:5:null:null:null:null:null:null:jdbc:transbase://localhost:2034/COMM</param>
<param name="ALLBMS_URL">pooling:50:null:10000:null:2:true:null:null:null:null:null:jdbc:transbase://localhost:2034/ALLBMS</param>
<param name="DCEX_DCEX_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/DCEX_DCEX</param>
<param name="MBJA_DCJA_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBJA_DCJA</param>
<param name="MBIE_DCIE_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBIE_DCIE</param>
<param name="MBLA_DCLA_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBLA_DCLA</param>
<param name="MBOE_DCBUS_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBOE_DCBUS</param>
<param name="MBOE_DCCAR_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBOE_DCCAR</param>
<param name="MBOE_DCGWGN_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBOE_DCGWGN</param>
<param name="MBOE_DCTRAC_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBOE_DCTRAC</param>
<param name="MBOE_DCTRAN_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBOE_DCTRAN</param>
<param name="MBOE_DCTRK_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBOE_DCTRK</param>
<param name="MBOE_DCUMOG_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBOE_DCUMOG</param>
<param name="MBNA_DCNA_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBNA_DCNA</param>
<param name="MBSA_DCSA_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBSA_DCSA</param>
<param name="MBSM_DCSM_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBSM_DCSM</param>
<param name="COMMONI_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/COMMONI</param>
<param name="JAIMG_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/JAIMG</param>
<param name="LAIMG_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/LAIMG</param>
<param name="NAIMG_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/NAIMG</param>
<param name="SAIMG_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/SAIMG</param>
<param name="SMIMG_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/SMIMG</param>
<param name="OEBUSI_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/OEIMG</param>
<param name="OECARI_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/OEIMG</param>
<param name="OEGWGNI_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/OEIMG</param>
<param name="OETRACI_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/OEIMG</param>
<param name="OETRANI_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/OEIMG</param>
<param name="OETRKI_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/OEIMG</param>
<param name="OEUMOGI_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/OEIMG</param>
<param name="OESAIMG_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/OESAIMG</param>
<param name="OEAGGIMG_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/OEAGGIMG</param>
<param name="MBIE1COMM_H_URL">pooling:30:null:10000:null:2:null:null:null:null:null:null:jdbc:transbase://localhost:2034/MBIE1COMM</param>
<param name="COMMONI_H_IMAGES_URL">COMMONI_H_URL</param>
<param name="MBJA_AGGBM_IMAGES_URL">COMMONI_H_URL,JAIMG_H_URL</param>
<param name="MBJA_CARBM_IMAGES_URL">COMMONI_H_URL,JAIMG_H_URL</param>
<param name="MBJA_TRANBM_IMAGES_URL">COMMONI_H_URL,JAIMG_H_URL</param>
<param name="MBIE_AGGBM_IMAGES_URL">COMMONI_H_URL,MBIE1COMM_H_URL</param>
<param name="MBLA_AGGBM_IMAGES_URL">COMMONI_H_URL,LAIMG_H_URL</param>
<param name="MBLA_CVBM_IMAGES_URL">COMMONI_H_URL,LAIMG_H_URL</param>
<param name="MBLA_TRANBM_IMAGES_URL">COMMONI_H_URL,LAIMG_H_URL</param>
<param name="MBOE_AGGBM_IMAGES_URL">COMMONI_H_URL,OESAIMG_H_URL,OEAGGIMG_H_URL</param>
<param name="MBOE_BUSBM_IMAGES_URL">COMMONI_H_URL,OEBUSI_H_URL</param>
<param name="MBOE_CARBM_IMAGES_URL">COMMONI_H_URL,OECARI_H_URL</param>
<param name="MBOE_GWGNBM_IMAGES_URL">COMMONI_H_URL,OEGWGNI_H_URL</param>
<param name="MBOE_TRACBM_IMAGES_URL">COMMONI_H_URL,OETRACI_H_URL</param>
<param name="MBOE_TRANBM_IMAGES_URL">COMMONI_H_URL,OETRANI_H_URL</param>
<param name="MBOE_TRKBM_IMAGES_URL">COMMONI_H_URL,OETRKI_H_URL</param>
<param name="MBOE_UMOGBM_IMAGES_URL">COMMONI_H_URL,OEUMOGI_H_URL</param>
<param name="MBNA_AGGBM_IMAGES_URL">COMMONI_H_URL,NAIMG_H_URL</param>
<param name="MBNA_CARBM_IMAGES_URL">COMMONI_H_URL,NAIMG_H_URL</param>
<param name="MBSA_AGGBM_IMAGES_URL">COMMONI_H_URL,SAIMG_H_URL</param>
<param name="MBSA_CARBM_IMAGES_URL">COMMONI_H_URL,SAIMG_H_URL</param>
<param name="MBSA_CVBM_IMAGES_URL">COMMONI_H_URL,SAIMG_H_URL</param>
<param name="MBSA_TRANBM_IMAGES_URL">COMMONI_H_URL,SAIMG_H_URL</param>
<param name="MBSM_CARBM_IMAGES_URL">COMMONI_H_URL,SMIMG_H_URL</param>
<param name="MBSM_AGGBM_IMAGES_URL">COMMONI_H_URL,SMIMG_H_URL</param>
<param name="COMM_IMAGES_URL">COMMONI_H_URL,OESAIMG_H_URL:402702003303603903204,NAIMG_H_URL:804,JAIMG_H_URL:105,LAIMG_H_URL:705,SAIMG_H_URL:405,SMIMG_H_URL:207</param>
<param name="MBNOART_IMAGES_URL">COMMONI_H_URL</param>
<param name="dbUser">tbuser</param>
<param name="helpPath">/EPC-net/online-help/html</param>
<param name="wnewPath">/EPC-net/whatsnew/html</param>
<param name="logoPath">/images/logo/background_main.jpg</param>
<param name="showLogoImage">true</param>
<param name="dmsPartNoDelims">' ','-'</param>
<param name="imageop1">ScaleSmooth</param>
<param name="defaultDatabaseLocale">en</param>
<param name="defaultLocale">G</param>
<param name="defaultLocaleGUI">G</param>
<param name="hasSA">true</param>
<param name="availableClasses">1,2,3,4,5,6,7,F,M,T,A,S</param>
<param name="availableClasses_NA">1,2</param>
<param name="availableClasses_JA">1,2,3</param>
<param name="availableClasses_LA">3,4,5,6</param>
<param name="availableClasses_SA">1,2,3,4,5,6,7</param>
<param name="availableClasses_SMART">F</param>
<param name="shoplistVersion">1.1</param>
<param name="loggerLevel">4</param>
<param name="XFR_Delete_Exit">true</param>
<param name="LookAndFeel">Automatic</param>
<param name="enhancedFilteringClasses">1</param>
<param name="SupplementaryTextIn_SL_XFR_File">true</param>
<param name="sendAllModelsForDK">false</param>
<param name="searchHitListWarningLimit">500</param>
</config>

9 Advanced Configuration

9.1 Switching EWA net to default HTTP Port 80

The standard installation will make EWA net run on the specific port 9000. This is to avoid conflicts with existing installations of an HTTP server listening on port 80 (i.e. Windows 2000 Server installations with IIS running for administrative tasks). If you make use of an upfront web server as described in the section about setting up EWA net for clustering you will already find EWA net running on the port 80.

So apart from the steps described in the following sections to make the EWA net Application Server listen on port 80, you might also want to see the clustering documentation and setup a WebServer in front of the application server.

However, to allow you to switch your application server installation to use the HTTP default port 80, following instructions might be helpful for you:

1. Edit the J2EE Server configuration
   
   For the "local" environment this is:
   [EWA_HOME]\server\conf\server.xml
   Find the section and edit the line:
   

   <!--
       Define a non-SSL HTTP/1.1 Connector on port 9000
   -->
   <Connector port="80"
              protocol="HTTP/1.1"
              secure="false"
              maxHttpHeaderSize="8192"
              acceptCount="300"
              maxThreads="200"
              minSpareThreads="25"
              maxSpareThreads="75"
              enableLookups="false"
              redirectPort="8443"
              connectionTimeout="60000"
              disableUploadTimeout="false" />
   

   Replace the current value for "port" (i.e. "9000") with the new value “80".

2. Edit the central config file of EWA net:

   [EWA_HOME]\config\core_cfg.xml

   Edit the value

   [...]
   <PARAMETER name="httpPort">80</PARAMETER>
   [...]

   Replace the value with “80”.

3. Edit the EPC configuration file. Adjust the property for the datacard access URL:

   [EWA_HOME]\config\epc_cfg.xml

   Find the section and edit the line:

   [...]
   <param name="datacardapi">http://localhost:80/EPC-net/datacardapi</param>
   [...]

   Replace the value with “80”

4. Restart the EWA net server
5. If you make use of EWANAPI please assure that all clients refer to the corrected address now. As EWANAPI has to connect to the server, it needs the correct URL, including a correct port number for the URL.
   Find and edit the file:

   EWANAPI.INI

   and edit the entry

   [...]
   [HTTP-Config]
   [...]
   Port=80
   

   Replace the value with “80”.

9.2 Logging

9.2.1 EWA net system log

EWA net makes use of the Log4J logging API, a de-facto standard in the Java world. Its configuration will be performed within the file

[EWA_HOME]\config\log4_config.xml

You will find different so called “appenders” within this file to be configured. Each of them has properties that you can use to fine tune the logging mechanisms:

There are 2 basically different files that log different things:

1. A developer log file being that contains typically the most information.
   This information will be generated by two appenders: one writing HTML formatted output (name of the appender is “HTML”), the other one writing plain ASCII (name of this appender is “STANDARD_FILE”)
2. A DC compliant monitor file reporting monitoring information.
   This information will be generated by an appender named “DCMONFILE”. It creates a file in the format specified by Daimler

9.2.1.1 File names and location of logfiles

You can modify the filenames into which the appenders write. The filenames are being defined by the parameter “File” for each appender. You are free in choosing a filename you like. As long as you specifiy simply a filename without directory information, this file will be created in the folder [EWA_HOME]\logs.

As soon as you provide an absolute path, this will be chosen.

Example:

<param name=”File” value=”C:\test__log.txt” />

will write the output directly into the root directory of drive C:

Note:
Please be aware that changing the directory in which EWA net will log might have unwanted side effects. One of them is that neither Dr.EWA nor the administration pages will be able to find those log files then. EWA net's tools expect that logfiles will be written into [EWA_HOME]\logs.

9.2.1.2 Log level

The log level for the log appenders can be set individually for the both appenders writing the debugging log information. For each of these appenders you will find the entry

<param name=”Threshold” value=”WARN” />

There are different log levels available. The higher you set the level (from DEBUG up to FATAL) the less narrative the log file will be, but you will then only see the more critical reports :

9.2.2 Application Server logging

EWA net will be run inside and under the control of the application server. During runtime of the application server all of its components perform some kind of communication between each other and fulfill different tasks. Those are not under the control of EWA net and will be monitored within separate, application server specific files.

If something goes wrong – i.e. an exception occurs (some unexpected behavior) – It will be logged into an application server (often also referred to as "container") own log file. The details of the logging information depends upon the configured log level (or debug level).

Note:
These logfiles will mainly contain information in the startup phase of the components. Typically during runtime you will find the most relevant information within the logfiles that EWA net writes on its own (see above).

9.2.3 Client Side Logging

Besides logging on server side, logging can also be influenced on client side. This can mainly be used for troubleshooting of client application problems.

Logging is per default enabled on information level but can be configured during runtime to a different level or format. Logging configuration is set by a file on the clients machine. The format of the file is described below and will be searched in the following order:

1. %USERPROFILE%\logging.properties

2. C:\logging.properties

3. (default configuration)

The client application is watching for a configuration change for every 10 seconds and refreshes the logging configuration if the file has been altered.

An example logging configuration on client side could look like this:

# Handler to which the log output is directed to
handlers=java.util.logging.ConsoleHandler

# Default global logging level.
# This specifies which kinds of events are logged across
# all loggers. For any given facility this global level
# can be overriden by a facility specific level
# Note that the ConsoleHandler also has a separate level
# setting to limit messages printed to the console.
.level=INFO

# For example, set the com.hp logger to only log SEVERE messages:
com.hp.level=SEVERE

Logging levels can be specified for different application component structures and set to different levels. Levels can be...

• SEVERE (highest value)
• WARNING
• INFO
• CONFIG
• FINE
• FINER
• FINEST (lowest value)

For further configuration options, please take a look to the Java Logging Overview,

9.3 Security

9.3.1 Secure Socket Layer (SSL, HTTPS) Support – Optional

Support for SSL is optional. Installing SSL requires general SSL knowledge. Before installing SSL please make sure the server is running correctly. Only after you tested the system completely and assured it is running fine, start installing SSL. After completing the SSL installation, you can use the system like before. You can even use your old bookmark. EWA net will automatically switch to SSL during logon. You can recognize this by finding the yellow lock icon in the Internet Explorer status bar.

For protection against unsolicited access please find more information here.

During the SSL installation, please stop the EWA net server and restart it only after completing the SSL setup. If you do not do this you might get confused as files might be locked or the server will not react in the way you expected it.

Get a certificate for the computer

Before using SSL you have to get an official SSL certificate for the server you want to run the EWA net application server on. This certificate will be issued to the host name and IP address. It can either be a "self signed" certificate (for first simple tests this might be sufficient) or an official certificate signed by a known certificate authority like Verisign or Thawte.

Note:
A self signed certificate should only be used for testing. EWANAPI doesn’t support self signed certificates. Also the Internet Explorer will show a warning, that the certificate issuer is not trusted.

General approach for getting a certificate (find more details about that later on):

1. Use an empty key store like the one provided on the EWA net media (or create a new empty key store for your certificate)
   Key stores are a Java mechanism for storing the private/public key pairs that finally make up your certificate. You can think of those files like a treasure box which is locked by a password that only you and of course your application server know.
2. Generate a public/private key pair in that key store. This key pair will again be protected by a password.
   Ensure you use the same password for both your key pair and your key store itself!
   If you muss this, you will not be able to run the Application Server in SSL mode as it then cannot access your certficate.
3. Request a certificate from a certificate authority (CA) for that key
4. Import the certificate you have received from the CA. Import the chain certificate (the certificate authentication the CA).

An example can be found at http://www.caucho.com/quercus/faq/question.xtp?question_id=1306

For getting an official and trusted certificate please refer to the certificate authorities and your internal processes for doing so.

Prepare the key store

Find the prepared and empty key store on the delivery media (you may also create your own if you have good experience). We will later refer to the key store in the server's file system at:

File: [EWA_HOME]\certificates\ewanet.jks

So, copy the key store file from the delivery media at

[DVD-DRIVE]:\ewa\central\config\ewanet.jks

to

[EWA_HOME]\certificates\ewanet.jks

(create the directory "certificates" if needed).
Please ensure to remove any write protection on the file after you copied it from the delivery media..

The file is a Java key store file and we will make use of it in the next steps.

To be able to work with the system you could simply make use of Sun's "keytool" which is part of a public Java Development Kit. But we recommend to make use of the “KeyTool GUI” (http://www.waynegrant.info/keytool.html). This document assumes you have this software installed.

Assuming you have installed the "KeyTool GUI", you will now be able to open the key store at

EWA_HOME\certificates\ewanet.jks

Double-click the file and a GUI will open, asking you for the key store's password.

1. You will be asked for a password. Enter "changeit" as this is the default when you use the key store from the delivery media
2. We recommend you change the password now and save the key store again (use the menu "Tools / Set Keystore password" to do this and then click on "File / Save").
3. Create a public/private key pair (this will make up your certificate later).

   

   Use RSA, 1024 Bits and the default settings for the rest.
   When asked for information, (Common Name (CN), Email,...) please set at least a meaningful duration (i.e. 365 days for one year) and the Common Name attribute with exactly the DNS name that your client later will refer to when trying to connect your EWA net server.

   

   Make use of the default algorithm (MD2withRSA).

   Note:
   It is important that for the "Common Name" you specify exactly the server name that your clients of EWA net will make use of in the future. Typically it is recommended to use the fully qualified DNS name of the EWA net server.

4. You will then be asked for an alias. This will not be used by the server, it is just an intuitive name for your reference, as you could i.e. add several different certificates within the given key store. You may just accept the suggestion of the KeyTool application.

   

5. Enter a password for the keypair now.
   Note:
   It is important that you now use exactly the same password as for the key store itself. If you do this wrong, your EWA net server will definitely not run with SSL switched on as it will not be able to access your certificate. So make use of the password that you have set for the key store itself again.

   

6. Now you must save your keystore again.
   Congratulations! You successfully created a "self-signed" certificate.
   It is not yet trusted, but to test your system you could for now skip the next few steps of this documentation and try to configure your server.

   Note:
   DO NOT DELETE THE KEYSTORE NOW. It will be used by the server and you will also need it to re-import the real certificate from a trusted authority like VeriSign. If you delete the keystore and then get your official certificate back, it will be worthless. You will not be able to recreate a keystore and keypair matching this certficate.

7. To get a real certificate, please first create a Certificate Signing Request (CSR) now

   

   Save this to the disk and get in contact with i.e. VeriSign or Thawte where you will have to upload this information.
   They will return 2 certificates after a few days - and after you paid it, of course :)
   - a so called "chain certificate"
   - your personal "trusted" and official certificate that now will be accepted by all browsers and the EWANAPI executable once imported into your key store.
   Both have to be imported via "Import CA Reply" in the context menu of your certificate in the key store (see screenshot above) - starting always with the chain certificate!
   Please follow the instructions of the certificate authority where you received the certificate files from. Should you have any problems importing the certificates, please contact the certificate authority or have a look at: http://www.caucho.com/quercus/faq/question.xtp?question_id=1306,
   which basically tells you that you might have to import and export the files through the InternetExplorer certificate store.
8. Do not forget to save your key store now. Then close the KeyTool application.
9. Congratulations! Your key store is complete, but to use it you now have to activate SSL in the server - something you will have to do after each update of the software.

Activate SSL within the application server

File: [EWA_HOME]\server\conf\server.xml

<!--
    Define a non-SSL HTTP/1.1 Connector on port 9000
-->
<Connector port="9000"
    protocol="HTTP/1.1"
    secure="false"
    maxHttpHeaderSize="8192"
    acceptCount="300"
    maxThreads="200"
    minSpareThreads="25"
    maxSpareThreads="75"
    enableLookups="false"
    redirectPort="8443"
    connectionTimeout="60000"
    disableUploadTimeout="false" />


<!--
    Define a SSL HTTP/1.1 Connector on port 8443
<Connector port="8443"
           protocol="HTTP/1.1"
           maxHttpHeaderSize="8192"
           acceptCount="300"
           maxThreads="200"
           minSpareThreads="25"
           maxSpareThreads="75"
           enableLookups="false"
           scheme="https"
           secure="true"
           clientAuth="false"
           connectionTimeout="60000"
           disableUploadTimeout="false"
           keystoreFile="[EWA_HOME]/certificates/ewanet.jks" 
           keystorePass="changeit"
           sslProtocol="TLS" />
-->

Note:
Ensure that your replace the placeholder string "[EWA_HOME]" by your real installation directory, i.e. "C:/EWA_net" wherever it appeared in the samples above.

Now you successfully activated the SSL mode of the application server, but EWA net is not yet aware of this setting.

Activate SSL inside of the EWA net application

After configuring your application server to make use of SSL you finally have to tell the EWA net application itself about your intention to use SSL and on which ports your application server listens. This is needed as there is no common API in the different application servers to ask them for this information.

Note:
In opposite to early versions of EWA net is not necessary anymore to perform this step after each software update.

Edit the configuration file:

File: [EWA_HOME]\config\core_cfg.xml

Activate SSL inside of EWA net. Go to the AccessGateway -> ApplicationSettings section at the very bottom of that file. There set the property “sslEnabled” from false to true.

<SECTION name="AccessGateway">
    <SECTION name="ApplicationSettings">
    <!-- SSL within EWA net - do not forget to configure your server accordingly -->
    <PARAMETER name="sslEnabled">true</PARAMETER>
    <!-- currently SSL for Client apps is not supported. Future use. 
    Needs further extension of SSL for Struts -->
    <PARAMETER name="sslForClientsEnabled">false</PARAMETER>
    <PARAMETER name="httpPort">9000</PARAMETER>
    <PARAMETER name="httpsPort">8443</PARAMETER>

    </SECTION>

9.3.2 Protection against unsolicited access

The system should be protected against unsolicited access. In general all URLs that shouldn’t explicitly accessed from outside should be blocked. For the application itself the so called AccessGateway will be a single point of entry. No direct access to business logic is allowed and possible. This prevents potential security issues. There are also URLs that should be only accessible for system administrator (e.g. run time statistics).

The security constraint feature of the web application settings (web.xml) will be used to reach this goal.  Only few resources should be accessible from outside. Unfortunately it isn’t possible to define a positive list (which URLs are allowed) but only a negative list.

The protection level are:

• Public:               External access allowed
• Protected:          No external access allowed.
• Admin:              These URLs are only allowed to access using a system administrator role.

EWA-net URLs

¹Internal info: these URLs have already been protected by Apache Struts.

EPC-net URLs

WIS-net URLs

Configure web.xml

Change the settings of all installed web applications. The settings file is

EWA-net:          [EWAHOME]\webapps\EWA-net\WEB-INF\web.xml
EPC-net:           [EWAHOME]\webapps\EWA-net\WEB-INF\web.xml
WIS-net:            [EWAHOME]\webapps\EWA-net\WEB-INF\web.xml

Add to the web.xml:

<security-constraint>
    <web-resource-collection>
        <web-resource-name>Blocked URLs</web-resource-name>
        <description>Block all traffic to unwanted URLs.</description>
        <url-pattern>/jsp/*</url-pattern>
        <url-pattern>/someotherurl</url-pattern>
    </web-resource-collection>
    <auth-constraint>
        <description>This group doesn't contain user. So no user is allowed to
            access such URLs</description>
        <role-name>ewanet_protected</role-name>
    </auth-constraint>
</security-constraint>

<security-constraint>
    <web-resource-collection>
        <web-resource-name>Admin URLs</web-resource-name>
        <description> URLs accessible for administrators only</description>
        <url-pattern>/statistic</url-pattern>
        <url-pattern>/someotherurl</url-pattern>
    </web-resource-collection>
    <auth-constraint>
        <description>Only admin user </description>
        <role-name>ewanet_admin</role-name>
    </auth-constraint>
</security-constraint>

<login-config>
    <auth-method>BASIC</auth-method>
</login-config>

<security-role>
    <role-name>ewanet_protected</role-name>
    <role-name>ewanet_admin</role-name>
</security-role>

9.4 User Management Configuration

File: [EWA_ HOME]\config\core_cfg.xml
File: [EWA_ HOME]\config\um_cfg.xml
File: [EWA_ HOME]\config\um_batch_cfg.xml

The User Management configuration can be changed by editing the files core_cfg.xml and um_cfg.xml. Additionally the file um_batch_cfg.xml is used for installations which support EWANAPI. It is required to configure the login method for EWANAPI authentication calls.

EWANAPI uses the values of "um_batch_cfg.xml" where as the standard login masks use "um_cfg.xml" as configuration. So the best way to configure EWANAPI access to setup a correct and tested "um_cfg.xml" and then after successful tests make a copy of it and rename it "um_batch_cfg.xml".

9.4.1 HP User Management

HP User Management is the default User Management. It is being switched on automatically at the time when EWA net local is installed.

Edit: [EWA_ HOME]\config\um_cfg.xml

Set <PARAMETER name="userManagementService">HPUserManagement</PARAMETER>
Set <PARAMETER name="authenticationMode">Own</PARAMETER>

EWA net supports different authentication modes for the HP User Management:

• Own
  Authentication will be performed against the EWA net built in user management database only.
• LDAP
  Authentication will be performed against an LDAP capable User directory (i.e. MS Active Directory). Nevertheless the users will have to be setup within the EWA net built in user management database for authorization.
• Corporate Directory
  Daimler internal authentication directory.

9.4.2 LDAP

LDAP authentication offers the possibility to authenticate users using a generic LDAP server. Also Microsoft Active Directory can be used as authentication interface using LDAP. LDAP authentication is only possible if HP User Management is switched on.

The LDAP authentication interface offers four possibilities for authentication of users:

1. LDAP Authentication (Most simple mode)
   The entered user name, domain and password are used for authentication by trying to bind against a LDAP server. If the bind is successful, it is assumed that the password was correct.
2. LDAP Attribute comparism (Fetch Mode)
   The LDAP server is bound using a fixed account. An LDAP record is fetched using the userid and domain name of the entered credentials. One attribute from the record is then compared to the entered password of the user.
3. LDAP Search and Result Attribute comparism (Search Mode)
   The LDAP server is bound using a fixed account. A LDAP record is searched in the directory using a specific scope with a filter which is generated using the credentials of the user. One attribute from the LDAP search result is compared with the password of the user.
4. LDAP Entry Search and User Authentication
   The LDAP directory is searched for a user name like in search mode, the resulting matched user is authenticated using the provided password.

9.4.2.1 General Setup of LDAP

To enable LDAP authentication the following configuration needs to be adopted:

Edit: files [EWA_ HOME]\config\um_cfg.xml / [EWA_ HOME]\config\um_batch_cfg.xml

Set <PARAMETER name="userManagementService">HPUserManagement</PARAMETER>
Set <PARAMETER name="authenticationMode">LDAP</PARAMETER>

Modify the section “LDAP” to match your LDAP environment.

No matter which type of authentication you want to make use of, there is one common thing for all of them:

Specify your LDAP Server and Port:
<PARAMETER name="ldapHost">your.ldap.server</PARAMETER>
<PARAMETER name="ldapPort">389</PARAMETER>
Port 389 is an LDAP port of a typical "standard" environment.

See the sections below for the specific settings of each individual authentication method.

9.4.2.2 Using LDAP Authentication (Simple mode)

Using this simple mode basically performs a "bind" against the given LDAP server. If a "bind" is succesful, the user will be authenticated successfully, if not the user will not be authenticated. Typically this will not work in large and complex setups where users are distributed in LDAP over several nodes which cannot be expressed by one single DN pattern.

To authenticate the user against LDAP by issuing a direct bind with the user credentials, the following settings in sections LDAP need to be adopted:

1. Specify the bind DN to use for authentication:
   <PARAMETER name="bindDN">[your bind DN]</PARAMETER>
   DN with which the LDAP-Connection is established. Placeholders in the DN - to make the DN more flexible - are:
   {userid}
   {password}
   {domain}  Note: This value only exists if you setup userids in the form "<domain>\<userid>"
   They will be replaced from the provided login information of the user. Before replacement, the characters "*()" of the entered user credentials will be escaped.
   Example for a bindDN parameter, which expects users in the subtree (com - company - {domain} - Users):
   CN={userid},CN=Users,DC={domain},DC=company,DC=com
2. Specify the binding password for the connection:
   Placeholders
   {userid}
   {password}
   {domain}
   will be replaced by the submitted login information. The characters "*()" of the user credentials will be NOT escaped! To authenticate against LDAP, use the following setting:
   <PARAMETER name="bindPasswd">{password}</PARAMETER>
3. Specify the mode for authentication:
   <PARAMETER name="authMode">authenticate</PARAMETER>

All other options in the section LDAP are not relevant in this case.

9.4.2.3 Using LDAP Fetch Mode

If you do not want to make use of LDAP user passwords for your EWA net users, you may want to sign a specific attribute within the User object in LDAP as pseudo password. In this case we follow the approach:

1. Bind to the LDAP server with one explicit "bind user" or even anonymous.
2. Go down the hierarchy following a provided, flexible DN
3. Resolve the attribute of the user object that was found and compare the password against this attribute

To process authentication using a LDAP fetch the following settings need to be performed within the configuration:

1. Specify the bind DN to use for authentication:
   <PARAMETER name="bindDN">[your bind DN]</PARAMETER>
   DN with which the LDAP-Connection is established with an explicit "bind user". These values will be fixed as they are needed for binding and do not make use of the provided login information during the.authentication process. You might even be able to bind anonymously. In this case you can leave the "bind" fields empty.
   Example:
   CN=Administrator,CN=Users,DC=myDomain,DC=company,DC=com
2. Specify the binding password for the connection:
   <PARAMETER name="bindPasswd">noBodyShouldKnowTh1s</PARAMETER>
3. Specify the mode for authentication:
   <PARAMETER name="authMode">fetch</PARAMETER>
4. Specify the DN to fetch. This means that the LDAP tree will be followed down the given path stated by the DN and at the located User object a distinct attribute will be compared against the password or another fixed value.
   The DN is typically composed using the entered user credentials. The placeholders
   {userid}
   {password}
   {domain}
    will be replaced by the submitted login information. Before replacement, the characters "*()" in the entered credentials will be escaped.
   Example:
   <PARAMETER name="fetchDN">
   CN={userid},CN=Users,DC={domain},DC=company,DC=com
   </PARAMETER>
5. Specify the attribute of the LDAP User object which should be used for comparison against the password:
   Example:
   <PARAMETER name="attribute">telephoneNumber</PARAMETER>
6. Specify whether the attribute value should be encrypted before comparism. The encryption method is SHA-1.
   This will be set to "false" in most cases.
   <PARAMETER name="encryptAttributeBeforeCompare">false</PARAMETER>
7. Specify whether the entered password of the user should be encrypted before comparism. The encryption method is SHA-1.
   This will correspond to "false" in most cases.
   <PARAMETER name="encryptPasswordBeforeCompare">false</PARAMETER>

All other options of section LDAP are not relevant in this case.

9.4.2.4 Using LDAP Search Mode

The "search" mode is even more advanced. In complex environments, the User objects will typically be distributed over several different subtrees within LDAP. Fetch is not sufficient in this case, so we allow a recursive "search" below a given subtree. To perform this search we need a root part of the tree - the DN from which to start (here referred to as "searchScope"). Furthermore we need a search clause to tell us how we find a User object that might by a potential candidate. And finally we need an attribute to compare the password against.

To process authentication using a LDAP search the following settings need to be done in the configuration:

1. Specify the bind DN to use for authentication:
   <PARAMETER name="bindDN">[your bind DN]</PARAMETER>
   DN with which the LDAP-Connection is established. These values will be fixed as they are needed for binding, but could also be anonymous.
   Example:
   CN=Administrator,CN=Users,DC=myDomain,DC=company,DC=com
2. Specify the binding password for the connection:
   <PARAMETER name="bindPasswd">noBodyShouldKnowTh1s</PARAMETER>
3. Specify the mode for authentication:
   <PARAMETER name="authMode">search</PARAMETER>
4. Specify the search filter to use when trying to find a LDAP record.
   Regular LDAP search filter expressions can be entered. See RFC 2254 for a detailed description of LDAP filters.
   The known placeholders
   {userid}
   {password}
   {domain}
   can be used in the expression and will be replaced automatically by the submitted login information. Before replacement, the characters "*()" in the entered credentials will be escaped.
   Note: Only the first matching record will be used for authentication!
   Examples:
   <PARAMETER name="searchFilter">
   mail=*_{userid}@{domain}.company.com
   (&(sAMAccountName={userid})(ObjectClass=user))
   employeeNumber={userid}
   </PARAMETER>
    
5. Specify the search scope.
   Context which will be searched for an LDAP user entry.
   Again, the tokens
   {userid}
   {password}
   {domain}
   can be used and will be replaced by the submitted login information. Before replacement, the characters "*()" in the entered credentials will be escaped.
   Example:
   <PARAMETER name="searchScope">
   CN=Users,DC={domain},DC=company,DC=com
   </PARAMETER>
6. Specify the attribute which should be compared against the password:
   Example:
   <PARAMETER name="attribute">telephoneNumber</PARAMETER>
7. Specify whether the attribute value should be encrypted before comparism. The encryption method is SHA-1.
   This will correspond to "false" in most cases.
   <PARAMETER name="encryptAttributeBeforeCompare">false</PARAMETER>
8. Specify whether the entered password of the user should be encrypted before comparism. The encryption method is SHA-1.
   This will correspond to "false" in most cases.
   <PARAMETER name="encryptPasswordBeforeCompare">false</PARAMETER>

All other options of the section LDAP are not relevant in this case.

9.4.2.5 Using LDAP Search and Authentication Mode (most valuable for accessing an MS ActiveDirectory)

Typically in an ActiveDirectory world you will still not be satisfied with the approaches discussed up to now. "Bind" will not work as in large environments you will not be able to specifiy a bind DN which is flexible enough, and "search" and "fetch" rely on attributes to be compared instead of using the ActiveDirectory password - which is not exposed as a separate attribute that we could use for comparison.

Any help out of this dilemma? Yes. We allow another mode which is "Search and Authenticate". The basic idea is that after finding a user candidate in the LDAP tree we bind it, because we now can get the real bind DN of this user. The name of this attribute holding the DN is "distinguishedName" in MS ActiveDirectory, in other LDAP directories it might be different, i.e. "dn".

To process authentication using a LDAP search and authenticate the following settings need to be done in the configuration:

1. Specify the bind DN to use for authentication for searching the user account:
   <PARAMETER name="bindDN">[your bind DN]</PARAMETER>
   DN with which the LDAP-Connection is established. These values will be fixed as they are needed for binding.
   Example:
   CN=Administrator,CN=Users,DC=myDomain,DC=company,DC=com
2. Specify the binding password for the connection:
   <PARAMETER name="bindPasswd">noBodyShouldKnowTh1s</PARAMETER>
3. Specify the mode for authentication:
   <PARAMETER name="authMode">search+authenticate</PARAMETER>
4. Specify the search filter to use when trying to find a LDAP user.
   Regular LDAP search filter expressions can be entered. See RFC 2254 for a detailed description of LDAP filters.
   Tokens
   {userid}
   {password}
   {domain}
   will be replaced by the submitted login information. Before replacement, the characters "*()" in the entered credentials will be escaped.
   Note: Only the first matching record will be used for authentication!
   Examples:
   <PARAMETER name="searchFilter">
   mail=*_{userid}@{domain}.company.com
   (&(sAMAccountName={userid})(ObjectClass=user))
   employeeNumber={userid}
   </PARAMETER>
    
5. Specify the search scope.
   Context which will be searched for an LDAP user entry.
   Again, tokens
   {userid}
   {password}
   {domain}
    will be replaced by the submitted login information. Before replacement, the characters "*()" in the entered credentials will be escaped.
   Example:
   <PARAMETER name="searchScope">
   CN=Users,DC={domain},DC=company,DC=com
   </PARAMETER>
6. Specify the attribute which should be user to define the DN of the user.:
   Examples:
   <PARAMETER name="attribute">dn</PARAMETER>
   <PARAMETER name="attribute">distinguishedName</PARAMETER> (recommended for MS Active Directory)

All further options of section LDAP are not relevant in this case.

9.4.3 Corporate Directory

This is basically used by Daimler internally in Stuttgart.

Edit: [EWA_HOME]\config\um_cfg.xml

Set <PARAMETER name="userManagementService">HPUserManagement</PARAMETER>
Set <PARAMETER name="authenticationMode">CorporateDirectory</PARAMETER>

Modify the section “CorporateDirectory” to match the DC CorporateDirectory LDAP settings and furthermore assure that the internal IT allows your EWA net Server to access the Corporate Directory.

9.4.4 StarTekInfo

This is only used by MB USA for integration of EWA net into the external StarTek portal. In this mode most parts of the EWA net internal UserManagement become switched off.

Copy
[DVD-DRIVE]:\ewa\central\config\startekapi.properties
to
[EWA_HOME]\config
Edit the URL to the StarTekInfo server inside this file, if the server has changed.

Edit: [EWA_HOME]\config\um_cfg.xml
Set <PARAMETER name="userManagementService">StarTekInfo</PARAMETER>.

To run the WIS net / EPC net applications the user needs to log on using the StarTekInfo Portal. The rendered portal web page needs to use the following or an equivalent HTML form to start the application:

<form name="docWisForm" method="post" action="http://server.domain:9000/EWA-net/ewa-net.jnlp">
    <input type="hidden" name="userid" value="STAR0101" />
    <input type="hidden" name="sessionid" value="ABCDEFGHIJKLMNOPQRSTUVWXYZ" size="50" />
    <input type="hidden" name="function" value="start" />
    <input type="hidden" name="method" value="start" />
    <input type="hidden" name="appid" value="50" />
</form>

Check the Proxy Settings in the core configuration file [EWA_HOME]\config\core_cfg.xml. The EWA net server needs to perform HTTP network access to the configured StarTek server and thus you may have to specify a proxy to allow this.

  <!--
      Define an AJP 1.3 Connector on port 8009
<Connector port="8009" 
    backlog="200"
    maxThreads="200"
    enableLookups="false"
    redirectPort="8443"
    secure="false"
    protocol="AJP/1.3"
    tomcatAuthentication="false" />
 -->

  <!--
      Define an AJP 1.3 Connector on port 8009
  -->
<Connector port="8009" 
    backlog="200"
    maxThreads="200"
    enableLookups="false"
    redirectPort="8443"
    secure="false"
    protocol="AJP/1.3"
    tomcatAuthentication="false" />

<SECTION name="AccessGateway">
    <SECTION name="ApplicationSettings">
    <!-- SSL within EWA net - do not forget to configure your server accordingly -->
     <PARAMETER name="sslEnabled">false</PARAMETER>
        <!-- currently SSL for Client apps is not supported. Future use. 
        Needs further extension of SSL for Struts -->
        <PARAMETER name="sslForClientsEnabled">false</PARAMETER>
     <PARAMETER name="httpPort">80</PARAMETER>

12 De-Installation

For the de-installation of EWA net just follow the standard way for Windows applications. Go into the Control panel into “Add or Remove Programs”, select the entry “EWA net” and click on “Change/Remove”.

The EWA net software will be completely deinstalled from the system.

12.1 "Hardcore" de-installation

You might at some point face the problem that one step of the advanced de-installation fails and subsequently the whole de-installation fails. This is a frustrating thing with Windows installation software as the smallest change to your environment might make a de-installer fail. To help you out of this misery, we provide a script that de-installs the software in a batched way.

The following step will wipe your EWA net installation, but it does not remove services or de-install your standard products. So please be aware to perform stopping and removing probable EWA net  services as described above before you execute the script.

Note:
Use this script own your own risk - this is not the official way to de-install the software. But it has proven to often run much better then the official way.

You can find the script on the delivery media:

[DVD-DRIVE]:\ewa\tools\CleanEWAInstallation.vbs

13 Update / Migration

Note:
Update and migration steps are only supported from the exact previous delivery version to the current one. If you have an older version, you might want to de-install it and install EWA net from scratch using the most current delivery media.

Note:
EWA net does not support a full recover option. You may want to make a full backup of your system before updating the software. A good harddrive partitioning tool or tape backup will help to get the server back working if something should go wrong during an update.

There are two aspects of updating the EWA net system:

1. Monthly updates (typically database content for WIS net and EPC net as well as updates of resources)
2. Major updates of the system software

Typically you will not see a difference in the way how to perform those updates.

13.1 Regular updates

Typically once a month you will receive a new set of DVDs (or receive your media sets online via the ManageSoft online channel). Updating is a simple thing.

Note:
If you performed an upgrade from a 1.2 version of EWA net to the current version, a migration of the database internals will have to be performed based on some heuristics.
If you have set up only one workshop with several groups and users, the single workshop will be migrated and visible. If you have defined multiple workshops, a new Server Workshop will be created containing the administrator user. In this case other workshops and users are not visible anymore (but still existing!). In this case the "Cascaded Workshop Administration" needs to be enabled. This will allow you to use multiple workshops in your installation. Information on how to do this can be found here.
Anyway it is recommended you check the relationships of your user objects to groups and workshops after migration and manually correct it where the migration algorithm did not perform the steps you would have expected.

14 Additional software installation

14.1 Spooler

14.1.1 General

EWA net provides basically the same spooler programs as provided as part of the former WIS. Those spoolers have slightly been modified to fit better into the EWA net architecture.

Note:
This description is not a replacement for the spooler manuals. It just describes installation and basic ideas behind the spoolers in the special context of EWA net.
For a reference of the spooler manuals including a description of the file formats please refer to the documentation's table of contents.

Note:
In order to run the spoolers successfully you need at least 2 GB free harddisk space on the disk where the WIS net database service is running (!) as complex SQL queries on the database may need temporary space on the disk. Especially the creation of DamageCode rules files need a lot of temporary harddisk space.

In order to be able to create spool files the spooler programs (ASRA spooler and Damagecode spooler) will have to be installed manually from the delivery media of EWA net onto the same machine where the EWA net installation resides. The installation will be described in more detail in the following sections.

The basic mechanism to spool out data (either via ASRA spooler or Damagecode spooler) and to make it accessible for download in the download area is:

• Install the spooler on the server machine of EWA net.
  You will find the installer on the delivery media at
  [DVD-Drive]:\ewa\spooler\setup.exe
  This installer will install both spoolers at once.
• After successful installation you will find two more icons in the list of your favorites in the Internet Explorer:
  
  
• Check for a necessary configuration step.
  If you run an installation where the database system for WIS net still remains on the same server machine as where the spooler is installed, you can start right away. (This is the standard case after a local or a basic central installation)
  If your database server for WIS net data has been installed on a different server, you will have to tell the spooler programs what the hostname of the WIS net database server is.
  You can do this by use of a Windows environment variable.
  Simply set the variable EWANET_DB_SERVER_NAME to the name of your database server.
  Example:
  EWANET_DB_SERVER_NAME=ewadb.my.company.com
  You can do this via the control panel for environment variables in Windows.
• Ensure you have installed a valid WIS net access authorization.
• Now you can successfully start the spoolers.
• Spool out results will be written by default into the [EWA_HOME]\downloads\spooler directory, separated for the Damagecode spooler and the ASRA spooler.
• By spooling these files into special directories within EWA net's home directory, these files can be made available on every client with access to EWA net and for users with access rights for spoolout files (typically users with administrative rights like server administrators and workshop administrators). But EWA net has also the ability to be switched into a mode where any user can gain the right to download spoolout files, independent from its user role. See the UserManagement documentation how to do this.

14.1.2 Configuration

14.1.2.1 Spool file location

The location for the spool out files can be changed by editing the core configuration file core_cfg.xml within the section "Spooler". By default a relative path is set for both ASRA and Damagecode spooler which is interpreted as relative to the EWA_HOME directory. Server administrators which intend to run the spoolers in batch mode and in a clustered environment may want to change this location to a distinct location which is accessible by all EWA net cluster nodes.

Default (relative path)

<SECTION name="Spooler">
    <PARAMETER name="ASRASpoolout">downloads/spooler/asra</PARAMETER> 
    <PARAMETER name="DamageCodeSpoolout">downloads/spooler/damagecode</PARAMETER> 
</SECTION>

Example (absolute path)

<SECTION name="Spooler">
    <PARAMETER name="ASRASpoolout">N:/ewanet_spooler_results/asra</PARAMETER> 
    <PARAMETER name="DamageCodeSpoolout">N:/ewanet_spooler_results/asra/damagecode</PARAMETER> 
</SECTION>

Note:
It is important for you to know that if you switch your file locations to a network path (accessed via UNC path or via mapped drive letters) you will have to change the account under which your EWA net server is running to a user account being allowed to access network resources. The "system" account in Windows is not allowed to do so.

14.1.2.2 Access rights for spool out files

By default EWA net gains users with user role "System Administrator" or "Workshop Administrator" access to the download area for spooled files. You can change this behavior to a per-user-setting by changing the value "userBasedDownloadPermissisons" to "true" in the section "General" of the  UserManagement configuration file um_cfg.xml. Once done you must explicitly assign the user right "Allow download of spooler files" to any user who should gain access to this download area. Even the system administrator does not have this right by default!

14.1.3 Interactively running the spoolers

14.1.3.1 ASRA Spooler (AWAT data spooler)

This spooler allows the extraction of ASRA related data from the WIS net database in the same way as it was possible with "classic" WIS. After startup of the application you will see the following screen:

The marked text field shows the automatically pre-selected output folder for your files. It is recommended to not change this folder in order to ensure that your spool out files will be written into a location where EWA net can find them to allow downloads via the EWA net download page.

Note:
Please ensure that you do not accidently override existing files. Please move those files into a backup location before spooling out the files.

After spooling out the data you may login into EWA net from any client and display the download section (assuming you have the rights to access those pages).

You may download the files for the ASRA Spooler from the section named "ASRA Spooler Output". You may even browse the log file from here. The download page will list all the file that have been spooled out along with the configuration information that was used to create those files. Clicking on one of the hyperlinks in the browser will make the browser start the download of the appropriate file.

14.1.3.2 Damagecode  Spooler (SSL data spooler)

This spooler allows the extraction of damage code related data from the WIS net database in the same way as it was possible with "classic" WIS. After startup of the application you will see the following screen:

The marked text field shows the automatically pre-selected output folder for your files. It is recommended to not change the output folder in order to ensure that your spool out files will be written into a location where EWA net can find them to allow downloads via the EWA net download page.

Note:
Please ensure that you do not accidently override existing files. Please move those files into a backup location before spooling out the files.

After spooling out the data you may login into EWA net from any client and display the download section (assuming you have the rights to access those pages).

You may download the files for the Damage Code Spooler from the section named "Damage Code Spooler Output". You may even browse the log files from here.

14.1.4 Scheduled process of spooling / Spooling multiple "packages"

If you want to make use of more advanced features like

• Scheduled spooling
• Spooling several "packages" of files

you will want to make use of the option to run the spooler executables in "batch mode" which means that they do not show any user interface but get their configuration information from a separate ini-file which basically tells them what they have to do. Once you are sure that your created configuration files are valid and operating the way you expect them you can easily make this process part of the Windows Scheduler.

Note:
This spooler configuration file must be created in ASCII (ISO-8859-1) encoding.

Note:
The spooler will always start a process and will not return values to the command prompt if started from there. The spooler will write a logfile into the spool out directory defined in the configuration file. If you cannot find a logfile after starting the process there is a good chance that the spooler could not find the config file at all. Be sure to quote the path correctly and be sure to always provide the full path to the configuration file like
/f "C:\Program Files\EWA net\spooler\dc_sample.ini"

14.1.4.1 ASRA spooler

You can run the ASRA spooler from its install location in batched mode via the command line:

[EWA_HOME]\spooler\awatso.exe /nongui /f "<configuration file>"

where <configuration file> must be an absolute path pointing to a configuration file. The configuration file may look like this - an example for one single spoolout package with the name "MyFirstSetOfFiles" in Japanese, UTF8 encoding:

[general]

# Root_Path for spool files and the log file
# Note: Use your EWA net installation directory unless you really need to spool into a different location.
Root_Path=C:\Program Files\EWA net\downloads\spooler\asra

[set_MyFirstSetOfFiles]
# Spool out in uppercase (1) or not (0)
Uppercase=0

# Language for which to create the spool outs:
# 0 = German
# 2 = English
# 3 = French
# 4 = Spanish
# 6 = Italian
# 7 = Dutch
# 8 = Danish
# 9 = Swedish
# 10 = Finnish
# 12 = Greek
# 15 = Norwegian
# 17 = Turkish
# 20 = Japanese
# 22 = Russian
# 25 = Polish
# 81 = Slovenian 
SpoolSprache=20

# Allowed file format (encoding) values are ASCII, UTF8 and UCS2
Format=UTF8

# Timemode to be used: "foreign" (= hours) or "domestic" (=AW, only for Germany)
Timemode=foreign

# Directory under which to create the spool files relative to the root path
Relative_Path=MyFirstSetOfFiles

# Define files which shall be spooled out as part of this set

#  326 Master data
326Stammdaten=0
326Filename=VZ002A
# Additional info for 326 Master data
# Want to spoolout job texts?
SatzartArbeitstexte=1
# Want to spoolout included texts?
SatzartUmfassttexte=1
# Want to spoolout flat rates?
SatzartArbeitswerte=1
# Want to spoolout note texts / additional text
SatzartHinweisZusatz=1

# 84 Table data
84Tabellendaten=0
84Filename=VZ004A

# 140 Model designations
140Baumuster=0
140Filename=VZ008A

# 80 Model designations
80Baumuster=0
80BMFilename=VZ046A

# 80 Flat Rate complete
80Awert=1
80AWFilename=VZ000A

Basically the file consists of two basic section types:

[General]

This section occurs only once at the top of a configuration file. Here you can specify the root path for the files that will be spooled out. This also determines where the log file will be written to. The logfile will always be written into the root directory which was specified.

[set_<Name of package>]

A section of this type beginning with "set_" defines a package of files with specific attributes which shall be spooled out. It will also be referred to as "configuration set". It may occur several times with individual names. These names will show up on the User Interface.

Basically you begin specifying in which format you want the files to be spooled out:

1. Uppercase:
   "0" for normal case, "1" for uppercase texts ("1" can only be used with Format="ASCII" - see below)
2. SpoolSprache:
   The Daimler language number for the language in which to spool out the data. See the file example above for all valid languages
3. Format:
   This is basically the encoding of the file. Valid values are "ASCII" for ISO-8859-1 representation, "UTF8" and "UCS2" for double byte representation.
4. Timemode:
   Specifies in what unit for the time of operation items shall be used: "foreign" for countries other than Germany (resulting in hour-based values) or "domestic" for Germany (resulting in AW-based values).

Next is to specify where the files shall be spooled on the file system and what files shall be written at all:

1. Relative_Path:
   This is the directory which will created below the directory specified in the Root_Path property and will contain all the selected files of this package. Typically the name of the package will also be used as a directory name.
2. The rest of the package definition is the statement, which files of the 5 different file types you want to be created (indicated by a "1") and which name you would like to be used for that individual file.
   326Stammdaten: 0 to omit "326 Master Data", 1 to create it.
   326Filename: Filename for "326 Master Data"
      SatzartArbeitstexte: 0 to omit Job Texts of "326 Master Data", 1 to include them.
      SatzartUmfassttexte:  to omit Included Texts of "326 Master Data", 1 to include them.
      SatzartArbeitswerte: to omit Flat Rates of "326 Master Data", 1 to include them.
      SatzartHinweisZusatz: to omit  Note Texts/Additional Texts of "326 Master Data", 1 to include them.
   
   
   84Tabellendaten: 0 to omit "84 Table Data", 1 to create it.
   84Filename: Filename for "84 Table Data"
   
   140Baumuster: 0 to omit "140 Model designations", 1 to create it.
   140Filename: Filename for "140 Model designations"
   
   80Baumuster: 0 to omit "80 Model designations", 1 to create it.
   80BMFilename: Filename for "80 Model designations"
   
   80Awert: 0 to omit "80 Flat Rate complete", 1 to create it.
   80AWFilename: Filename for "80 Flat Rate complete"
    

14.1.4.1.1 Sample spoolout

The following sample of a configuration file will show the effect for the download page as a sample:

[general]

# Root_Path for spool files and the log file
# Note: Use your EWA net installation directory unless you really need to spool into a different location.
Root_Path=C:\Program Files\EWA net\downloads\spooler\asra

# Default Name of the logfile. The file-extension ".log" will
# be added automatically
#Logfile_Name=ASRA_Spoolout

[set_Japanese_Files]
# Spool out in uppercase (1) or not (0)
Uppercase=0

# Language for which to create the spool outs:
# 20 = Japanese
SpoolSprache=20

# Allowed file format (encoding) values are ASCII, UTF8 and UCS2
Format=UTF8

# Timemode to be used: "foreign" (= hours) or "domestic" (=AW, only for Germany)
Timemode=foreign

# Directory under which to create the spool files relative to the root path
Relative_Path=Japanese_Files

# Define files which shall be spooled out as part of this set

#  326 Master data
326Stammdaten=0
326Filename=VZ002A
# Additional info for 326 Master data
# Want to spoolout job texts?
SatzartArbeitstexte=1
# Want to spoolout included texts?
SatzartUmfassttexte=1
# Want to spoolout flat rates?
SatzartArbeitswerte=1
# Want to spoolout note texts / additional text
SatzartHinweisZusatz=1

# 84 Table data
84Tabellendaten=0
84Filename=VZ004A

# 140 Model designations
140Baumuster=0
140Filename=VZ008A

# 80 Model designations
80Baumuster=0
80BMFilename=VZ046A

# 80 Flat Rate complete
80Awert=1
80AWFilename=VZ000A

[set_German_Files]
# Spool out in uppercase (1) or not (0)
Uppercase=1

# Language for which to create the spool outs:
# 0 = German
SpoolSprache=0

# Allowed file format (encoding) values are ASCII, UTF8 and UCS2
Format=ASCII

# Timemode to be used: "foreign" (= hours) or "domestic" (=AW, only for Germany)
Timemode=domestic

# Directory under which to create the spool files relative to the root path
Relative_Path=German_Files

# Define files which shall be spooled out as part of this set

#  326 Master data
326Stammdaten=1
326Filename=VZ002A
# Additional info for 326 Master data
# Want to spoolout job texts?
SatzartArbeitstexte=1
# Want to spoolout included texts?
SatzartUmfassttexte=1
# Want to spoolout flat rates?
SatzartArbeitswerte=1
# Want to spoolout note texts / additional text
SatzartHinweisZusatz=1

# 84 Table data
84Tabellendaten=0
84Filename=VZ004A

# 140 Model designations
140Baumuster=0
140Filename=VZ008A

# 80 Model designations
80Baumuster=0
80BMFilename=VZ046A

# 80 Flat Rate complete
80Awert=1
80AWFilename=VZ000A

You can see that both packages are shown on the screen. Each package is provided as a complete ZIP download package or as individual files along with their description.

14.1.4.2 Damagecode spooler

Batch runs of the damagecode spooler run basically the same as for the ASRA spooler (see above). There are only slight differences in the configuration file over the file that the ASRA spooler uses.

[EWA_HOME]\spooler\sslso.exe /nongui /f "<configuration file>"

where <configuration file> must be an absolute path pointing to a configuration file. The configuration file may look like this - an example for one single spoolout package with the name "MyFirstSetOfFiles" in Japanese, UTF8 encoding:

[general]

# Root_Path for spool files and the log file
# Note: Use your EWA net installation directory unless you really need to spool into a different location.
Root_Path=C:\Program Files\EWA net\downloads\spooler\damagecode

[set_MyFirstSetOfFiles]
# Spool out in uppercase (1) or not (0)
Uppercase=0

# Language for which to create the spool outs:
# 1 = German
# 2 = English
# 3 = French
# 4 = Spanish
# 5 = Portuguese
# 6 = Italian
# 7 = Dutch
# 8 = Danish
# 9 = Swedish
# 10 = Finnish
# 13 = American-English
# 17 = Turkish
# 20 = Japanese
SpoolSprache=20

# Allowed file format (encoding) values are ASCII, UTF8 and UCS2
Format=UTF8

# Directory under which to create the spool files relative to the root path
Relative_Path=MyFirstSetOfFiles

# Define files which shall be spooled out as part of this set

# The DamageCode Rules file
SSRegel=0
RegelFilename=XZD25A.Z.SSLREGIE

# The DamageCode Part Naming
SSTeil=1
TeilFilename=XZD25A.Z.SSLTEIL

# The Damage Types
SSArt=1
ArtFilename=XZD25A.Z.SSLART

# The Function Groups
SSFGR=1
FGRFilename=XZD25A.Z.SSLFGR

# The plausibilities for IDIS/DAVIS
SSPlausi=0
PlausiFilename=XZD25A.Z.SSLPLAUSI

Basically the file consists of two basic section types:

[General]

This section occurs only once at the top of a configuration file. Here you can specify the root path for the files that will be spooled out. This also determines where the log file will be written to. The logfile will always be written into the root directory which was specified.

[set_<Name of package>]

A section of this type beginning with "set_" defines a package of files with specific attributes which shall be spooled out. It will also be referred to as "configuration set". It may occur several times with individual names. These names will show up on the User Interface.

Basically you begin specifying in which format you want the files to be spooled out:

1. Uppercase:
   "0" for normal case, "1" for uppercase texts ("1" can only be used with Format="ASCII" - see below)
2. SpoolSprache:
   The Daimler language number for the language in which to spool out the data. See the file example above for all valid languages
3. Format:
   This is basically the encoding of the file. Valid values are "ASCII" for ISO-8859-1 representation, "UTF8" and "UCS2" for double byte representation.

Next is to specify where the files shall be spooled on the file system and what files shall be written at all:

1. Relative_Path:
   This is the directory which will created below the directory specified in the Root_Path property and will contain all the selected files of this package. Typically the name of the package will also be used as a directory name.
2. The rest of the package definition is the statement, which files of the 5 different file types you want to be created (indicated by a "1") and which name you would like to be used for that individual file.
   SSRegel: 0 to omit "Damage Code Rules", 1 to create it.
   RegelFilename: Filename for "Damage Code Rules"
   
   SSTeil: 0 to omit "Damage Code Part Naming", 1 to create it.
   TeilFilename: Filename for "Damage Code Part Naming"
   
   SSArt: 0 to omit "Damage Types", 1 to create it.
   ArtFilename: Filename for "Damage Types"
   
   SSFGR: 0 to omit "Function Groups", 1 to create it.
   FGRFilename: Filename for "Function Groups"
   
   SSPlausi: 0 to omit "IDIS/DAVIS Plausibility", 1 to create it.
   PlausiFilename: Filename for "IDIS/DAVIS Plausibility"
    

14.1.4.2.1 Sample spoolout

The following sample of a configuration file will show the effect for the download page as a sample:

[general]

# Root_Path for spool files and the log file
# Note: Use your EWA net installation directory unless you really need to spool into a different location.
Root_Path=C:\Program Files\EWA net\downloads\spooler\damagecode

[set_Japanese_Files]
# Spool out in uppercase (1) or not (0)
Uppercase=0

# Language for which to create the spool outs:
# 20 = Japanese
SpoolSprache=20

# Allowed file format (encoding) values are ASCII, UTF8 and UCS2
Format=UTF8

# Directory under which to create the spool files relative to the root path
Relative_Path=Japanese_Files

# Define files which shall be spooled out as part of this set

# The DamageCode Rules file
SSRegel=0
RegelFilename=XZD25A.Z.SSLREGIE

# The DamageCode Part Naming
SSTeil=1
TeilFilename=XZD25A.Z.SSLTEIL

# The Damage Types
SSArt=1
ArtFilename=XZD25A.Z.SSLART

# The Function Groups
SSFGR=0
FGRFilename=XZD25A.Z.SSLFGR

# The plausibilities for IDIS/DAVIS
SSPlausi=0
PlausiFilename=XZD25A.Z.SSLPLAUSI




[set_German_Files]
# Spool out in uppercase (1) or not (0)
Uppercase=1

# Language for which to create the spool outs:
# 1 = German
SpoolSprache=1

# Allowed file format (encoding) values are ASCII, UTF8 and UCS2
Format=ASCII

# Directory under which to create the spool files relative to the root path
Relative_Path=German_Files

# Define files which shall be spooled out as part of this set

# The DamageCode Rules file
SSRegel=0
RegelFilename=XZD25A.Z.SSLREGIE

# The DamageCode Part Naming
SSTeil=1
TeilFilename=XZD25A.Z.SSLTEIL

# The Damage Types
SSArt=1
ArtFilename=XZD25A.Z.SSLART

# The Function Groups
SSFGR=1
FGRFilename=XZD25A.Z.SSLFGR

# The plausibilities for IDIS/DAVIS
SSPlausi=0
PlausiFilename=XZD25A.Z.SSLPLAUSI

You can see that both packages are shown on the screen. Each package is provided as a complete ZIP download package or as individual files along with their description.

15 Client software installation

15.1 Java Runtime Environment

Before users can start working with the EWA net clients (EWANAPI installer, EPC net, WIS net), you should ensure that the client systems are well prepared. If you have an officially supported  Java Runtime already installed on all the client machines, you are well prepared. Going to the Download Area of the User Management in your browser you will notice that the Web Application automatically tries to determine whether your clients are capable of executing EWA net.

If you need to install a Java Runtime Environment, you can make use of the one provided in the downloads section. Simply click on "Download and Install" which will download the appropriate Java Installer.

Note:
After successful installation of a new Java Runtime Environment you may have to log off and on again to update the System check display as it cashes the settings per session to avoid nasty dialogs.

15.2 EWANAPI (External API to call EWA net clients for DMS calls and/or Xentry integration) (ewanapi.exe / wisapi.exe)

EWA net provides an external application called EWANAPI.exe which allows external programs to communicate with the AccessGateway, the WIS net client  and/or the EPC net client.

This application was implemented with downwards compatibility in mind. Its command line arguments are compatible with the “classic” WISAPI.exe from the former WIS environment. It has been extended to support authentication at the AccessGateway and Shoppinglist calls to EPC net.

Note:
EWANAPI has matured from a simple DMS integration layer to an API which is heavily used by the Xentry applications like Xentry TIPS or Xentry Diagnostics. Therefore it is recommended to have EWANAPI installed in always the most current version on the client PCs. A so called "automatic deployment" supports to keep the clients up to date. Read more about this feature here.

15.2.1 Automatic Installation via the integrated EWANAPI Installer

EWA net provides a Java based installer which performs the necessary steps on each of the clients computers that otherwise would have to be executed manually.

The EWANAPI installer can easily be accessed from the Download section of EWA net. Simply click on the Download and Install button. You can also do this anytime you want to update your EWANAPI environment.

Note:
This step can only be performed once a correct version of Java has been installed on the client. If no Java has yet been installed, just install it via the appropriate Download and Install button just above the "EWANAPI/WISAPI" installer link.

15.2.1.1 Server side preparation (System administrators tasks):

The installer will always fetch the most recent EWANAPI installation files from the server installation directory [EWA-HOME]\clientapps\EWANAPI. The following files will be transferred to the clients by the installer:

• ewanapi.exe
• wisapi.exe
• ewanapi.ini
• hpwin32.dll
• ewanapi.jar

The executables, the JAR and the DLL will be copied to the client during installation as they are (Note: ewanapi.exe will also be installed as wis.exe during installation on the client for WIS Classic backwards compatibility).

The installer will check the directory for an appropriate ewanapi.ini file to read the settings from in the following order:

1. Check for an ewanapi.ini.<workshop_number>.
   The idea behind it is to allow a per workshop default setting which allows especially hosters of large central environments a high level of flexibility.
   Imagine a workshop still using Autoline 8.2. Let's assume this workshop has the workshop number "XG307". In this case you could copy the ewanapi.ini file with the name ewanapi.ini.XG307. Starting the installer from the download page will fetch the current users workshop information and try to read the workshop specific ewanapi.ini file and run the installation with settings provided there.
2. If such a file cannot be found the installer tries to read the file ewanapi.ini.installer.
3. If all those files could not be found the installer will fall back to the standard ewanapi.ini file and read its information for the installation from there.

Note:
The installer will take care about all these files and will migrate your existing settings during a software update on the server side.

The steps that now will be performed by the installer are

• The installer will check whether there is already a valid installation of EWANAPI on the client. If yes, it will switch itself into the update mode in which it just overrides the current installation with the most recent program files.
• If there is no installation found it will default to the mode which allows you to install EWANAPI completely from scratch on the client. Depending on what has been configured as a default installation directory for the EWANAPI files has already been chosen. This is typically something like "C:\Program Files\EWANAPI" (the Windows default directory for program installation). If really needed a different directory can easily be chosen by use of the "Browse ..." button.

Note:
The user running the installer must have sufficient user rights to install files into the chosen directory. Depending on the policies of your local Operating System he may not even be allowed to install files or create directories within "C:\Program Files\EWANAPI". In this case a different directory must be chosen or the user may have to ask the local system administration.

• It creates the installation directory on the target machine inside the selected directory (i.e. the Windows default directory for program installation) as %ProgramFiles%\EWANAPI directory.
• It copies the necessary files from the EWA net server onto the client PC
• It automatically adjusts the configuration file for EWANAPI (if auto-configuration values have been set in the configuration files (see table below). By default these values are being used. The installer makes use of placeholders within the ewanapi.ini file on the server to be expanded during installation within the local ewanapi.ini. See below for more information about these values:
   
• It extends the Windows system path variable (only if the user executing the installer has sufficient rights to do so; if not: simply extend the user's path variable). This step is needed to allow all system programs to find the ewanapi.exe without the need to know where exactly it is installed (required i.e. for the DMS Autoline)

Now for the tasks that you as system administrator will want to perform to influence the installation on the client side in the best way. The central point is the ewanapi.ini file. It contains a high level of flexibility to influence the client installation.

15.2.1.1.1 Automatic property replacement within ewanapi.ini

The following table documents that placeholders you can make use of if you like some properties to be filled automatically according to the runtime settings.

This allows high flexibility for the System Administrator. To allow the installer to derive the correct runtime settings from the server and automatically apply it to the EWANAPI installation on each of the clients, the pre-installed configuration file ewanapi.ini may directly be used.
But these values might also be overridden by static values.

Example:
If you specify:
Host=my.ewanet.com
the installer will leave this untouched.

But specifying
Host=%EWA_HOST%
indicates the installer it should replace this pattern by the server name that was used when accessing EWA net via the browser.

Hint:
The administrator might even decide to let EWANAPI determine the WebStart Installation automatically during runtime. In this case the complete line
WebStart=....
can be omitted or simply commented (default now in the delivered ini-file).

15.2.1.1.2 Influence target installation directory on the client PC

By default the preconfigured ewanapi.ini file will make the client installer install the EWANAPI files into %ProgramFiles%\EWANAPI. This behavior is controlled by the property:

[Installer]
InstallDir=%ProgramFiles%\EWANAPI
 

If you know of policies that inhibit the normal users in your environment to install in this directory because of insufficient rights do not let them run into trouble. Of course they can select a new path in the client anyway, but be so kind and change the default location already to a path where they will be allowed to install in. A fallback that should always work is:

[Installer]
InstallDir=%USERPROFILE%
 

15.2.1.1.3 Prefer SSO authentication before provided credentials

[General]
SSOPreferred=true

For environments that make use of NTLM Authentication within EWA net it might be very helpful to enforce EWANAPI to try NTLM authentication first before making use of any credentials provided to EWANAPI. Thus the authentication consists of a maximum of 2 steps:

1) Try to authenticate via NTLM. If this does not succeed, perform step 2

2) Try to authenticate via credentials provided.

Note:
This setting might be useful especially within EWA net environments where the EWA net user database is not yet synchronized with the Dealer Directory of Daimler.
A good example is a call from TIPS to EWA net where TIPS expects a user to be setup in the local EWA net system. But if the userid does not exist (is not synchronized) within the local EWA net server, the call will fail.
If the local EWANAPI.ini contains the flag "SSOPreferred=true" and the EWA net server is configured for NTLM authentication then the applet tries to first authenticate via NTLM. TIPS in this case can make the call with  userid which is currently known to the underlying Windows system and the local EWA net server.

15.2.1.1.4 Address Proxy settings / problems

Proxy settings will be handled automatically by WebStart in the same way like for all the EWA net clients. If the EWA net clients like WIS net or EPC net or even the EWANAPI Installer itself work fine in a given environment, EWANAPI will do so as well using exactly the same mechanisms in WebStart.

Note:
The proxy properties have gone from the EWANAPI.ini file. Adding them will not harm, but the information will not be used anymore by EWANAPI.

15.2.1.1.5 Preparation for Autoline 8.30 / 8.35 integration

Version of Autoline 8.3 and above provide an out of the box support of EWA net via EWANAPI. The tradeoff is that it currently expects some files to be located in the user profile. If those files are not present Autoline 8.3 will not enable the EPC or WIS/ASRA buttons. The best way to install EWANAPI on user's PCs is by use of the following settings - which have to be set on the EWA net server inside the file [EWA-HOME]\clientapps\ewanapi\ewanapi.ini:

[Installer]
InstallDir=%USERPROFILE%
Autoline_82_Enabled=false
Autoline_82_Allowed=false
Autoline_82_WISServer=
Autoline_82_EPCServer=
 

Note:
Modify the EWANAPI file on the server before you start installing EWANAPI on the clients! If you published EWANAPI to a client already before applying those changes on the server side, go ahead and deinstall EWANAPI on that client(s) and then install again after applying the changes on the server.

15.2.1.1.6 Preparation for Autoline 8.2 Emulation layer

For an Autoline 8.2 related installation the section for the Autoline 8.2 emulation layer must look like this - otherwise the user will not see the option for installation of the Autoline 8.2 emulation:

Note:
The user installing EWANAPI for an Autoline 8.2 integration must have administrative rights to be able to install distinct files and registry settings on the system for the Autoline 8.2 integration layer.

Note:
Once you installed EWANAPI with the Autoline 8.2 support enabled then any classic applications like WIS Classic and EPC FP will not work in an integrated way anymore. Leave the server side of these applications installed, but do not make use of the clients anymore.
A mixed environment is not supported and may lead to confusing situations.

[Installer]
InstallDir=%ProgramFiles%\EWANAPI
Autoline_82_Enabled=true
Autoline_82_Allowed=true
Autoline_82_WISServer=
Autoline_82_EPCServer=

 

Explanation:

• InstallDir:
  This property provides a recommended default for the user where on the client's PC the EWANAPI files will be installed. You can choose basically whatever directory the user has write access to. It is recommended to keep the given directory unless users run into problems when their PC's have highly restricted policies applied.
• Autoline_82_Enabled:
  Is the Autoline 8.2 emulation layer enabled by default? Should be set to "true". Will only be used if also Autoline_82_Allowed is set to "true".
• Autoline_82_Allowed:
  Is the emulation layer for Autoline 8.2 enabled at all? Must be set to "true" in this case..
• Autoline_82_WISServer:
  Provide the computer name of the server where the WIS server is installed and thus where the network shares for the JOBORDER directory are being accessed from. (\\<server>\JOBORDER)
• Autoline_82_EPCServer:
  Provide the computer name of the server where the EPC FP server is installed and thus where the network shares for the shopping list transfer files directory are being accessed from. (\\<server>\MBXX-mbxx)
   

15.2.2 Automatic Deployment of EWANAPI

EWA net supports a new feature called "AutoDeployment". This feature has been introduced with early Xentry releases as Xentry highly relies on EWANAPI as an integration layer.

The idea of automatic deployment is, that an EWA net user will not have to take care about a renewal of an EWANAPI release on his client. In former times of EWA net, deployment was implemented via a kind of a pull-mechanism, i.e. the user had to check for a new release on the server by himself. By use of automatic deployment, this can be switched now to a push-mechanism, i.e. the user will automatically be notified in case of a new release on the server.

The check of a new release is triggered during the start of the EWA net clients (WIS net or EPC net): after startup, the application will query the current version of EWANAPI on the server. Based on the check of the "Version" field a more recent file on the server can be detected. In such a case the user will be notified. He than can decide to directly install the new EWANAPI or to delay the installation.

Automatic deployment can be controlled by the following attributes as part of the [Installer] section within the  ewanapi.ini file(s) on the server:

In addition to these attributes, the following principles will additionally control automatic deployment:

• Automatic deplyoment can be deactivated for performance-tests to avoid unnecessary server contacts and unexpected stops of automatic test flows. Therefore, you have to set attribute ewa.client.connectivity.performance to "true", i.e.
  <property name="ewa.client.connectivity.performance" value="true"/>. This setting has to be done inside your jnlp launcher-file.
   
• Automatic deployment will never start the installer on Star Diagnosis Systems.
   
• The automatic deployment attributes as described above are read from the server in the following cascade (as mentioned already above):
  try to find ewanapi.ini.<Workshop ID of user>, i.e ewanapi.ini.000001
  if not available try to find ewanapi.ini.installer
  if not available try default file ewanapi.ini
   
• Automatic deployment will only give a notification, if the server's version of EWANAPI is more recent than the client version or if the client version does not indicate a version at all.

The following diagram shows the complete control of the automatic deployment:
 

15.2.3 Manual Installation

On the delivery media you will find the WISAPI/EWANAPI program along with the required components in the folder:

[DVD-DRIVE]:\ewa\Apps\ewanapi\application

You can also find it after installation within the server installation directory

[EWA_HOME]:\clientapps\ewanapi

If you want to use these components, installation is fairly simple:

• Copy the folder including all files anywhere you like on the client’s system, i.e.
  C:\Program Files\EWANAPI
• Extend the system’s path variable by this folder.
  This is needed to ensure that both the executable as well as the DLL can be found.

If you enter “ewanapi.exe” or “wisapi.exe” in a Console window now, you should see a usage information listing all parameter sets that are known to ewanapi.exe.

15.2.4 Configuration

Configuration has to be performed in the ewanapi.ini file. Adjust the values inside this file according to your needs.

• Adjust at least the property “Server” pointing to the application server of your specific application.
• If SSL is used, change “Port” to "8443" (or whatever you have set the secure port to) and set “Secure-HTTP” to "true".
• If you explicitly make use of the property WebStart to clearly tell EWANAPI which Java WebStart it should use, ensure that this property really points to the Java WebStart executable javaws.exe.
  As this locations varies with each different version of a client java, you will have to check and possibly adapt it to your special environment.
  If you are not sure about the path, just comment this property and let EWANAPI do the job itself. It will then dynamically find the current WebStart application from the Windows Registry. This is the recommended way.
• The variables %HOMEDRIVE% and %HOMEPATH% are Windows environment variables directing to the user's home directory. These do not need to be changed typically.

15.2.5 Proxy Server Configuration for EWANAPI

Proxy settings will be handled automatically by WebStart in the same way like for all the EWA net clients. If the EWA net clients like WIS net or EPC net or even the EWANAPI Installer itself work fine in a given environment, EWANAPI will do so as well using exactly the same mechanisms in WebStart.

Note:
The proxy properties that were part of the early configuration files of EWANAPI have gone from the EWANAPI.ini file. Adding them will not harm, but the information will not be used anymore by EWANAPI.

15.2.6 Example of an ewanapi.ini file

Following dump shows a sample ewanapi.ini file. Highlighted properties may be changed already on the server side's ini-file to preset valid values for the clients or may be set on the client side later on:

[HTTP-Config]
##################################
# ATTENTION!!!
##################################
# Some parameters are being set to
# %EWA_xxx%
# These will be replaced by the automatic installer for EWANAPI
# If you want to make those values explicit or do not distribute EWANAPI via the installer,
# please adjust the values on your own before distributing EWANAPI.
# EWANAPI will not work if it is being installed with those values during runtime.
##################################
#
#
# Name of the Server where the AccessGateway is installed
Server=%EWA_HOST%
# Server=localhost  
#   if you want to state a server explicitly for all clients in advance
#
# Port on which the application is listening
# Typically this is 9000 for a normal HTTP connection, 8443 for a HTTPS connection
Port=%EWA_PORT%
# Port=9000         
#   if you want to specify a port explicitly for all clients in advance
#
# Will you use HTTPS for a secure connection?
Secure-HTTP=%EWA_SECURE%
# Secure-HTTP=false
#

[Files]
# Where to store data files
# For future use maybe, not yet supported
WIS-Net_DATA=%HOMEDRIVE%%HOMEPATH%\data_wis.txt
WIS-Net_ERROR=%HOMEDRIVE%%HOMEPATH%\error_wis.txt
EPC-Net_DATA=%HOMEDRIVE%%HOMEPATH%\data_epc.txt
EPC-Net_ERROR=%HOMEDRIVE%%HOMEPATH%\error_epc.txt

[General]
Version=1.5.2.0
# Maximum seconds to wait until application has to respond on the channel
Timeout=60
# For STAR DIAGNOSIS and STANDALONE environments set this to "true"
Standalone=false
# Let the system find the file on its own
#WebStart=%EWA_WEBSTART%
# WebStart=%ProgramFiles%\Java\j2re1.4.2_05\javaws\javaws.exe
Extended_Parameters=
#WIS-Net_StarterApplication=%ProgramFiles%\Citrix\ICA Client\wfcrun32.exe "%ProgramFiles%\EWACTXCL\CTX-WIS.ica"
#EPC-Net_StarterApplication=%ProgramFiles%\Citrix\ICA Client\wfcrun32.exe "%ProgramFiles%\EWACTXCL\CTX-EPC.ica"
SSOPreferred=false

[Standalone]
WIS-Net_EXE=%WISNETEXE%
# Not yet supported as there is not yet a standalone EPC net
EPC-Net_EXE=%EPCNETEXE%

[Installer]
# For Autoline 8.3x support choose
# InstallDir=%USERPROFILE%
InstallDir=%ProgramFiles%\EWANAPI
Autoline_82_Enabled=false
Autoline_82_Allowed=false
Autoline_82_WISServer=
Autoline_82_EPCServer=
# How do we want to control the automatic publication of EWA net clients?
# Valid values are:
# None: No check will ever be performed by this client
# CheckUpdate: Checks for new versions will only be performed if there is already an EWANAPI locally installed on that client
# CheckInstallAndUpdate: Enforce updates and even new installations if there is not yet an EWANAPI locally installed on that client
Autodeployment=CheckInstallAndUpdate
# Do we want to trace whether we accidently moved to another EWA net server?
# true: it will be monitored whether the current connection contacts the same server as the one registered inside EWANAPI
# false: there is no monitoring active at all
TraceServerChanges=true
# Do we want to leave an EWANAPI cookie on the client ?
# true: the client will leave the information about: EWA net Server, HTTP-Port and HTTP(S) inside a small ".ewanapi_cookie" file in the user's home directory
# false: no cookie will be left
LeaveCookie=true
# The number of seconds after which a timeout will occur if the files which need to be overwritten during the install process are still locked.
TimeoutStillLocked=120

16 Server Monitoring and Management

16.1 Introduction

When having the EWA net server installed the administrator needs to ensure that it will be up and running most of the time. EWA net therefore enables the administrator to monitor the installation as well as the running instances with a central interface.

The first approach for monitoring the state of the server is to check if it is reachable using the browser. If the server is not reachable a view to the log files will be the second step to check why the server is not available.

It is always recommended to modify the logging depending on your needs. further details regarding logging are described in the advanced configuration section for logging.

Besides the logging information and the browser checks, EWA net provides an additional interface to monitor the runtime state of the server. The requirement for this additional interface is, that the Java server is active. If enabled, runtime monitoring information of the application can be retrieved very detailed using a separate interface.

16.2 Management Interface Architecture

The management interface of EWA net is based on the Java Management Extensions (JMX) standard. EWA net as application integrates into the existing management frameworks on the given application server. Besides the documented features, the common JMX standards and features also apply on the EWA net implementation.

The JMX architecture is built according to a three-level model. This gives flexibility by allowing subsets of the specification to be used individually by different developer communities utilizing Java technology.

• Instrumentation level - gives instant manageability to the objects of the application. The application components can expose different parts for management.
• Agent level - provides management agents. JMX agents are containers that provide core management services which can be dynamically extended by adding JMX resources. EWA net ships per default using a HTTP adapter to allow management via Browser. However further adapters can be applied.
• Manager level - provides management components that can operate as a manager or agent for distribution and consolidation of management services. This level is aimed at the management solutions development community and completes the management through Java technology provided by the Agent level. The manager level is not distributed within EWA net and needs to be build specific for every installation. This will be depended of the environment of the installation.

Further documentation of the JMX capabilities and limitations can be found on the JMX homepage http://java.sun.com/products/JavaManagement.

16.3 Management Configuration Options

The management service inside EWA net is disabled per default. To use the EWA net management features you need to enable the service in the configuration. When enabling the management service, please do not forget to also modify the other parameters as they are very important for the security.

All management service related parameters are contained in in [EWA_HOME]\config\core_cfg.xml. The following options are relevant for the management service interface:

Section Services / ManagementService:
All options in this section configure the management service in general.

Section Services / ManagementService / HttpAdapter:
Options in this section configure the behavior of the HTTP adapter which ships together with EWA net.

16.4 Management Interface Usage and Options

To use the management HTTP interface, log in as administrator on the EWA net server and navigate to "Server Management".

Then use the link presented at "Show Management Console" to run the HTTP adapter page.

Note:
When this link is disabled, please check the configuration.

If the page is displayed you will see an overview screen of the server state which allows to drill down to details.

When clicking on the details links, details of components, configuration and statistics will be displayed.

Using the link "Follow this link to see all management server details" will open up the regular JMX console and display all management object details.

16.4.1 Web Server Interface

The web server will expose all its internal management objects to the EWA net management service. All components which are listed beneath "Other Domains" in the overview page are exposed by the web server or the JMX implementation itself.

A detailed description of the possible options of the objects are described on the screen.

For further details, please refer to the documentation of Tomcat.

16.4.2 EWA net Core Components Interface

The EWA net core components are exposing with a name beginning with "EWA net Core: ". Several objects are included to view details of the server runtime and monitor the state as well as performance metrics. Some self test beans are available to run tests and verify that business logic is still working correctly.

The EWA net management information is separated into State, Statistic and Configuration sections. Please drill down into the management page to figure out which options apply. The statistics section for example provides an overview how long request processing for each application takes as average or how long authentication takes to process. If you experience performance options you can monitor the statistics numbers.

The State of the EWA net core components also provides information about access authorization usage.

16.4.5 Retrieving Management Information

The Management information is available through 4 interfaces:

1. Log on as administrator onto the administration page and use the menu "Administration" --> "Server Management" --> "Show Management Console". This will generate a basic interactive overview in your browser rendered as HTML. This is for use for simple checks and basic overview.
2. Use the HTML management interface provided by the build in management server which is configured in core_cfg.xml. The URL is usually http://localhost:9030/ on the application server. This overview will basically list all components with the base data. All information is presented "as-is" without aligning into functionality groups. You can click on each entry to view details of attributes.
3. Download XML information using the Administration interface of EWA net. For details about retrieving XML information see the following chapter
4. Attach a JMX Adapter to the application server and connect this to your monitoring infrastructure.

16.4.6 Retrieving XML Information of Management Information

To retrieve Management information of the server, call the server with a URL like the following:

http://myewanet:9000/EWA-net/jmx?userid=admin&password=secret

This will generate output similar to the management overview page discussed in previous chapters. Besides the basic generation further options can be specified on the URL. Please see the following table about possible options:

17 Performance optimization & fine tuning

17.1 Introduction

An important goal of the EWA net system is it to answer clients in a reasonable good time. The system has to do this under extreme circumstances. It may has to process a lot of requests from many clients in parallel. Sometimes it will be the only solution to add new hardware to deliver an acceptable good overall performance. Still, often the system performance can be improved drastically by tuning some configuration parameters, since most times standard parameters are not optimized for performance but for stability. Which settings are most effective without reducing system stability has to be figured out during stress tests at the hosting site. This guide will address some common performance issues, and it gives a solution approach for each identified issue. The guide does not claim to address all possible performance issues. Especially the optimization of the operating system and application server should be core competence of the individual hoster.

Figure: Pillars of Performance

The general approach is it to optimize performance in three different system “parts” (pillars) on the local machine (optimization besides the server itself or hardware optimization are out of the scope of this guide).

1. The operating system has to be configured for a server system. E.g. the socket settings of the system need to be appropriate for a large number of parallel requests.
2. The applications server needs to be configured for the specific scenario (e.g. number of requests per second, typical response time, …).
3. The EWA net applications (including commonly shared components like the Access Gateway) need to be optimized for the specific system environment (e.g. depending on whether the User Management resides in the LAN or a WAN).

Each of these three areas needs to be optimized to get the best overall system performance. Tuning those can improve performance by much more than 100% in total. It also can help stabilizing the system by setting it up for the expected amount of concurrent requests. The following sections will address some of those performance issues. Still, all settings have to be verified for the specific hosting environment.

17.2 Operating System

First step is to tune the operating system where the application server resides on.

17.2.1 Socket Timeout (Windows)

Description: The default timeout for tcp sockets is set to 240 seconds. That means a socket waits 240 seconds on its last usage until it closes. Due to the limited number of available sockets this effectively reduces the maximum number of connections.

Solution approach: If the registry value “TcpTimedWaitDelay” is not in the registry, create that value. Set the value to 30 (or any feasible low value).

System Key:[HKEY_LOCAL_MACHINE\System\CurrectControlSet\Services\Tcpip\Parameters]
Value Name: TcpTimedWaitDelay
Data Type: REG_DWORD (DWORD Value)
Value Data: 30 - 300 seconds (decimal)

For details refer to http://www.winguides.com/registry/display.php/878/

17.4 Tomcat Settings

As the general performance of modern machines is growing constantly more and more Users can connect to one server at the same time. The increased number of connections lead to an increased number of threads on the Tomcat Server. So servers under heavy load should increase the maxThreads value to 400 in the server.xml.

          
        <Connector port="8443"
                   protocol="HTTP/1.1"
                   maxHttpHeaderSize="8192"
                   acceptCount="300"
                   maxThreads="400"
                   minSpareThreads="25"
                   maxSpareThreads="75"
                   enableLookups="false"
                   scheme="https"
                   secure="true"
                   clientAuth="false"
                   connectionTimeout="60000"
                   disableUploadTimeout="false"
                   keystoreFile="[EWA_HOME]/certificates/ewanet.jks" 
                   keystorePass="changeit"
                   sslProtocol="TLS" />

17.5 Application Settings

At some points the applications can be tuned for better performance.

17.5.1 Logging (AccessGateway)

Description: The AccessGateway and the HP Services feature a logging mechanism. The logging setup may eat up system performance, if many entries are written to the hard disk. Because this may interfere with local database access or other file operation.

Solution: In the HP configuration of the logging (log4j_config.xml) tune the settings for the logging. You can adjust the level (and in relation to that the amount of info) to be logged.

Example:

[...]
<root>
  <priority value="INFO"/>
  <appender-ref ref="HTML" />
  <appender-ref ref="STANDARD_FILE" />
  <appender-ref ref="DCMONFILE_ERROR" />
</root>
[...]

If you set this to “DEBUG” you will get a lot of information - too much for a typical runtime environment. Do this only in case that your system has trouble. Too much logging will end in a heavy server performance decrease.

17.6 Database Settings

17.6.1 Shared Memory Configuration for Transbase

Description: With the standard installation of Transbase (valid for all TransBase versions <= 5.3.1.47) the Multiplexer service will be installed to run under the local system account with the option “Allow service to interact with desktop” unchecked.

This setting will limit the amount of shared memory that can be used for TransBase connection processes. That way large installations might run into problems if a lot of connections are in use (there is no fixed limit – it varies from system to system).

Solution: There are two ways now to address this limitation:

1) Please set the property “Allow service to interact with desktop” for the TransBase services is set in the registry to "true".

2) Directly go to the registry with “regedit.exe”.
Go to the hive “HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\”
and edit the entry “Type” in each of the hives
”EWA net DB Core”
”EWA net DB WIS net”
”EWA net DB EPC net”
Modify the initial HEX-Value from “0x10” to “0x110”

Note:
This will already be done by the installers for the TransBase versions used by the Core and by WIS net.

There is also a knowledge base entry from Microsoft regarding general memory limits of windows background services. See the knowledgebase entry at http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q184802&

In short words you can use the registry editor and modify the value
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Window

Editing this value you will find a string part indicating something like
“... SharedSection=1024,3072,512 ...”
Modify the 3^rd value to at least 1024. This will have an effect an all background services running on Windows.

17.6.2 Increasing WIS net Transbase Cache Settings

Description: The WIS net database is configured per default with very conservative caching settings. In Load tests an increase of the database cache sizes can increase the performance.

Solution: To discover the current settings for caching inside Transbase WIS database execute the following command:
[EWA_HOME]\database\TransBase WIS>tbadm32 -i wisnet

@(#) tbadm32
Version: V5.3.1.53 (Build 410) 2004/05/24 (Release)
License: 32966BFA-F9944C00-22F9F47F-F581F07D

U.S.-Patent Nr. 6,381,596 and 6,510,335

Copyright (c) 1987 - 2004 by Transaction Software, D 81737 Munich



Database Name       = wisnet@schefflerjens
Database Home       = C:\Data\026_EW~1\Install\database\DATABA~2\wisnet
Bfim/Log Path       =        ~\bfims
Scratch Path        =        ~\scratch
Accounting Path     =        ~\account\acctlog

Size(MB) Blob Diskfile Path
     976   No C:\Data\026_EW~1\Install\database\DATABA~2\wisnet\disks\tbdsk001

Database Romfile(s)
C:\DB\WIS\wisnet\012005~2\R0\rfile000                    on CD-ROM 'CD_1'
C:\DB\WIS\wisnet\012005~2\R1\rfile001                    on CD-ROM 'CD_2'
C:\DB\WIS\wisnet\012005~2\R2\rfile002                    on CD-ROM 'CD_3'
C:\DB\WIS\wisnet\012005~2\R3\rfile003                    on CD-ROM 'CD_4'
C:\DB\WIS\wisnet\012005~2\R4\rfile004                    on CD-ROM 'CD_5'
C:\DB\WIS\wisnet\012005~2\R5\rfile005                    on CD-ROM 'CD_6'
C:\DB\WIS\wisnet\012005~2\R6\rfile006                    on CD-ROM 'CD_7'

Page Size           = 2     KB          Rom Size            = 4687  MB
Data Cache          = 512   KB          Sorter Cache Size   = 512   KB
Number of Users     = 254               Dbident             = 211
DB Type             = CD_Retrieval      DB-Identification   = RETRIEVAL SYSTEM
min multiplexed     = 0                 max multiplexed     = 0
Locale setting      = German_Germany.125Codepage            = Propriet
Accountlog          = off (NONE)
Case Insensitivity  = off               Status              = booted
Encryption = no

When increasing the cache sizes, it is proposed to extend data and sorter cache sizes in an equal number. The configured amount of space will be allocated during startup of the database. The allocated memory will be shared within the database instance.

Note:
You need to ensure that for changes of the cache sizes enough system memory is available. The cache setting for all WIS net and EPC net databases needs to be suitable for the amount of memory available.

To change the cache values, execute the following commands:

Step 1: Stop EWA net Server
[EWA_HOME]\database\TransBase WIS>net stop "EWA net Server"

The EWA net Server service is stopping.
The EWA net Server service was stopped successfully.

Step 2: Stop EWA net WIS Database
[EWA_HOME]\database\TransBase WIS>net stop "EWA net DB WIS"

The EWA net DB WIS service is stopping.
The EWA net DB WIS service was stopped successfully.

Step 3: Modify the Cache Settings (This example: 2MB data + 2MB sorter cache)
General command line of this command is:
tbadm32 -af wisnet nc=<data cache> lc=<sorter cache>

The cache size is defined as Kilo-Bytes (KB). If more than 2MB should be used for data cache, you need to add a muliplier to define the number of cache pages, for example:

[EWA_HOME]\database\TransBase WIS>tbadm32 -af wisnet nc=8*2048 lc=16384

@(#) tbadm32
Version: V5.3.1.53 (Build 410) 2004/05/24 (Release)
License: 32966BFA-F9944C00-22F9F47F-F581F07D

U.S.-Patent Nr. 6,381,596 and 6,510,335

Copyright (c) 1987 - 2004 by Transaction Software, D 81737 Munich


alter database wisnet: shutdown, entry altered, database booted

Step 4: Check the settings again
[EWA_HOME]\database\TransBase WIS>tbadm32 -i wisnet

@(#) tbadm32
Version: V5.3.1.53 (Build 410) 2004/05/24 (Release)
License: 32966BFA-F9944C00-22F9F47F-F581F07D

U.S.-Patent Nr. 6,381,596 and 6,510,335

Copyright (c) 1987 - 2004 by Transaction Software, D 81737 Munich



Database Name       = wisnet@schefflerjens
Database Home       = C:\Data\026_EW~1\Install\database\DATABA~2\wisnet
Bfim/Log Path       =        ~\bfims
Scratch Path        =        ~\scratch
Accounting Path     =        ~\account\acctlog

Size(MB) Blob Diskfile Path
     976   No C:\Data\026_EW~1\Install\database\DATABA~2\wisnet\disks\tbdsk001

Database Romfile(s)
C:\DB\WIS\wisnet\012005~2\R0\rfile000                    on CD-ROM 'CD_1'
C:\DB\WIS\wisnet\012005~2\R1\rfile001                    on CD-ROM 'CD_2'
C:\DB\WIS\wisnet\012005~2\R2\rfile002                    on CD-ROM 'CD_3'
C:\DB\WIS\wisnet\012005~2\R3\rfile003                    on CD-ROM 'CD_4'
C:\DB\WIS\wisnet\012005~2\R4\rfile004                    on CD-ROM 'CD_5'
C:\DB\WIS\wisnet\012005~2\R5\rfile005                    on CD-ROM 'CD_6'
C:\DB\WIS\wisnet\012005~2\R6\rfile006                    on CD-ROM 'CD_7'

Page Size           = 2     KB          Rom Size            = 4687  MB
Data Cache          = 16    MB          Sorter Cache Size   = 16384 KB
Number of Users     = 254               Dbident             = 211
DB Type             = CD_Retrieval      DB-Identification   = RETRIEVAL SYSTEM
min multiplexed     = 0                 max multiplexed     = 0
Locale setting      = German_Germany.125Codepage            = Propriet
Accountlog          = off (NONE)
Case Insensitivity  = off               Status              = booted
Encryption = no

Step 5: Start the WIS Database
[EWA_HOME]\database\TransBase WIS>net start "EWA net DB WIS"

The EWA net DB WIS service is starting.
The EWA net DB WIS service was started successfully.

Step 6: Start EWA net Server again
[EWA_HOME]\database\TransBase WIS>net start "EWA net Server"

The EWA net Server service is starting.
The EWA net Server service was started successfully.

Results from first performance tests showed that the database performance did not very much increase when setting cache sizes to very high numbers of ~100MB. Ideal tuning parameters are currently not available but the current assumption is that a small value is sufficient for most cases.

Note:
The cache sizing will be overwritten by AdminTool whenever the database is switched and/or updated. You need to take care that the configuration in re-applied after each data update!

<SECTION name="pool">
  (...)
  <SECTION name="db">
    (...)
    <PARAMETER name="size">50</PARAMETER>
    (...)
</SECTION>
</SECTION>

18 General Information

18.1 Filesystem structure

18.1.1 Delivery media (DVD)

The following sections provides a short overview over the disc layout to give a better understanding of what to find in which directory.

18.1.2 Filesystem layout on the target system

This section describes the target layout of the EWA net directory which you will do your modifications and adjustments in. Folders that remain untouched are being displayed with a grey background.

19 Backup and Migration Tool

19.1 Purpose of the Back up and Migration Tool

The purpose of the Backup and Migration Tools is to help with the backup and the migration of workshops, groups and users. It is an command-line based tool which allows an easy integration into scripts. Because its dynamically configurable even big clusters can be backupped dynamically.

19.1.1  

19.1.2 Configuration of the Backup and Migration Tool

The basic configuration is done with a configuration file. This File uses the standard Java-properties-syntax. This means that the different parameters are written like this:

parameter-value = value.

Comments have to be market with a # (=Hash sign).

This configuration-file contains the following types of parameters:

• Task type

• Data-Source

• Data-Target

• Filters

The task-type defines what kind of task should be performed. Data-Source and Data-Target contains information if the source or the target is a file or a database.

Filters specify if only specific datasets should be copied.

The following section describes the configuration-parameters which have to be listed in the configuration-File.

19.1.3 1.1           Task Type configuration options

Currently there are the tasks Copy and Migrate where copy just copies the data from source to target while migrate is also deleting the data from the *source. Please note that just the Workshops, Groups, Users and  the  GeneralStorageService(GSS) is copied with this tasks. Fins and sessions are ignored. To copy the whole content use the Backup-Task. Note that that is just valid if you are copying an database to an file.

So a valid entry in the config-file would be: Task=Copy

*Here is an List with the possible configuration of tasktypes and tasks

19.1.4 1.2           Defining source and target

The description of source and target is achieved with the prefix Source or Target followed by the data provider. So a valid call for a source file would be Source.File=c:\\backup.xml.

Note that if your target is a file then there is the opportunity to add wildcards so that there is a timestamp and/or the hostname/ipaddress added to the name of the backup xml-file. This allows the user to run automated backups without overwriting the old backups and recognize the machine from where the backup came.

Note:
If you use the wildcard %hostname% then the hostname is extracted from the source-database-connection-string

To use the wildcard insert an %timestamp% and/or %hostname% in the filename. So an example-statement looks like this:

Target.File=c:\\%timestamp%_backup.xml

This will result in an file which will look somewhat like this:  2007.12.20-01-01-01_backup.xml.  It will be located in c:\ .

Another sample would be:

Target.File=c:\\%hostname%_backup.xml

This will result in a file which will look somewhat like this:  16.57.51.133_backup.xml depending on the sources IP-Address.

19.1.5 1.3           Defining an database

The description of a database consists of four parameters.

•         DBDriverClass – The Java driver class to use

•         DBURL – The JDBC URL to use for connection to database

•         Username

•     Password

The Database-drivers and connections-strings for the standard EWA net databases are listed below:

For example a valid database-description would look like:

Source.DBDriverClass=transbase.jdbc.Driver

Source.DBURL=jdbc:transbase://localhost:2044/ewacore

Source.Username=tbadmin

Source.Password=

19.1.6 1.4           Defining an Filter

There are several filters provided to copy just parts of the data. These are User, UserGroup and Workshop.

User copies a specific user including the related user group and workshop.

UserGroup copies all related users to listed Group as well as the related workshops.

Workshop copies all related groups und users for the listed workshop.

A Filter works always no matter if a copy or restore-process is started.

There is just one filter-type at once allowed.

Each ID of the desired Entity has to be listed on a new line with an unique number which is increased by one compared to its ancestor. The fist filter entity has to marked with a one .

So the content of a workshop-configuration-file could look like this:

 Filter.Type=Workshop

Filter.Workshop.1=XX898sd987dsf44

Filter.Workshop.2=XX898sd987dsf454

Filter.Workshop.3=XX898sd987dsf500

19.1.7 1.4.1       Filtering administrator-users

Per default every administrator-user is sorted out while migrating the data. This is done to prevent previous administrators from local installations to overtake central hosted farms . To override this setting the following line has to be added to the configuration.

KeepAdministrator = true

19.1.8 1.5           Sample Configuration Files

Integrate specific workshops from a backup 

19.1.9 2      Logging

There will be a log file stored in the folder from where the bam-tool is executed. It will contain information about the process-settings itself followed by information about the result of the copy-process.

19.1.10 3      Running the tool

The EWA BaM tool is started from the command line. For that the name of the configuration has be added. So a valid call would be:

If no or no valid config-file is found then there will be a warning displayed and the application is going to exit.

If the application is successfully exiting then there is the SystemCode 0 returned. The returncode -1 is returned in case of an error.

  <!--
      Define an AJP 1.3 Connector on port 8009
<Connector port="8009" 
    backlog="200"
    maxThreads="200"
    enableLookups="false"
    redirectPort="8443"
    secure="false"
    protocol="AJP/1.3"
    tomcatAuthentication="false" />
 -->

  <!--
      Define an AJP 1.3 Connector on port 8009
  -->
<Connector port="8009" 
    backlog="200"
    maxThreads="200"
    enableLookups="false"
    redirectPort="8443"
    secure="false"
    protocol="AJP/1.3"
    tomcatAuthentication="false" />

<SECTION name="AccessGateway">
    <SECTION name="ApplicationSettings">
    <!-- SSL within EWA net - do not forget to configure your server accordingly -->
     <PARAMETER name="sslEnabled">false</PARAMETER>
        <!-- currently SSL for Client apps is not supported. Future use. 
        Needs further extension of SSL for Struts -->
        <PARAMETER name="sslForClientsEnabled">false</PARAMETER>
     <PARAMETER name="httpPort">80</PARAMETER>