ae virsa installation guide

Installation Guide

Virsa Access Enforcer™ Version 5.2for SAP WAS 700

COPYRIGHT

© Copyright 2006 SAP AG. All rights reserved.

SAP Library document classification: PUBLIC

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.

Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc.

HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and implemented by Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

Virsa, Virsa Systems, Access Enforcer, ComplianceOne, Compliance Calibrator, Confident Compliance, Continuous Compliance, Firefighter, Risk Terminator, Role Expert, the respective taglines, logos and service marks are trademarks of SAP Governance, Risk and Compliance, Inc., which may be registered in certain jurisdictions.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves information purposes only. National product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP AG and its affiliated companies (“SAP Group”) for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.

2

SAP—Important Disclaimers

SAP Library document classification: PUBLIC

This document is for informational purposes only. Its content is subject to change without notice, and SAP does not warrant that it is error-free. SAP MAKES NO WARRANTIES, EXPRESS OR IMPLIED, OR OF MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE.

Coding Samples

Any software coding and/or code lines/strings (“Code”) included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding. SAP does not warrant the correctness and completeness of the Code given herein, and SAP shall not be liable for errors or damages caused by the usage of the Code, except if such damages were caused by SAP intentionally or were grossly negligent.

Internet Hyperlinks

The SAP documentation may contain hyperlinks to the Internet. These hyperlinks are intended to serve as a hint where to find supplementary documentation. SAP does not warrant the availability and correctness of such supplementary documentation or the ability to serve for a particular purpose. SAP shall not be liable for any damages caused by the use of such documentation unless such damages have been caused by SAP’s gross negligence or willful misconduct.

Accessibility

The information contained in the SAP Library documentation represents SAP’s current view of accessibility criteria as of the date of publication; it is in no way intended to be a binding guideline on how to ensure accessibility of software products. SAP specifically disclaims any liability with respect to this document and no contractual obligations or commitments are formed either directly or indirectly by this document. This document is for internal use only and may not be circulated or distributed outside your organization without SAP’s prior written authorization.

3

CONTENTS

Preface

About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Alert Statements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

Product Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9Documentation Formats . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .9

Installation Guide, Configuration Guide, User Guide, and Release Notes . . . . . . . . . . . . . . . . . . . . .9

Contacting SAP GRC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10

1 Installation Overview

How to Use This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Installation Pre-requisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Software Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Configuration Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

Memory Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13

2 Virsa Access Enforcer Installation

Pre-installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16Virsa Access Enforcer Installation Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Before You Begin! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Deploying the Virsa Access Enforcer Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

Restarting the NetWeaver J2EE Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18

3 Post-installation Configuration

Virsa Access Enforcer Post-installation Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22Importing the Virsa Access Enforcer Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22

Assigning the AE Admin Role to the Administrator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24

Importing Initial Virsa Access Enforcer Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

Connecting a Standalone J2EE System to the Remote SAP Server . . . . . . . . . . . . . . . . . . . . . . . . . . .28

5

Virsa Access Enforcer Version 5.2Installation Guide

A Upgrading From a Previous Version of Virsa Access Enforcer

Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32The Upgrade Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32

Upgrading Access Enforcer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33Pre-upgrade Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .33

Configuring Memory Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Upgrading the Deployed Access Enforcer Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

Importing Virsa Access Enforcer Roles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Upgrading Virsa Access Enforcer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36

Importing Initial Access Enforcer Configuration Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

6

PREFACE

TOPICS COVERED IN THIS PREFACE

About this Guide

Conventions

Alert Statements

Product Documentation

Documentation Formats

Installation Guide, Configuration Guide, User Guide, and Release Notes

Contacting SAP GRC

7

Virssa Access Enforcer Version 5.2Installation Guide

About this Guide

Conventions

The following conventions are observed throughout this document:

• Bold sans-serif text is used to designate file and folder names, dialog titles, names of buttons, icons, and menus, and terms that are objects of a user selection.

• Bold text is used to indicate defined terms and word emphasis.

• Italic text is used to indicate user-specified text, document titles, and word emphasis.

• Monospace text (Courier) is used to show literal text as you would enter it, or as it would appear onscreen.

Alert Statements

The alert statements—Note, Important, and Warning—are formatted in the following styles:

Note Information that is related to the main text flow, or a point or tip provided in addition to the previous statement or instruction.

Important Advises of important information, such machine or data error that could occur should the user fail to take or avoid a specified action.

Warning Requires immediate action by the user to prevent actual loss of data or where an action is irreversible, or when physical damage to the machine or devices is possible.

8

Product DocumentationPreface

Product Documentation

Documentation Formats

Documentation is provided in the following electronic formats:

• Adobe® Acrobat® PDF files

You must have Adobe® Reader® installed to read the PDF files. Adobe Reader installation programs for common operating systems are available for free download from the Adobe Web site at www.adobe.com.

Installation Guide, Configuration Guide, User Guide, and Release Notes

You can download the Installation Guide, Configuration Guide, and User Guide, and Release Notes in PDF format.

9

Virssa Access Enforcer Version 5.2Installation Guide

Contacting SAP GRC

For information on contacting SAP Governance, Risks, and Compliance (SAP GRC), go to the SAP Support Portal which can be found on the SAP Service Marketplace at: service.sap.com.

In order to use the SAP Support Portal you will need to log in using your SAP user account. If you do not already have an existing SAP user account, you must first create a new account. At the bottom right area of the SAP Service Marketplace page, under the “Questions Regarding Login?” heading, click the “New User? Register here!” link. You will be prompted for a Customer Number or Installation Number which you can get from your SAP Basis Administrator. (In an SAP system you can find your installation number under System -> Status -> SAP System data.)

To submit your support request(s) from the SAP Support Portal, use the quick-link “Messages” and follow the “SAP Message Wizard” procedure. All support requests should be logged under the following SAP GRC support components:

• GRC-SAE Virsa Access Enforcer

• GRC-SCC Virsa Compliance Calibrator

• GRC-SFF Virsa Firefighter for SAP

• GRC-SRE Virsa Role Expert

For more information on the SAP Support Portal, use the quick-links provided below:

• SAP Notes Search Here you can search for reference material and possible solutions for any questions regarding the GRC components.

• Messages Here you can create Support Messages for the GRC components.

• Software Download Here you can download installations, upgrades, and support packages.

• SAP Service Channel - Your Inbox Here you can monitor the status of your open messages.

10

1INSTALLATION OVERVIEW

TOPICS COVERED IN THIS CHAPTER

How to Use This Guide

Installation Pre-requisites

Hardware Requirements

Software Requirements

Configuration Requirements

11


How to Use This Guide

This guide is designed to simplify the Virsa Access Enforcer installation process. It identifies the steps you need to follow, specifies the order in which those steps must be performed, and guides you through the process. There are three phases to the process, each represented by a chapter in the guide:

• This chapter (“Installation Overview”) lays the groundwork for the installation. It provides an overview of the Virsa Access Enforcer implementation process, of which the installation itself is only a part.

• Chapter 2, “Virsa Access Enforcer Installation” guides you through the installation process. Once you have completed the procedure, you will have a running instance of Virsa Access Enforcer.

• Chapter 3, “Post-installation Configuration” lists the procedures you must perform after installation. These are one-time administrative tasks you must complete to make Virsa Access Enforcer ready for use.

• Appendix A, “Upgrading From a Previous Version of Virsa Access Enforcer” describes the procedures you must perform to update your Access Enforcer implementation. These procedures are specific to the upgrade process.

If you follow the process described in this guide, you will be able to install Virsa Access Enforcer simply and directly.

Installation Pre-requisites

Before you begin installing Virsa Access Enforcer, you need to ensure that your system meets the necessary requirements:

Hardware Requirements

Machine = Server basedDual Processors = 2.4–3.2 GHz or fasterRAM = 4 GBHard Disk = 40 GB Minimum (120 GB Recommended)

Note For upgrading from versions older than 5.1 VP1, see SAP Note 1004078.

Note For hard disk capacity, 40 GB is adequate. However, depending on how many users and requests you process, Virsa Access Enforcer can consume 40 GB of storage in approximately a year. Once the drive is full, you would need to either archive the data, or migrate to a larger drive. For this reason, you are recommended to install Virsa Access Enforcer on a drive of at 120 GB or larger.

12

Installation Pre-requisitesChapter 1 Installation Overview

Software Requirements

Operating Systems:

• Windows 2000 Server

• Windows 2000 Advanced Server

• Windows 2003 Server (Standard/Enterprise/Web)

• Linux Enterprise Server 4.0

• Unix

Java Runtime Environment = JRE version 1.4

Web/Application server = SAP Web Application Server 700 – SP8 or above, with Java/J2EE Stack

Configuration Requirements

In addition to the basic hardware and software requirements, Virsa Access Enforcer installation also requires certain configuration settings.

Memory Settings

To ensure that Virsa Access Enforcer installation does not encounter an out-of-memory condition, you need to set your memory parameters. You do this using the Config Tool installed along with NetWeaver. The command you use to launch the Config Tool depends on your operating system:

• If you are running the Unix or Linux operating systems, use:

/usr/sap/<SID>/DVEBMGS00/j2ee/configtool/configtool.sh

• If you are running the Windows operating system, use:

\usr\sap\JSA\JC00\j2ee\configtool\configtool.bat

1 In the Config Tool, navigate to the server instance for which you wish to set the memory parameters, and select the server by its server number.

2 Under the General tab, add or change memory parameters as required. For additional details on memory settings, refer to SAP Note 723909.

13


14

2VIRSA ACCESS ENFORCER

INSTALLATION


Pre-installation Procedures

Virsa Access Enforcer Installation Procedures

Before You Begin!

Deploying the Virsa Access Enforcer Files

Restarting the NetWeaver J2EE Server

15


Pre-installation Procedures

The Virsa Access Enforcer™ application files are available on the SAP Service Marketplace at: service.sap.com.

To download the Virsa Access Enforcer files:

1 From the SAP Support Portal section, click the Software Download quick link.

2 From the SAP Installations & Upgrades page, in the navigation bar on the left, click Entry by Application Group.

3 From the Installations & Upgrades page, click the SAP Solutions for Governance, Risk, and Compliance link.

4 Under the SAP Solutions for Governance, Risk, and Compliance area, click the SAP GRC Access Control link, then the VIRSA ACCESS ENFORCER link.

5 Under the VIRSA ACCESS ENFORCER area, click the linkfor the particular system where you plan to install Virsa Access Enforcer.

6 Click the Installation link, then the Download tab, and follow the instructions under this tab to download the files.

To proceed with the Virsa Access Enforcer pre-installation:

1 Create a folder on your system with no spaces in the folder name. An example of a good folder name is AE_Install.

2 Go to the SAP Service Marketplace as described in the previous section and download the Virsa Access Enforcer files into your local folder. Depending on the speed of your network, it can take up to four hours to download the application files.

3 Extract the setup files that you have downloaded.

4 Verify whether your download was successful.

To verify a successful download, compare the list of files in your download directory (for example, AE_Install) to the list of files in the distribution list that accompanies the download. If all of the files listed in the distribution list are present, the download has been successful.

Important Do not create your folder on your desktop, or copy the Virsa Access Enforcer Installation Package onto your desktop. The installation process will not function properly if executed from your desktop.

16

Virsa Access Enforcer Installation ProceduresChapter 2 Virsa Access Enforcer Installation

Virsa Access Enforcer Installation Procedures

The installation procedures detailed in this chapter are all required, and are listed sequentially. You should perform them in the order they appear.

Virsa Access Enforcer installation procedures include:

• “Deploying the Virsa Access Enforcer Files” on page 17

• “Restarting the NetWeaver J2EE Server” on page 18

Before You Begin!

Virsa Access Enforcer has specific system requirements, and cannot run successfully unless these requirements are met. The section “Installation Pre-requisites” on page 12 in Chapter 1, “Installation Overview” lists all system pre-requisites. If you have not yet read this section, you should go back and read it now. Do not attempt to install Virsa Access Enforcer until you are certain that your target system meets these requirements.

Installation Checklist

Before you begin installing Virsa Access Enforcer, you need to ensure that:

Deploying the Virsa Access Enforcer Files

The first step in installing Virsa Access Enforcer is to deploy the Virsa Access Enforcer files. There are several files you need to deploy:

• AEDictionary.sda Contains the Virsa Access Enforcer Data Dictionary.

• AEUME.sda Contains the actions required by Virsa Access Enforcer.

• AEEAR.ear contains the Access Enforcer executables.

• AEWorkFlowWSEAR.ear contains the Access Enforcer Web services for Role Expert™ integration.

• AEEAR4WS.ear contains the Web services for Sun IDM integration.

Use the Software Deployment Manager to deploy each of these files.

Important You must have system administrator privileges to successfully install Virsa Access Enforcer.

___ The SAP NetWeaver J2EE Server 700 is installed and configured.

___ The SAP database exists.

___ The User Management Engine (UME) is installed and configured.

___ Memory settings for SAP 700 Web Application Server (WAS) are configured. For more information about memory settings, see “Memory Settings” on page 13 in Chapter 1, “Installation Overview.”

17


To deploy the Virsa Access Enforcer files:

1 Open the Software Deployment Manager (SDM) application.

The Software Deployment Manager GUI appears.

2 Connect SDM to the NetWeaver host.

If connected to the correct instance of NetWeaver, SDM will automatically target the deployment node.

3 Click the Deployment tab.

4 Click the button, and browse to the directory into which you extracted the Virsa Access Enforcer installation files.

5 In the Browse window, double-click AEDictionary.sda, and then in SDM click Next.

6 Complete the wizard to deploy the Virsa Access Enforcer data dictionary.

Follow steps 1 through 6 in “To deploy the Virsa Access Enforcer files:” on page 18 to deploy the following files in the order presented here:

AEUME.sda file

AEEAR.ear

AEWorkFlowWSEAR.ear

AEEAR4WS.ear

Restarting the NetWeaver J2EE Server

At this point, you need to restart the NetWeaver J2EE server.

To verify that your update has been successful, launch a Web browser, and enter the following URL in the address field:

18

Virsa Access Enforcer Installation ProceduresChapter 2 Virsa Access Enforcer Installation

http://<server>:<port>/AE/index.jsp

where

server = the name or IP address of the NetWeaver J2EE server on which Access Enforcerresides.

port = the port number on which Access Enforcer listens.

If your update has been successful, you see the Access Enforcer start page, as shown in Figure 1:

Figure 1 Access Enforcer Public Start Page

This completes the Virsa Access Enforcer installation. Next you need to perform the initial Virsa Access Enforcer configuration. Chapter 3, “Post-installation Configuration” describes the tasks you need to perform.

19


20

3POST-INSTALLATION

CONFIGURATION


Virsa Access Enforcer Post-installation Tasks

Importing the Virsa Access Enforcer Roles

Assigning the AE Admin Role to the Administrator

Importing Initial Virsa Access Enforcer Configuration Data

Connecting a Standalone J2EE System to the Remote SAP Server

21


Virsa Access Enforcer Post-installation Tasks

The configuration procedures detailed in this chapter are all required, and are listed sequentially. You should perform them in the order they appear.

Virsa Access Enforcer post-installation configuration includes:

• “Importing the Virsa Access Enforcer Roles” on page 22

• “Assigning the AE Admin Role to the Administrator” on page 24

• “Importing Initial Virsa Access Enforcer Configuration Data” on page 27

Importing the Virsa Access Enforcer Roles

Once you have completed the installation procedures described in Chapter 2 “Virsa Access Enforcer Installation” and restarted the NetWeaver J2EE server, Virsa Access Enforcer is installed and running. However, before you can use Virsa Access Enforcer, you must import user roles and create an initial user account. The first step is to import the Virsa Access Enforcer user roles. You use the User Management Engine (UME) to do this.

To import Virsa Access Enforcer user roles:

1 Start the UME.

Use a Web browser to connect to and log into the NetWeaver J2EE server, and on the Index page, click User Management. Log into the UME.

22

Virsa Access Enforcer Post-installation TasksChapter 3 Post-installation Configuration

2 Click Batch Import.

3 Go to the directory into which you extracted the Virsa Access Enforcer installation files, and using any text editor, open the file ae_ume_roles.txt. Select and copy the entire contents of the file.

23


4 Go back to the UME, and in then in the blank area, paste the contents of ae_ume_roles.txt.

5 Click Upload.

Assigning the AE Admin Role to the Administrator

Once you have imported the Virsa Access Enforcer user roles, you need to define the initial Virsa Access Enforcer administrator. You will use this administrator role to perform certain tasks, to create other administrators and users, and to assign roles to them.

The Virsa Access Enforcer administrator has permission to perform any task in Virsa Access Enforcer. At some point in the future, you might decide to create other users with the same permissions, and perhaps to delete this initial administrator.

24


To assign the AE Admin role to a user:

1 Start the UME.

Use a Web browser to connect to and log in to the NetWeaver J2EE server, and on the Index page, click User Management. Log into the UME.

2 In the Get drop-down list, select Role.

25


3 Enter “AE*” and click Go to display the Roles list. In the Roles list, find and select the AE Admin role, click the Assigned Users tab, and then click Modify to assign that role to your specified user.

4 In the Available Users pane, type the user name in the Get field and click Go. Select the user to whom you will assign AE Admin privileges.

26


Importing Initial Virsa Access Enforcer Configuration Data

The final post-installation task is to import Virsa Access Enforcer’s initial configuration data. You do this from within Virsa Access Enforcer itself.

To import initial Virsa Access Enforcer configuration data:

1 Using a Web browser, connect to the NetWeaver J2EE server.

2 Type the application URL in your internet browser.

http://<hostname>:<portnumber>/AE

where

hostname = The name or IP address of the system on which NetWeaver runs.

portnumber = The port on which Virsa Access Enforcer has been configured to listen. The default is 50000.

For example, if the Access Enforcer server resides on host “mighty,” and it has the default port number, the correct URL would be:

http://mighty:50000/AE

You see the initial Access Enforcer screen.

3 Click User Login to display the Login screen.

Use the username and password of the AEAdmin user you just created.

4 Click the Configuration tab.

27


5 In the navigation pane, click Initial System Data.

6 In the content pane, click Browse, and navigate to the directory into which you extracted the Virsa Access Enforcer installation files.

7 In the Browse window, double-click the appropriate .xml file, and then in the Virsa Access Enforcer content pane, click Import.

The files you import are:

AE_init_append_data.xml - select the Append option.

AE_init_clean_and_insert_data.xml - select the Clean and Insert option.

Connecting a Standalone J2EE System to the Remote SAP Server

If you are performing a “standalone” J2EE system installation, you need to connect it to the back-end SAP server.

Use the following procedures to connect your J2EE system to a remote SAP server.

28


To add the required entry to your services file:

1 Open the Windows services file in a text editor, such as WordPad. Use the following path and file name:

c:\WINDOWS\system32\drivers\etc\services

The services file opens.

Note The following steps are for Windows installations. For UNIX installations, open your etc/services file with a text editor, and add an entry as described in Step 2 on page 30, for your particular environment. Add also the following entry:

sapgw00 3200/tcp

(You do not need to restart your UNIX system after performing this procedure.)

29


2 Add an entry in the services file in the following format:

sapms<sap_sid> 36<instance>/tcp

where:

sapms identifies the SAP message service

sap_sid is the name of your SAP server (always uppercase)

36 is the standard message port for SAP

instance is the SAP server instance number

tcp is the message protocol

For example:

sapmsSNW 3600/tcp

3 Add also the following entry:

sapgw00 3300/tcp

4 Save your changes and close the services file.

5 Restart Windows.

For more information regarding the services file, see SAP Notes 723562 and 52959.

This completes the Virsa Access Enforcer post-installation configuration. Virsa Access Enforcer is now running and ready for use.

The next step in the process is to configure Virsa Access Enforcer to support your provisioning processes, and to create workflows. These tasks are described in the Configuration Guide for Virsa Access Enforcer Version 5.2.

Note Do not forget to terminate each line (and also the last one) with [CR] (carriage return) when editing the services file.

30

AUPGRADING FROM A

PREVIOUS VERSION OFVIRSA ACCESS ENFORCER

TOPICS COVERED IN THIS APPENDIX

Upgrade Overview

The Upgrade Process

Upgrading Access Enforcer

Pre-upgrade Procedures

Configuring Memory Settings

Upgrading the Deployed Access Enforcer Files

Importing Virsa Access Enforcer Roles

Upgrading Virsa Access Enforcer Data

Importing Initial Access Enforcer Configuration Data

31


Upgrade Overview

This appendix describes the steps you follow to upgrade from an earlier version of Virsa Access Enforcer. Be sure to follow all of the instructions included in this appendix.

The Upgrade Process

The process for upgrading Virsa Access Enforcer is similar to the initial installation. There are some additional steps in the upgrade that do not appear in the installation, and certain steps you perform during an installation are not required when upgrading.

The upgrade process includes the following tasks:

• “Pre-upgrade Procedures ” on page 33

• “Configuring Memory Settings” on page 35

• “Upgrading the Deployed Access Enforcer Files” on page 35

• “Importing Virsa Access Enforcer Roles” on page 36

• “Upgrading Virsa Access Enforcer Data” on page 36

• “Importing Initial Access Enforcer Configuration Data ” on page 37

Important For upgrading from other versions older than 5.1 VP1, see SAP Note 1004078.

Important Wherever appropriate, this appendix refers to procedures described in the installation portion of the guide. The information contained in this appendix refers primarily to how the upgrade process differs from the installation process.

32

Upgrading Access Enforcer Appendix A Upgrading From a Previous Version of Virsa Access Enforcer

Upgrading Access Enforcer

To upgrade to Virsa Access Enforcer version 5.2, perform each of the following tasks, in the order in which they appear.

Pre-upgrade Procedures

Before you can upgrade your Access Enforcer implementation, you must perform the following pre-upgrade procedures:

• Run a background job to process HR Triggers in your current version of Access Enforcer.

• Back up your existing Access Enforcer implementation.

To process HR Triggers in Access Enforcer:

1 Log in to your current version of Access Enforcer.

2 From the navigation menu of the Configuration tab, click Background Jobs. The Schedule Service page appears.

3 From the Task Name drop-down list, select HR Triggers Load Data. If the background job is currently active, the Deactivate button appears at the bottom of the page. Click Deactivate to stop the background job.

33


4 From the Task Name drop-down list, select HR Triggers. If the background job is currently active, the Deactivate button appears at the bottom of the page. Click Deactivate to stop the background job.

5 Ensure HR Triggers still appears as the Task Name and then from the Schedule Type drop-down list, select Immediate.

6 Click Run.

To view all the processed HR Triggers, from the navigation menu of the Configuration tab, click HR Triggers > Process Log.

To prepare for an Access Enforcer upgrade:

1 Backup your existing Access Enforcer implementation to a safe place.

This includes:

Backing up your Access Enforcer database (all database tables with the prefix “VIRSA_” or “VT_AE_”).

Backing up the installation files you used when you originally installed your current version of Access Enforcer.

34


You should err on the side of caution here. You need to be able to restore your existing Access Enforcer implementation in the event that the upgrade process unexpectedly fails.

2 Perform all of the steps listed in the section “Pre-installation Procedures” on page 16 in Chapter 2, “Virsa Access Enforcer Installation.”

Verify that you have downloaded all of the files listed in the distribution list.

Configuring Memory Settings

This task is the same for installation and upgrade. Perform the configuration described in the section “Memory Settings” on page 13 in Chapter 1, “Installation Overview.”

Upgrading the Deployed Access Enforcer Files

To upgrade the deployed Access Enforcer files:

1 Use the Software Deployment Manager (SDM) to un-deploy the following files:

AEUME.sda

AEEAR4WS.ear

AEWorkFlowWSEAR.ear

AEEAR.ear

2 Use the SDM to re-deploy the following files in the order presented here:

AEDictionary.sda

AEUME.sda

AEEAR.ear

AEWorkFlowWSEAR.ear

AEEAR4WS.ear

3 Restart your NetWeaver J2EE engine.

To verify that your update has been successful, launch a Web browser, and enter the following URL in the address field:

http://<server>:<port>/AE/index.jsp

where

server = the name or IP address of the NetWeaver J2EE server on which Access Enforcer resides.

port = the port number on which Access Enforcer listens.

35


If your update has been successful, you see the Access Enforcer start page, as shown in Figure 2:

Figure 2 Access Enforcer Public Start Page

Importing Virsa Access Enforcer Roles

Before proceding to Upgrading Virsa Access Enforcer Data, you must import Virsa Access Enforcer Roles. Follow the procedures in the section “Importing the Virsa Access Enforcer Roles” on page 22. Make sure you select the Overwrite Existing Data checkbox in Step 4 on page 24.

Upgrading Virsa Access Enforcer Data

To Upgrade initial Virsa Access Enforcer data:

1 Log in to Virsa Access Enforcer.

2 From the navigation menu of the Configuration tab, select Upgrade.

The Upgrade page appears.

36


Figure 3 Upgrade Page

3 Click Upgrade.

Importing Initial Access Enforcer Configuration Data

To import the initial Virsa Access Enforcer configuration data, follow the procedure described in the section “Importing Initial Virsa Access Enforcer Configuration Data” on page 27 in Chapter 3, “Post-installation Configuration.”

When you have completed these tasks, you have successfully upgraded your Access Enforcer implementation.

37


38

ae virsa installation guide

Documents