Hi all,
I hope this helps.
ADS Installation and Configuration
Introduction: Adobe Document Services (ADS) enable form-based processing of business data triggered by both ABAP- and Java-based applications. It is an additional SAP NetWeaver solution extension included in the SAP NetWeaver usage type AS Java
Installation checks:
  1. Check whether ADS is installed on PI Java Stack
http://<AS Java hostname>:<port>/monitoring/ComponentInfo

    2. If it is installed, Configure the communication between PI and ECC

If it’s not installed follow below steps to install it.
      • Download support package ADSSAP07_0-10009589.SCA (SP07for ADOBE DOCUMENT SERVICES 7.31) from SAP support portal.
      • Upload SCA file to AS Java server (any temp location).
      • Logon to AS Java server console via SSH with <sapsid>adm user.
      • Execute telnet localhost <telnet port> and login with administrator of AS Java user (Administrator or similar).
      • Execute lsc (refer to SAP Note 1715441)
      • Deploy SP07 for ADOBE DOCUMENT SERVICES 7.31
        (refer to
        http://wiki.scn.sap.com/wiki/display/TechTSG/(JSTSG)(Telnet)DeployController+Commands?original_fqdn=wiki.sdn.sap.com)
        with command:

        deploy /tmp/ADSSAP07_0-10009589.SCA on_deploy_error=stop
        Note: during deployment of ADSSAP component AS Java server instance is restarted.

  • Execute
  • telnet localhost <telnet port> and login with administrator of AS Java user to re-connect to Deploy ControllerTelnet.
  • Execute get_result to view results of deployment.
  • Open http://<AS Java hostname>:<port>/monitoring/ComponentInfo and verify that ADSSAP is listed under System information: Components Info.
  • /wp-content/uploads/2014/03/1_408879.jpg

Configuration: As ADS
are running on an AS Java (PI) and form processing is performed in an ABAP (ECC) environment, we have to configure the communication
between the Form Processing Framework running on AS ABAP and the ADS running on
AS Java.
Note: Refer to SAP Note 925741
AS ABAP configuration:

  1. Log on to the ABAP system, call transaction SM59,and select ‘ADS’ from ‘HTTP connection to ext. server’.
  2. Specify the server name and http port number of the additional stand-alone AS Java.
  3. You also need to update the corresponding user and password information on the ‘Logon/Security’ tab.

/wp-content/uploads/2014/03/2_408880.jpg
/wp-content/uploads/2014/03/3_408884.jpg

4. 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 in SM59 the result can be “HTTP
response: (405) Method not allowed”. This is normal.

5. Open transaction SICF.

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

7.Choose Service/Virt.Host  →  Activate

8. 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:       

  1. Log on to the NetWeaver Administrator of your additional standalone AS Java.
  2. Select Server -> Service -> destination -> HTTP.
  3. Create an entry ‘FP_ICF_DATA_<SID>’,   where <SID> is the ABAP backend System ID.
  4. Enter the ABAP HTTP port (http://<servername>:<port>) in the ‘URL’ field.
  5. Enter the user ‘ADS_AGENT’ in the User name field, and the corresponding password of ABAP backend system.
  6. Save your entries.
/wp-content/uploads/2014/03/4_408885.jpg

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 -> 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://<standalone AS Java server name>:<http port>/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
/wp-content/uploads/2014/03/5_408886.jpg


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 Execute (F8)
.

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

Form:FP_TEST_00

ADS Connection:
ADS or the RFC Destination name specified in your system (if it does not
correspond to the default entry)

6.  Choose Program Execute (F8)
.

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
            FP_CHECK_DESTINATION_SERVICE.
          4. Execute the test without choosing the option With
            Destination Service.
          5. The system renders a test form in the background
            without using the destination service and displays the size of the created PDF.
          6. Execute the test again. Now select the option With
            Destination Service.
          7. If the settings of the destination service are
            correct, the system displays the same message as before (see step 5).
 

Note: Please refer to SAP Note 944221 for Adobe Document Services troubleshooting.

To report this post you need to login first.

16 Comments

You must be Logged on to comment or reply to a post.

  1. Andy Silvey

    Hi,

     

    the process is nicely described, next time, for such an instruction please use a Document as the container and not a Blog.

     

    Question, what is the architectural reason for choosing to host a centralised ADS on PI, instead of an alternative Java stack like CE or Portal (or ADS’s own Java stack) ?

     

    Andy.

    (0) 
    1. Basis Lady Post author

      Hi Andy,

       

      Thank you very much for your Comment / Suggestion. I will better document it from next time.

       

      In general, There is no specific reason. You Can use other java stacks too. But in my Organisation we have Java Stack on PI, Solution Mnagaer.

       

      And instead building an additional ADS’s own Java stack we have used PI in our case.

      (0) 
      1. Andy Silvey

        Hi Basis Lady,

         

        then that is fair enough and that is the beauty of architecture, every customer situation is different and requires different architecture decisions.

         

        Best regards,

         

        Andy.

        (0) 
        1. Amerjit CHAHAL

          Hi Andy,

           

          As you say it’s horses for courses in terms of architecture. We went with a dedicated stack for ADS due to CPU+Mem consumption (big/complex Interactive forms can consume up to 1.2GB heap during rendering and burn one CPU) and to mitigate cross component patching requirement conflicts.

           

          Kindest Regards,

           

          Amerjit

          (0) 
      2. Matt Fraser

        Historically ADS used to be supported only on 32-bit architecture (a limitation of the Adobe component), even while everything else on the Java stack worked in 64-bit, so this was one reason why ADS might have been installed on a dedicated host. Fortunately, this is no longer the case and hasn’t been for some time, so this limitation is gone.

         

        Nevertheless, I still prefer to keep this separate, especially as it’s not a big deal to spin up a VMware instance to run it. This way, with no additional functions, there are no limitations on NetWeaver versions, and thus you can freely run ADS on the latest and greatest NW 7.4 stack without worrying about interoperability with the rest of your landscape.

         

        Like Amerjit, we’re also running custom interactive forms through ADS, although I wouldn’t call our usage very heavy. However, that’s one additional piece that could be written about for ADS configuration: the installation of the Adobe Reader Rights Credential for interactive forms. I don’t think I’ve seen that mentioned in any of the various ADS blogs or documents I’ve come across.

         

        Regards,

        Matt

        (0) 
  2. Dieter Lorenz

    Is there is any SSL Config available without Certificates ? In my case I have an problem with the service endpoint. Get an 404 error from the RFC HTTP Connection to the Java 7.4 System.

    (0) 
    1. Matt Fraser

      Hi Dieter,

       

      No, certificates are part-and-parcel of the SSL protocol. However, if this is just for testing or internal-only use for a small number of people, you don’t necessarily have to get the certificates signed. Just add them as trusted exceptions to the browsers of all your users.

       

      Cheers,

      Matt

      (0) 

Leave a Reply