Adobe Document Services Configuration Document

1.                 Introduction.

This document covers the phases which were performed during the course of the ADS implementation at the CRM Box. The system is a Dual Stack (AS ABAP+ AS JAVA) installed on the same machine with SP12 level. The goal is to setup the basic authentication model for the ADS services.

Please note that the document only covers the overview of the configuration phase and one should always follow to the updated document at the SDN network.

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/30a9630b-4f89-2a10-6fab-e311b3ffd9a6

 The basic steps performed to setup the ADS at the CRM box were-

Steps needed to be Performed at Web AS JAVA

At AS- ABAP side we need to install ADS services. We need to configure users/groups and Destination.

***For interactive forms scenario we need to configure web service client service at the Web AS JAVA side.

Steps needed to be performed at Web AS ABAP

We need to configure RFC Destination, User/role and ICF service at the AS ABAP

2.                 Phase-1.

This phase covers the reset of the system users which were required to configure and validate the ADS services on the CRM system.

Initially during the configuration and testing phase the password for the following users were required

1.     Crmadm

2.     SDM User

3.     J2ee_admin

1. Have reset the password system account “crmadm” user to “***” to gain the access for go.bat directory to start the JSPM tool.

2. Have reset the password of SDM user to “***” to check/apply java support level/stacks.

Reset password of SDM user to access JSPM and verify the Support level for the ADS.

Steps to change the SDM password

SDM is default in Integrated Mode, first you have to take it to Standalone Mode and after changing password take it back to Integrated Mode

Stop the server from the SAP Management console

Navigate to the SDM\program directory in MS-DOS window

start the standalone SDM

sdm jstartup "sdmhome=C:\usr\sap\J2E\JC00\SDM\program" "mode=standalone"

change the password

sdm changepassword "sdmhome=C:\usr\sap\J2E\JC00\SDM\program" "newpassword=*****"

Take SDM to Integrated Mode: sdm jstartup "mode=integrated"

3. Activate the emergency user through the config tool.

 Start the config tool ( Path: C:\usr\sap\CRM\DVEBMGS10\j2ee\configtool )

 Set the following UME properties:

ume.superadmin.activated                     True

ume.superadmin.password                    Password

Restart the AS Java

Login into the UML with sap* user and reset the password for j2ee_admin

** In the current CRM box being a dual stack box the j2ee_admin user resides in ABAP client and password should be reset from the client itself**

3.                  Phase-2.

This Phase covers the steps performed on the CRM system to setup the ADS services.

Steps performed sequentially to setup ADS (interactive forms scenario) at the CRM box.

1.     Start Configuration tool at AS JAVA side (C:\usr\sap\CRM\DVEBMGS10\j2ee\configtool\configtool.bat)

Add following parameter if not found at the cluster data à instance_dvebmgs10à server

-Dorg.omg.PortableInterceptor.ORBInitializerClass.com.sap.engine.services.ts.jts.ots.PortableInterceptorJTSInitializer

2.     Restart the AS Java.

3.     Login into the http://server:port/useradmin and check for the ABAP Source client ( change it to 800 )

4.     Check/create “ADSuser” user at the ABAP source client using su01.

5.     Specify/check the role ADScallers assigned to the user as per guide.

6.     Create ABAP connection using RFC destination using SM59. As per page number 18 of the guide.

7.     Enter the URL http://:/AdobeDocumentServices/Config .

To find the port number of j2ee engine use this formula to calculate the port number. (Port number =50000+100*instance number)

Choose test à rpdata(test..), give adsuser users credentials and choose submit. If the configuration for the Users (Step 4, 5) is correct the system displays the version number of the ADS in the response area.

8.      Test the Report FP_PDF_TEST_00 for displaying the version number of the ADS.

9.      Activate the ICF service in ABAP Side

 Log on to your SAP Web AS ABAP system
Choose transaction SICF.
Choose default host → sap → bc → fp in the tree.
Choose Service/Virt.Host → Activate

10.  Create /Check the destination service 

·         Start the visual administrator tool àservicesà Destinations

·         Under runtime select HTTP. Choose New and create in the navigation panel

·         Configure the HTTP destinations for ADS by choosing Services ® Systems ® Destinations in the Visual Administrator for the J2EE Engine.

·         Create an HTTP destination with the name FP_ICF_DATA.

·         In the dialog box that follows, enter the name FP_ICF_DATA_, where is your ABAP system, for the new destination and choose OK.

·         Under Connection Settings, enter the message server (or Web Dispatcher) of the SAP NetWeaver AS ABAP in the URL field:

·         http://:

·         To display the host name of your SAP NetWeaver AS ABAP log on to SAP NetWeaver AS ABAP and call transaction SICF. In the main menu, choose Goto → Port Information. The information is displayed on a screen; where the HTTP_port is specified under Services.

·         Select the option BASIC for authentication and enter the service user (including password) that has authorization for Adobe in the standard client of the back-end ERP system.

·         Choose Save.

11.  Now run the report FP_CHECK_DESTINATION_SERVICE
once run this report without checking the destination and after that run with checking the destination box. Both should return the same number of bytes as per note 944221

12.  Goto se38 : Program name, Now Execute report FP_PDF_TEST_00

If the program Execution shows a two page PDF document then ADS configure is done.

13.   Obtain the Reader Rights Credential

You need to setup the RRC for the Adobe Interactive forms scenario. To obtain your Reader Rights Credential, see SAP Note 736902. Furthermore, you can get a trial 6-month Reader Rights Credential from SDN network.

https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/business_packages/a1-8-4/adobe_credential_sneakpreview_nw04.zip

14.  Install and Configure  the Reader Rights Credential

 Copy the credential file (filename.pfx) to the /usr/sap//SYS/global/AdobeDocumentServices/TrustManagerService/trust/credentials directory

Configure the Credential Attributes:

• Logon to the Visual Admin
• On the Cluster tab, choose Server - > Services -> Document Services Configuration.
• On the Runtime tab, select Credentials.
• From the Type field, select the type of credential you are configuring (P12 record)
• In the Alias field, enter the alias ‘ReaderRights’
• Choose Browse to search for the name of the credential and then Select
• In the sha1 field, enter the sha1 value. This value is available in the text file which is found along with the certificate in the zip file.
• In the password field, enter the password you received along with the credential. In this case, you can enter your own password or the same value in the text file.
• Confirm the password and click Add.

15.  Restart the service PDF Manipulation Module for changes to take effect.

• Logon to Visual Admin
• On the Cluster tab, choose server -> Services -> PDF Manipulation Module
• Right click and stop the service.
• Once stopped, right click and start the service

4.                 Phase-3.

This Phase covers the Troubleshooting part done at the CRM system.

S.n.	ISSUES	RESOLUTION
1.	While accessing the Visual admin through normal user (having J2EE_ADMIN role) it is giving error, Apart from that the j2ee engine still crashed when accessed by "useradmin " through the UML portal.	Followed the Note  724452
2.	After activating the emergency user sap* I was not able to reset the password for j2ee_admin or create a new user in identity management. An error occurred in the persistence. The original message (possibly not translated) was: "Attribute "lockreason" on namespace "com.sap.security.core.usermanagement" of principal "UACC.R3_DATASOURCE.J2EE_ADMIN" is not modifiable.” Contact your system administrator. Current user has user creation permissions in the UME, but cannot create users in the back-end system (data source). The original and possibly untranslated message was: "No active writeable datasource found for user creation, check your Persistence Configuration."	The ABAP Source client was set to 001 at the Portal. Changed that to 800 Client.
3.	When trying to execute the report FP_TEST_00 i am the following error An exception occurred which is explained in detail below. The exception, which is assigned to class 'CX_FP_API_INTERNAL', was not caught and therefore caused a runtime error. The reason for the exception is: Error in include information for function module /1BCDWB/SM00000002	Follow SAP NOTE 1076159: Download the program FP_GENERATE_FUNCTION_MODULE Run this program with FP_TEST_00 in the input parameter of this report. The report, FP_TEST_00 generates a few function modules based on the entries in few custom tables which should be refreshed. Thus by applying this note we refresh the entries.
4.	While accessing the Document services configuration with the visual admin tool , i am getting the error " can not load the required classes for the document services configuration "	Checked Note  1017526 and restarted the cluster
5.	While running the report FP_TEST_00 it was giving error” cannot find PDL type for output device LP01”	Installed a new printer device ( PDL Supported) and set it default for other users.
6.	While trying to execute the interactive form  http://server:8010/sap/bc/webdynpro/sap/zneri_zadobe and after putting the credentials it is giving following error . The following error text was processed in the system CRM : WebDynpro Exception: ADS: Request start time The error occurred on the application server 187799-ap_CRM_10 and in the work process 0 . The termination type was: RABAX_STATE The ABAP call stack was: Method: RAISE of program CX_WD_GENERAL=================CP	Re-installed the Readers Rights credentials configuration and restart the PDM service.