How to Configuration ADS in Netweaver 7.5

As ADS are running on an AS Java  Stack and form processing is performed in an ABAP Stack environment, we have to configure the communication between the Form Processing Framework running on AS ABAP and the ADS running on Java.

Note: More details refer SAP Note 925741

AS ABAP side  configuration:

Log on to the ABAP system, call transaction SM59, and select ‘ADS’ from ‘HTTP connection to ext. server’.

Specify the server name and HTTP port number of the additional stand-alone AS Java.

You also need to update the corresponding user and password information on the ‘Logon/Security’ tab.

Make sure that create the user ADS_AGENT with the

corresponding role SAP_BC_FP_ICF and SAP_BC_FPADS_ICF exist in AS ABAP. If this

user does not exist, create it according to the steps in ADS Configuration

Guide.

Note:

When you do connection test for ADS destination RFC in SM59 the result can be “HTTP

response: (405) Method not allowed”. Error is normal.

Execute Tcode  SICF.

Choose default_host →  sap  → bc →  fp in the tree.

Choose Service/Virt.Host  →  Activate.

If AS ABAP and AS Java (with ADS) are installed in different systems, and you want to bundle your forms to

     improve performance, you also have to activate the fpads ICFservice.

AS Java configuration:       

Log on to the NetWeaver Administrator of your additional standalone AS Java.

Select Server ; Service destination HTTP.

Create an entry ‘FP_ICF_DATA_XX’,   where is the ABAP backend System ID.

Enter the ABAP HTTP port (http://:) in the ‘URL’ field.

Enter the user ‘ADS_AGENT’ in the Username field, and the corresponding password of ABAP backend system.

Save your entries.

Note: When

you do ping test for the destination the result can be “Error 404: Not found”.

This is normal.

As Java configuration for WebDynpro Application:

1.    Log on to the NetWeaver Administrator of your additional standalone AS Java.

2.    Select SOA Management  and  Technical Configuration Destination Template

3.    Management

4.    Select’Create Destination’ and Enter following entry:

5.    Destination Type: WSIL

6.    Destination Name: ConfigPort_Document

7.    URL:http://:/inspection.wsil

8.    SecurityTab

9.    Select Authentication ‘HTTP Authentication’ and ‘User ID/Password (Basic)’

10.  Select ‘Details’ and enter the user ADSUser and the corresponding password.

11.  Select ‘Save'

Testing ADS Configuration:

·       Checking ADS Configuration in an ABAP Environment

1.  Log on to the AS ABAP system.

2.  Start the transaction SA38.

3.  Enter the program name FP_TEST_00.

4.  Choose Program and Execute it.

.

5.  Make sure, that the following default values are entered in the respective fields:

o  Form: FP_TEST_00

o  ADS Connection:

          ADS or the RFC Destination name specified in your system

6.  Choose Program and Execute it

.

7.  Enter the Output Device.

8.  Choose Print Preview.

9.  If the system displays a form containing several lines on two pages, the ADS configuration is       correct. Otherwise, perform the tests described below.

·       Checking the ABAP Connection to ADS

1. Log on to your SAP system.
2. Start the transaction SA38.
3. Enter the name of the test report FP_PDF_TEST_00.
4. Enter the name of the connection. Enter the default name ADS, or, if you have specified another name, the one you are using in your system.
5. Choose Execute (F8).
6. If the configuration is correct, the system displays the version number of the Adobe Document Services.

        ·       Checking the Destination Service and the ICF Service

1. Log on to your SAP NetWeaver AS ABAP system.
2. Call transaction SA38.
3. Enter the name of the test report
4. FP_CHECK_DESTINATION_SERVICE.
5. Execute the test without choosing the option With
6. Destination Service.
7. The system renders a test form in the background
8. without using the destination service and displays the size of the created PDF.
9. Execute the test again. Now select the option With
10. Destination Service.
11. If the settings of the destination service are
12. correct, the system displays the same message as before (see step 5).