Steps to done the ADS configuration on ABAP system and AS JAVA system.
The ADS component will already be there in the system we only need to make the configuration settings.
Please check SAP note 2029940 (Required Additional RPM packages for ADS on Linux) and make sure all the rpm’s are installed if you are using Linux environment
How to check if ADS is installed or not
http://.:500xx/startPage
http://<hostname>.<domain>:500xx/startPage
Click on System Information
We have to look for the component ADSSAP
Configuration to be done at ABAP stack:
(Ask SECURITY TEAM to create the USERS)
- Create two users as below:
ADSUSER with role ADSCALLERS
ADSCALLERS role will need to be created in PFCG and then we will add user ID here in ADSCALLERS.
ADS_AGENT with role SAP_BC_FPADS_ICF
Please do the caution while creating user and their respective role, while troubleshooting issue this is imp step.
- Create RFC destination ADS
Path prefix:
/AdobeDocumentServices/Config?style=rpc
It won’t accept the string as path prefix just hit enter after entering the path prefix in the field.
Activating Services:
Then go to tcode SICF and activate below services.
/default_host/sap/bc/fp
/default_host/sap/bc/fpads
Configuration to be done at JAVA stack:
If UME of AS Java is running on As ABAP system (in this case)
- a) Create ADSUSER in As ABAP.
- b) Create ADSCALLERS role in PFCG and don’t assign any authorization to it.
- c) Assign ADSCALLERS role to ADSUSER.
Above 3 step already done, just for verification
- d) Go to Identity Management of AS Java, there search for role SAP_ADSCALLER and add user ADSUSER to it.
Now , Go to SAP netweaver administrator http:// <hostname>.<domain>:500xx/startPage /nwa
We need to create two destinations here.
WSIL and FP_ICF_DATA_<ABAP_SID>
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 as below:
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 again go to SOA. Under SOA, go to Technical Configuration –> Destinations
Here create FP_ICF_DATA_<ABAP_SID> destination as below.
After this once check for the ADOBE services as below.
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.
The configuration part has been completed here now test for the ADOBE Functionality as below.
Test the functionality by executing below programs.
FP_TEST_00
If the FP_TEST_00 form is displayed in the print preview, the ADS configuration is correct.
FP_PDF_TEST_00
This enables you to check the RFC connection to ADS
If the system displays the version number of ADS, the configuration of the user and password is correct.
FP_CHECK_DESTINATION_SERVICE
Test destination service
Optional Activity:
If you need to have interactive ADS form perform below ADS license steps
Step 1: TCODE: SA38
now we have to apply the license.
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 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.
RESTART the SAP java application server.
Checking ADS is working or not.
Step 1: TCODE: SA38
SELCET OUTPUT DEVICES: LP01
All Test is successful now.