AVM -RTA Design Studio Operations Guide v2

AVM-RTA Design Studio Operations Guide v2.0SP07


Greenlight Technologies, Inc. Page 2 of 28

COPYRIGHT INFORMATION

COPYRIGHT NOTICES

2004-2018 Greenlight Technologies, Inc. All Rights Reserved. The information in this document is provided for informational purposes only, is subject to change without notice, and should not be construed as a commitment by Greenlight Technologies, Inc. Greenlight Technologies, Inc. assumes no responsibility or liability for any errors or inaccuracies that may appear in this book. Except as permitted by license, no part of this document may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means – electronic, mechanical, recording, or otherwise – without the prior written permission of Greenlight Technologies, Inc. Printed in the U.S.A. CAUTION This document contains proprietary, confidential information that is the exclusive property of Greenlight Technologies, Inc. If you do not have a valid contract with Greenlight Technologies for the use of this document, or have not signed a non-disclosure agreement with Greenlight Technologies, then you received this document in an unauthorized manner and are not legally entitled to possess or read it. Use, duplication, and disclosure are subject to restrictions stated in your contract with Greenlight Technologies, Inc. Use, duplication, and disclosure by the Government are subject to restrictions for commercial software and shall be deemed to be Restricted Rights software under Federal Law.



DOCUMENT REVISION HISTORY

Sr. No Date Version Comments

1 04/15/2013 2.0SP03 Updated for v2.0SP03 release.






TABLE OF CONTENTS

1 ABOUT THIS GUIDE ................................................................................................................. 5

1.1 DOCUMENT PURPOSE ........................................................................................................ 5

1.2 DOCUMENT CONVENTIONS ............................................................................................ 5

1.3 RELATED DOCUMENTS ..................................................................................................... 5

1.4 TARGET AUDIENCE ............................................................................................................. 5

2 TECHNICAL LANDSCAPE ....................................................................................................... 6

2.1 ARCHITECTURE .................................................................................................................... 6 2.1.1 AVM RTA DS DEPLOYMENT ON SAP NW AS 7.31+ ............................................ 6

3 MONITORING APPLICATION ............................................................................................... 7

3.1 LOGGING IN AVM RTA DS ............................................................................................... 7

3.2 SWITCH OFF THE LOG FILES........................................................................................... 11

3.3 CHANGING LOG LEVEL ................................................................................................... 12

3.4 ENABLE/DISABLE LOGS ................................................................................................... 13

4 MANAGING THE APPLICATION ........................................................................................ 15

4.1 START/STOP/RESTART AVM RTA DS APPLICATION ............................................... 15

4.2 CREATING USER ................................................................................................................ 17

4.3 BACKUP AND RESTORE ................................................................................................... 20

5 SOFTWARE CHANGE MANAGEMENT .............................................................................. 22

5.1 TRANSPORT AND CHANGE MANAGEMENT ............................................................. 22

5.2 DEVELOPMENT REQUESTS AND DEVELOPMENT RELEASE MANAGEMENT .. 22

5.3 QUALITY MANAGEMENT AND TEST MANAGEMENT ............................................ 22

5.4 SUPPORT PACKAGES AND PATCH IMPLEMENTATION ......................................... 22

6 HIGH AVAILABILITY ............................................................................................................. 23

7 TROUBLESHOOTING ............................................................................................................. 24

8 SUPPORT ................................................................................................................................... 27

9 TERMS AND DEFINITIONS .................................................................................................. 28



1 ABOUT THIS GUIDE

Greenlight’s AVM RTA Design Studio (RTA DS) is a software application that extends the SAP GRC applications for Access Control (AC) and Process Control (PC) to non-SAP systems in the customer’s IT landscape. The application establishes connections to non-SAP ERP systems and provides data to Access risk Management. It has many valuable features including the ability to establish real time connections to target ERP systems, databases, legacy systems, as well as reading data from flat files.

1.1 DOCUMENT PURPOSE

This document provides information on managing, operating and running the AVM RTA DS application.

1.2 DOCUMENT CONVENTIONS

The document conventions are as follows:

1. Bold Book Antiqua is used to designate names of icons, buttons and menus.

2. Italic Book Antiqua text in blue is used to designate hyperlinks and cross-references.

1.3 RELATED DOCUMENTS

The list of related document is as follows:

1. AVM-RTA_DS_User_Guide.pdf – this document contains detail information about how to use the AVM RTA DS application.

2. AVM-RTA_DS_Installation_Configuration_Guide.pdf - this document provides details for the installation and configuration of the AVM RTA DS.

1.4 TARGET AUDIENCE

The target audience for this manual is system administrators, solution administrators and/or technical people, who are responsible for installing AVM RTA DS.



2 TECHNICAL LANDSCAPE

This chapter discusses about the technical architecture.

2.1 ARCHITECTURE

The following section illustrates how AVM RTA DS is deployed on SAP NWA.

2.1.1 AVM RTA DS DEPLOYMENT ON SAP NW AS 7.31+

AVM RTA DS can be deployed in the following two ways for GRC 10.x integration depending upon if GRC is deployed on a dual stack Netweaver system (ABAP + JAVA) or just ABAP system.

Even if the dual stack is available for the GRC box, RTA DS can be deployed on a separate Netweaver Java Stack.

AVM RTA DS utilizes the Net weaver Java Stack Database onto which it is deployed to create and populate its tables.

Figure 2.1: Landscape Architecture

Note: If AVM is installed on a clustered NW JAVA instance (multiple application servers / multiple JAVA server nodes) then please maintain either Message Server based application URL or URL based on any load balancer (if one has been deployed in customer landscape) to distribute requests from Access Control to AVM.



3 MONITORING APPLICATION

Logs are available and can be viewed either through the application or directly on the server as an operating system file.

AVM RTA DS maintains error and debug logs per physical server at following file system path:

/usr/sap/<SID>/../j2ee/cluster/RTADS_LOGS, where SID is the system identifier.

To see the logs from the AVM RTA DS application, please follow this path:

Configuration >Logs Monitor >Application Log >xapp.debug.log, xapp_info.log and xapp_error.log

Log files are used by administrators to view the status of the system, database, and applications. AVM RTA DS logging API uses the log4j to produce logs in a common format and the status of the log files can be displayed using a browser. The actual log files are invoked using a hyperlink to individual log file. Log files are automatically written and contain a predefined severity that cannot be modified in the current release.

Apart from the logs provided by AVM RTA DS, the NW AS Java log and defaultTrace.trc, the default log and trace file for the J2EE engine are also available. There are primarily three levels of severity it supports:

1. Debug

2. Info

3. Error

Each log file records the following events:

1. Source of the record

2. Event timestamp

3. Message

4. Severity Level

3.1 LOGGING IN AVM RTA DS

The logging levels in the AVM RTA DS have appender properties as

1. Debug_appender- shows messages classified as DEBUG, INFO, and

ERROR.

2. info_appender- shows messages classified as INFO and ERROR.

3. Error_appender- shows messages classified as ERROR.

4. Initially during product deployment, the tag <appender-ref> is not commented for any appender.



a. The <appender-ref> appears as follows in the log4j.xml file.level. The tag is set to the debug_appender as

<level value="debug_appender"/>.

b. After successful deployment, the logging level can be changed. If the applications have been deployed for some time, there might be some log files, which can be deleted, and the new logging level can be set; the application would require a restart after changing the logging levels. For Example, if you want to create only ERROR logs file and does not want to create INFO and DEBUG logs file, then in that case, you need to comment <append-ref> tag for info_appender and debug_appender. Add error_appender value to <level> tag as shown below.

<level value="error_appender"/>.



c. Similarly, if you want to create only INFO logs file and does not wish to create DEBUG, ERROR logs then you can comment as:

<append-ref> tag for error_appender and debug_appender and add info_appender value to <level> tag as shown below. <level value="info_appender"/>.

d. Similarly, if you want to create only DEBUG logs file and does not want to create INFO, ERROR logs then you need to comment, <append-ref> tag for error_appender and info_appender. Add debug_appender value to <level> tag as shown below.

<level value="debug_appender"/>.

5. Maximum size of generated file would be 5000KB. After that new log file would be generated.



6. To view the logs, login to the AVM- RTA DS application, click Configuration tab.

7. Click Application Logs under Logs Monitor in the left menu bar.

8. The Application Log > screen opens as shown in the screenshot below.

Figure 3.1: Application Log >View Screen

9. The Application Log>View table displays Name column with Node link and last modified date time.

10. Click on the Node link.

11. The Application Log > <Node link> >View screen opens as shown in the following screenshot displaying details under columns Name, Size and Last Modified Date Time.

Figure 3.2: Application Log > Node

12. Click on the Name link to view and download the log files.

13. Click on the breadcrumb link to visit application log page.

14. The Log files are used by administrators to view the status of the system, database, and applications. The AVM RTA DS logging API uses the log4j to produce logs in a common format and the status of the log files can be displayed using a browser. The actual log files are invoked using a hyperlink



to individual log file. Log files are automatically written and contain a predefined severity that cannot be modified in the current release.

15. For debugging purposes, apart from the logs provided by AVM RTA DS; the logs available from NW AS Java and the default log and trace file for the J2EE engine can also be referred.

16. There are primarily three levels of severity it supports:

1. Error

2. Info

3. Debug

17. Each log file records the following events:

1. Source of the record

2. Event timestamp

3. Message

4. Severity Level

3.2 SWITCH OFF THE LOG FILES

The steps to switch off the log files are as follows.

1. Go to <RTA DS HOME PATH>/servlet_jsp/xPlatformAdapter/root/WEB-INF/classes/config/xapp_log4j.xml

2. In the xapp_log4j.xml file, remove the appropriate line if you want to switch off particular log.

3. The examples of logs are:

a. <appender-ref ref="info_appender"/>

b. <appender-ref ref="debug_appender"/>

c. <appender-ref ref="error_appender"/>

4. For Example:

To remove debug log, remove< appender-ref ref="debug_appender"/>. ”

Note: Greenlight recommends retaining info logs and error logs.

The following table displays the list of important log objects.

Log Objects Descriptions

/usr/sap/<SID>/JC<instance nor.>/j2ee/cluster/server0/log

Default location of AS JAVA log file.

defaultTrace.trc The standard log & trace file for the J2EE engine.

/usr/sap/<SID>/JC<instance

no.>/j2ee/cluster/apps/sap.com/xPlatform/servlet_jsp/xPlat

Location of AVM RTA DS log files.



Log Objects Descriptions

formAdapter/root/logs

xapp_debug.log Contains additional information about the flow of execution and error details for troubleshooting/debug purposes.

xapp_info.log Contains the information about the flow of execution of the programs

xapp_error.log Contains the exceptions and various errors occurred if any during the flow of execution of the programs.

3.3 CHANGING LOG LEVEL

This section describes information about changing log level.

The steps to configure xapp_log4j file are as follows:

1. Configure “MaxFileSize” and “MaxBackupIndex” parameters in the xapp_log4j file.

2. Open the xapp_log4j.xml file, on all the server nodes (server0,server1…) located at:-

/usr/sap/<SID>/../j2ee/cluster/server(N)/apps/sap.com/xPlatform/servlet_jsp/xPlatformAdapter/root/WEB-INF/classes/config/xapp_log4j.xml

--where ‘server(N)’ refers to server nodes (server0,server1… and so on.)

Note: in the clustered environment, perform the steps (1 and 2) on all the nodes e.g. server0, server1 etc. Restart the application.

3. Modify following parameters in xapp_log4j.xml for all the appenders (info_appender, debug_appender, and error_appender):

<param name="MaxFileSize" value="5000KB"/>

4. The values specified indicate that the appender will back-up the log files when they reach a size of 5000 KB.



Figure 3.3: xapp_log4j file

Note: you can modify the values as per the requirement.

3.4 ENABLE/DISABLE LOGS

This section describes how to enable /disable log levels.

1. In order to disable any log level (debug, info, error), remove <appender-ref> tag residing under <root> tag as shown in the following screenshot.

<root> <appender-ref ref="debug_appender"/> <appender-ref ref="info_appender"/> <appender-ref ref="error_appender"/> </root>

2. To disable debug log, remove:

<appender-ref ref=" debug _appender"/>

3. To disable info log, remove:

<appender-ref ref=" info _appender"/>

4. To disable error log, remove:

<appender-ref ref="error_appender"/>



Figure 3.4: Appender Log Level



4 MANAGING THE APPLICATION

This chapter discuss about how to Start and Stop application deployed on the SAP NWA 7.02 and information on backup and restore.

4.1 START/STOP/RESTART AVM RTA DS APPLICATION

The steps to start/stop/restart the AVM RTA DS application are as follows.

1. Logon to the SAP NetWeaver with the administrator credentials.

The following screen opens.

Figure 4.1: SAP NetWeaver Administrator

2. Click on the Operations tab as shown in the following screenshot.

Figure 4.2: SAP NetWeaver Administrator- Operations tab

3. Click on Start & Stop link.

The Start& Stop: Java Instances screen opens as shown in the following screenshot.

Figure 4.3: Start& Stop: Java Instances

4. Click on the Java Applications tab.

The Start& Stop: Java Applications screen opens as shown in the following screenshot.



Figure 4.4: Start& Stop: Java Applications

5. In the Filter text box, enter the value as xPlat/Platform as shown in the following screenshot.

Figure 4.5: Start & Stop: Java Applications: filter

6. The screen displays details as per the entry in the filter as shown in the following screenshot.



Figure 4.6: Figure: Start & Stop: Java Applications

7. Click on the Start button to start the application

8. Click on the Stop button to stop the application.

9. Click on the Restart button to restart the application.

Note: In the figure 4.6, the Start button is disabled as the application is running.

4.2 CREATING USER

After deploying the AVM RTA DS application on SAP NW 7.31, it is necessary to create user to logon to the AVM RTA DS application.

The steps to create user are as follows.

1. Logon to the SAP User Management Administrator with appropriate credentials as shown in the following screenshot.



Figure 4.7: SAP NetWeaver

2. Click on Log On.


Figure 4.8: Create User

3. Click on the Identity Management> Create User tab.


4. In the Logon ID section, enter administrator credentials. For Example: rtadsadmin.

5. Choose the option as Define Initial Password.

6. In the Define Password text box, enter appropriate password.

7. In the Confirm Password text box, enter appropriate password.

8. Enter all the mandatory fields.

9. Click on the Assigned Roles tab.

The following screen appears.



Figure 4.9: Assigned Roles

10. On the Available Roles screen, Select criteria as "All Data Sources" and value as "DS_SYS*". Click on Go button. Select the imported role/roles for AVM RTA DS. For example: to create the Admin User, select the DS_SYS_ADMIN role and assign it to the created user. Select the role and click on Add button.


11. Role is added in Assigned Role Pane as shown below.


12. Click on Save.

13. The login Id is created.

The system prompts with the message, “User Created” as shown in the screenshot below.

Figure 4.12: User Created



14. The login id is created with the Define Initial Password option.

15. To activate the Login Id and password, login to the NWA (SAP NetWeaver

Administration) with newly created user Id and password.

16. The UME screen prompts to change the password.

17. Enter the Old and the New passwords in the respective text boxes.

18. After changing the password successfully, login to the AVM RTA DS application with the new credentials.

Figure 4.13: SAP NetWeaver

19. Open the web browser and access the following link to the AVM RTA DS:

http://NetWeaverServerIP:port_number/xPlatformAdapter/checkLogin.do

4.3 BACKUP AND RESTORE

The AVM RTA DS serves to connect the SAP Access Control (AC) product with a Target ERP system like Oracle Financials to extract data from the target ERP and feed that ERP data to AC for analysis. The ERP data does not persist in RTA DS therefore no storage or backup and restore function exists in RTA DS for the data. It is important that the client follow good procedures to make regular backup copies of the target ERP system such as Oracle financials using the appropriate ERP tools and methods for the specific system as well as backups of the SAP GRC products and data.

The companies have their own disaster recovery plan. One of the benefits of having a streamlined IT infrastructure is that it enables companies to recover faster in the event of failure or environmental disaster. It is important to ensure that backup devices are not lost with normal data storage (separation of storage locations).

The backup and restore strategy for system landscape should consider SAP systems. It should be embedded in overall business requirements and incorporate



the entire process flow of the company. Taking back up of the Java AS and the relevant database prevents the data loss. It is also essential for the recovery of the server after the system break down.

The backup data to restore the system is used in the following scenarios:

1. Restore the initial state of the system, if an installation or upgrade fails.

2. Restore an SAP NetWeaver AS installation when operating system or file system problems occur.

3. Restore SAP system data in case of the database crash.

The backup strategies to be applied are as follows:

1. Offline Backup - This strategy enables you to create a full backup of your system that can be restored from a hard disk crash or operating system problems. It requires system downtime and is not practical to do on a daily basis.

2. Online Backup - This strategy allows you to back up the database and the file system to recover particular components of your system. For this backup full system shutdown is not required, thus making this strategy convenient for creating regular incremental data backups. Online backup does not guarantee a full backup of all system components.

Note: you can use the standard SAP NetWeaver 7.31+ operations for backup and restore for the AVM RTA DS. The application has several tables in the file system and database to back up and restore. Use the parameter: SAP<SID>DB, where SID is the system ID. You need to back up all tables with the following prefixes: GLT.



5 SOFTWARE CHANGE MANAGEMENT

The Software Change Management section provides additional information about the most important software components.

5.1 TRANSPORT AND CHANGE MANAGEMENT

This section pertains to transport of changes from DEV AVM RTA DS instance to later instances of the application in landscape on QA and PRD. From AVM RTA DS perspective there isn’t any persistent configuration/data whose change is to be migrated up the stack. One has to directly setup system, connection in the relevant application versions Dev, QA and PRD. Only part that is available for import is initial Master data and Adapter xml files but these do not part of Transport and change management procedures. AVM RTA DS application has max one component .sca (comprising 3 files, individual .ears /.sda can’t be provided). Being a JAVA application means support pack in itself will be entire JAVA application which can be deployed via SDM/JSPM or SUM.

5.2 DEVELOPMENT REQUESTS AND DEVELOPMENT RELEASE MANAGEMENT

Any new development request and releases will be incorporated in future support packs or major releases depending on the criticality.

5.3 QUALITY MANAGEMENT AND TEST MANAGEMENT

Each support pack/releases will be going through complete QA cycle.

5.4 SUPPORT PACKAGES AND PATCH IMPLEMENTATION

The support package for AVM-RTA Design Studio is available in the SAP Service Marketplace.



6 HIGH AVAILABILITY

AVM-RTA Design Studio uses SAP NetWeaver for high availability.



7 TROUBLESHOOTING

The list of the troubleshooting scenarios with regards to Installation of AVM RTA DS with the solution is as follows:

1. Not able to login to AVM RTA DS application.

Solution:

To be able to login to the AVM RTA DS application,

a. First make sure the platform has been properly registered.

b. Go to Platform Registration on the applications Home Page and check whether the status is REGISTERED.

c. Second, make sure the User Id you are trying to enter into the system has the appropriate RTA roles to login through SAP UME.

d. Ensure the UME password is correct and if necessary have the Administrator reset the password.

2. Why I am not getting risks in CC/RAR?

Solution:

For this problem there could be any of the following possibilities:

a. Please make sure that System name in CC/RAR is same as External Id of the corresponding System in RTA.

b. Please check whether System in AVM-RTA Design Studio is registered.

c. Please make sure that system is mapped to your Adapter APIs.

3. Why the connector types are not showing when the master data is imported?

Solution:

a. Make sure that the installation scripts were run during the installation of the AVM RTA DS.

b. If not run then, run the delete scripts once on the Database schema where AVM RTA DS application is installed to delete the data that might have already been created.

c. Run the installation scripts and then try re – importing the Master data.

4. Not able to find pre-configured roles to be attached to AVM RTA DS application users.

Solution:

a. To be able to associate roles to the AVM RTA DS application user;

b. Make sure you have imported the pre-configured role file into Sap UME through NetWeaver administrator.



5. The RTA cannot connect to the target ERP database because the database crashed or was offline. How do I reconnect it?

Solution:

a. Ensure that all the services are restarted in SAP Management Console. If this does not help then the server needs to be restarted.

b. This will clear all the inconsistencies. Once the server is started bring up all the services in SAP Management Console.

6. Why Standard Adapter mapping is not available?

Solution:

a. Once you overwrite the Master data or Standard Adapter then all the previously done mappings for Standard adapters will be removed. So you need to go and do system-adapter mapping again.

7. Why Auto Job execution is failing?

Solution:

a. If a job is scheduled and it does not have any data then that job will fail. This is a known issue that is scheduled to be delivered in the next release.

b. Check whether system is mapped to the correct API.

8. Why Program is failing in Test Program?

Solution:

a. Please check connection for connector.

b. Please check whether the adapter program is correct.

c. While performing test program please provide values for all input parameters. If you perform test program without providing values, then the program will fail.

d. If it is a JDBC connector and if the database onto which the connector has been restarted then the AVM RTA DS application needs to be restarted to make a fresh connection to the database by the JDBC connector. Restart the AVM RTA DS application and try the test connection again.

9. Why am I not able to associate the already attached system to the API once I overwrite the Adapter?

Solution:

a. This is a known issue in the current release. Anytime you need to overwrite the already existing adapter; you need to import the Master xml with the overwrite check box checked.

b. First import the master data in overwrite mode.

c. Re import, the adapter and now you can attach the system to the API.



10. Why am I not able to see the updated log entries even though I made a change to a connector in AVM RTA DS?

Solution:

a. If you open a log file such as the Error Log, Debug Log or the Info Log in the application and do not see the current time stamped entries, your internet browser may not be displaying the latest data. Clear your temporary internet files and reopen the log file. This issue should now be fixed in the current software release.



8 SUPPORT

The AVM RTA DS application comes with the software and the installation and configuration documents. For any technical queries, please login to the SAP support system once the implementation is completed. If you do not have access to support system, please send an email to [email protected] and we will provide the required login credentials to raise messages. After submitting the request, it will be routed to the appropriate party at Greenlight and they will contact you. The support person may set up a WebEx session or similar process to diagnose and resolve the problem. For any other query/support related issues send us an email at [email protected].

For information on Greenlight, products visit www.greenlightcorp.com

mailto:[email protected]

mailto:[email protected]

http://www.greenlightcorp.com/



9 TERMS AND DEFINITIONS

Terms Definitions

Application The application is a homogeneous group of systems.

Application Registration The process of registering the applications created in AVM RTA DS with a valid key provided by Greenlight Technologies.

GRC Governance Risk and Compliance

Logs The RTA DS application maintains the all error and debug logs.

NW NetWeaver

NWA NetWeaver Administrator

RTA DS

Real Time Analysis Design Studio abbreviated as RTA DS is the Java based application that extends and leverages SAP GRC capabilities to non-SAP systems.

UME User Management Engine

Documents

AVM -RTA Design Studio Operations Guide v2