Skip to Content
avatar image
Former Member

ADS Configuration in SAP Netweaver 7.3 AS java

We have a scenario where ADS is installed as a separate AS Java system and other ABAP systems connect to it to utilize ADS functionality. We recently have a requirement to use ADS on MII systems, which are basically AS Java systems.

We don't want to install ADS on MII and would like to utilize the existing ADS setup that we already have. I have already gone through the ADS configuration guide available at¤t_toc=/en/69/b830ac608446f38e9b53093cea3e14/plain.htm&node_id=30&show_children=false

I am not getting exactly, what steps do I need to perform at MII side to get it connected to our ADS system and utilize the ADS function. Can anyone please guide me here?


Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Dec 06, 2016 at 12:32 PM

    For old netweaver (<7.3)

    1. ABAP part

    1.1 in client 001

    1.1.1 create ADSUSER (system) and ADS_AGENT (service)

    1.1.2 assign role sap_bc_fp_icf and sap_bc_fpads_icf to ads_agent

    1.1.3 create ads_agent user in all clients with roles

    1.2 sm59 transaction

    1.2.1 HTTP connection to external server - name ADS - technical settings

    1.2.2 choose target host and port (usually 8000), path prefix /AdobeDocumentServices/Config?style=rpc

    1.2.3 logon and security - use ADSUSER and his password

    1.3 sicf transaction

    1.3.1 service path - activate two services - /sap/bc/fp and /sap/bc/fpads. In service check Goto > Port information (8000 port)

    1.4 spad transaction> create PDF printer. Device type PDF1. Access method - f. Host printer - 2PDF (improvise with it)

    2. Java part

    2.1 login to visual admin with j2ee_admin user

    2.2 server<x> > services > destinations > http > FP_ICF_DATA<SID>. Connection settings http://hostname:port (8000). Choose client and basic auth. Username ADS_AGENT and password. Save it.

    2.3 server<x> >services > security provider > user managment. Add users ADSUSER and ADS_AGENT to group ADSCallers. Policy configuratin tab > components > com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar . Choose role ADSCallers and map ADSUSER and ADS_AGENT

    2.4 server > services > Web Services Security > choose web service clients > > tc~wd~pdfobject >*ConfigPort_Document. Choose basis auth. Enter ADSUser and it's password. Services > deploy > choose button "application". Choose from tree Press stop application and start application again.

    2.5 Test. sa38 transaction > FP_TEST_00 > choose PDF printer > make a preview.

    There is a configuration assistant in the new netweaver. Just choose "Configuration of Adobe Document services as a hub".

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Igor,

      The OP wasn't asking about configuration of ABAP connectivity to ADS, but rather about configuration of another Java system (that isn't the ADS system) to ADS. He also stated he has access to and has read the official documentation, but wanted some clarification about which steps to perform on ADS and which on the connecting Java system. I'm not sure how your list of steps (which are related to connecting ABAP systems) is helpful for this.


  • Oct 20, 2016 at 10:37 PM

    In the "Configuring Adobe Document Services for Form Processing (Java)" help link there is a section called "Procedure" which suggests the basic ADS configuration with the link "Performing Basic ADS Configuration in a Java Environment". Have you performed this?

    Add comment
    10|10000 characters needed characters exceeded

    • Hi Saurabh,

      The Java Functional Unit Configuration is done on your ADS system, not the system that you are trying to connect to it (i.e., your MII system).

      The main thing you need to do on your client system (MII) is set up client certificates in key storage for your ADSuser, export them, and then import them to the ADS server to the ADSuser. Then, you need to setup the web service security on MII to point to your ADS server and reference the ADSuser. I think that should all be described in the online help, but I agree it can be confusing as to which parts are done on ADS and which on the client system when the two are not the same host.