Record of Release

Name Designation Version No. Release Date Modifications Done

Created By Sameer G C Sr Manager –IT 01 04.12.2015

Reviewed By Kalpesh Shah Head – IT

Authorized By

1.0 Introduction & Scope

AS JAVA Engine delivered from SAP is utilized for and forms the base of many of SAP s/w components like EP, PI, XI etc. SAP Java Engine is being implemented in FDC Limited for Adobe Interactive forms development, by using Adobe lifecycle designer to create portable forms etc.

2.0 O.S. Preparation

2.1. When installing on Windows 2012 R2, install the .Net framework 3.5 from Add/Remove roles.

2.2 Install all the Windows updates from Control Panel -> Windows updates (DO not install Security Patches). After installation disable the “Windows Update services”.

2.3 Set the paging file to approx 20 GB by creating separate partition for PRD instance. Keep separate partition for SAP Kernel.

2.4 Install latest JDK version. Current setup has “jdk-8-windows-x64”

2.5 Restart the O.S. wherever required

3.0 Database Installation

3.1 Dump all the CDs for MS SQL 2012 into folder (51047515) and uncar the files

3.2 Goto path <Drive>RDBMS_MSSQL\MS_SQL_2012\51047515 in the command prompt. Open the command prompt with option “run as administrator”

3.3 Run the script SQL4SAP and follow the inputs required by the installation.

3.4 Apply SP 2 downloaded from the Microsoft website “SQLServer2012SP2-KB2958429-x64-ENU”

4.0 SAP Installation (Distributed System):-

4.1 Download the latest SWPM (SWPM10SP07_7-20009707.SAR) and uncar in a folder. Name the folder as for SWPM and double click the exe ‘sapinst.exe’. Follow the snapshots below.

Click OK. System automatically logs off . Log back in and the installation starts on its own.

4.2 Database Instance Installation

This JAVA CD is mismatch for the Installation. Download CD 51042609

4.3 Primary Application Server Instance

5.0 Adobe Document Services Configuration :-

5.1 Access Java Server

Access the JAVA engine management console by link http://fdcerpjava.fdc.com:50000/startPage OR http://fdcerpjava.fdc.com:50000 to open as below (50$$0) $$ - Instance no or can be checked in SAP MMC Console. PAS Instance no given during the Installation.

Click on ‘System Information’ and the components available in JAVA system. Click on ‘User management’ and login by ‘Administrator’ and password supplied during installation.

5.2 Configuration Link and Prerequisites

The link will be used for configuration of ADS

1.http://scn.sap.com/people/sunny.pahuja2/blog/2012/01/04/ads-configuration-in-netweaver-73

2.https://help.sap.com/saphelp_nwpi711/helpdata/en/8d/1cbf69fff9454ca9c5de84182e4bfb/content.htm?frameset=/en/37/504b8cbc2848a494facfdc09a359b1/frameset.htm&current_toc=/en/a2/9d30609db44064b0046c9fe9443d21/plain.htm&node_id=3&show_children=false

Prerequisites-

1) SAP Netweaver 7.3 As Java System (ADS should be installed).

2) SAP Business Suite 7 System

3) Add both the host entries in the systems (AS Java and AS Abap)

5.3 Setting up Profile parameters and Licensing

Setup below parameters through RZ10 in your ABAP System

 Profile Parameter SAPFQDN should be set in both As Java and As ABAP system. In Java system, SAPFQDN can be checked in the Default.pfl

JAVA system needs to be licensed permanently. Login to the AS JAVA system by clicking on ‘SAP Netweaver Administrator’. Click on ‘My workspace’ -> ‘Recently Used’. Click on license to apply for License by the below Information on OSS and once the License file is received apply as below.

Use the License option for apply License key to the AS JAVA System

5.4 Configuration for ADS

Login into AS JAVA by clicking on ‘User Management’

a) Create ADSUSER as a Technical User in Identity management if it does not exist.

b) Create ADSCALLERS group in Identity Management.

c) Assign UME Role SAP_ADSCALLER (You need to assign this role only to users who need to access ADS). In my case, I assigned this role to the ADSCALLERS group in identity management.

d) Assign ADSCALLERS group to ADSUSER in identitiy management.

5.5 Destination Template Management

Go to SAP netweaver administrator (http://<server>:<port>/nwa).

Then Go to SOA. Under SOA, go to Technical Configuration --> Destination Template Management

Choose Create New Destination

Choose Destination Type as WSIL and enter Destination name as ConfigPort_Document

Enter URL http://<server>:<port>/inspection.wsil

Enter System name: <SID of As Java> and hostname: <hostname of As Java>

On next screen, Choose Authentication as HTTP Authentication and Select User ID/Password (Basic). Enter ADSUSER and password as shown below:

Then click on finish. Now, destination ConfigPort_Document will be created.

Note: If you are configuring Interactive Adobe Forms then first request SAP to provide Adobe Interactive form credentials and *.pfx file which you need to configure Reader Right credentials. In order to obtain Reader Right credentials then please follow SAP note 736902.

4) In order to install Reader Right credentials, go to nwa (http://<server>:<port>/nwa).

Go to Configuration --> Infrastructure --> Adobe Document Services

Choose Document Security and then select Credentials.

Click on Manage P12 Files. A Pop-up will be open where you need to provide path of *.pfx file that you got from SAP.

Choose Upload. Now, your *.pfx file will be uploaded. Click on Add New Object and a pop-up will be opened. In Alias, Select Reader Rights Type should be P12. P12 File should be automatically filled as we have already uploaded the file in previous step. Enter Password for P12 file.

Save this record.

5) Restart the service Document Service Trust Manager Service and then the service PDF Manipulation Module for the changes to take effect. In order to restart the service, go to Operations --> Systems --> Start & Stop. Open Java Services Tab. In order to obtain list of services for ADS, filter the Service component Name column by Adobe. Restart the service.

6) Create Destination FP_ICF_DATA_<SID of As ABAP> in SOA.

Go to nwa (http://<server>:<port>/nwa)

Go to SOA --> Technical Configuration .Select Destinations.  Click on Create.

Enter Destination Name as FP_ICF_DATA_<SID of As ABAP>. Select Destination Type as HTTP. Click Next.

Enter URL of As ABAP system (http://<server>:<port>) e.g. http://abc.com:8000

Enter System ID and Client of As ABAP system. On Next screen, Select Authentication as Basic.

Enter User as ads_agent and its password.

Click on Finish.

By this way, configuration of ADS on As Java side is complete.

 5.6 Configuration is AS ABAP

Login to As ABAP system.

1) Create user ADSUSER as a system User in transaction SU01.

2) Create user ADS_AGENT as a system user in transaction SU01 and assign roles SAP_BC_FP_ICF, SAP_BC_FPADS_ICF & SAP_BC_JSF_COMMUNICATION.  

Note: Either assign standard roles or make a copy of this role to Z roles. If you are assigning Standard roles then make sure that profile of these roles should be generated.

3) Create role ADSCALLERS in PFCG and assign user ADSUSER to it.

4) Go to t-code SM59 and create ADS RFC as Type G.

a) In Target System settings, enter target host name and Service no. of your As Java systems.

b) In Path Prefix, enter- /AdobeDocumentServices/Config?style=rpc

c) In Logon & Security tab, select Basic Authentication. Then, enter user adsuser and its password. Save the RFC.

5) Go to SICF and activate below services

/default_host/sap/bc/fp

/default_host/sap/bc/fpads  

By this way configuration of ADS is completed.  

5.6 Troubleshooting  

944221- Troubleshooting if problems occur in forms processing

915399- com.adobe.ProcessingError File not found on URL Location

 Link to help.sap.com for ADS Configuration-

6.0 Configuration Check

Step 1 :- Checking PDF Output

The first check you need to perform is checking by Executing Test Report FP_TEST_00 in SE38. Keep the input parameters as they are. Select printer whose Device type in SPAD should be ‘PDF1’. If the configuration is correct system displays o/p as below.

Step 2 :- Checking Adobe Version

Execute test report FP_PDF_TEST_00 in se38 and select RFC connection as ADS created in SM59. Test result should show Adobe version as below

Step 3 :- Checking User and Password

a. Enter the following URL in your Web browser: http://<server>:<port> where <server> is the name of the AS Java

where the Adobe document services are installed, and <port> is the port of the AS Java.

  b. Choose Web Services Navigator

  c. In the Provider system , choose com.adobe/AdobeDocumentServces_com.adobe_AdobeDocumentServicesVi.

  d. Choose rpData.

  e. Choose Execute without entering any parameters.

  f. Enter the user name ADSUser and the password and press OK.

g. If the configuration is correct, the system displays the version number of the Adobe document services in the

result area as below. This version number should match with previous ADS version number.

Step 4:- Checking the Destination Service and ICF Service.

  a. Log on to your SAP NetWeaver AS ABAP system and call transaction SA38.

  b.  Enter the name of the test report FP_CHECK_DESTINATION_SERVICE

  c. Execute the test without choosing the option With Destination Service.

  d. The system renders a test form without using the destination service and displays the size of the

created PDF.

  e. Execute the test again. Now select the option With Destination Service.

  f. If the settings of the destination service are correct, the system displays the same message as before.

  g. In your Web browser enter the URL http://<server>:<port>/sap/bc/fp/form/layout/fp_test_00.xdp

Where <server> is the server that hosts the AS ABAP and <port> is the http port of the AS ABAP.

  h. In the dialog box enter ADS_AGENT as user and the password you have specified for it.

i. If the settings of the ICF service are correct, the system displays the layout information of the form

FP_TEST_00 in XML format.