Pre-requisites
It is necessary to go through the following SAP Notes before we start the installation of ADS.| 736902 – Adobe Credentials |
| 944221 - Troubleshooting if problems occur in forms processing |
| 894009 – ADS: Configuration Guide (NW 7.0) |
| 685571 – Printing pdf based forms |
I. Configuration in ABAP AS and JAVA AS (non-dual stack)
1. Create user ADSUSER in JAVA AS in either Visual Administrator or IRJ Portal, if it does not exist already. Usually ADSUSER will be created during the installation in JAVA AS system as of release NW 7.0
Visual Admin: server<x> --> services --> Security Provider.
IRJ Portal: http://<fully qualified name>:5<XX>00/irj/portal
Note: User type must be TECHNICAL USER as follows.
2. Assign security role in Java Stack.
a. Go to Visual Admin
b. On the Cluster tab, choose Server <x> → Services → Security Provider.
c. On the User Management tab, choose the Tree tab in the left panel.
d. In the User Tree, ensure that the user you created in ABAP appears under the ADSCALLERS group.
e. On the Policy Configurations tab, in the Components area, select
com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar.
f. On the Security Roles tab, select ADSCALLER from the Security Roles list.
g. In the Mappings area, choose Add, which is assigned to Users. A dialog Choose Users or Groups is displayed.
h. Choose the Tree tab.
i. In the User Tree, under the ADSCALLERS group, select the ADSUSER you just created and choose OK. This assigns the new user to the ADSCALLERS security role.
3. Create Service User ADS_AGENT in ABAP (SU01), if it does not exist.
a. User type must be "System"
4. Create ABAP RFC Connection (SM59)
a. Go to SM59 and create destination called ADS under “HTTP Connections to External Server” and connection type “G”.
b. Provide Target Host in “Technical Settings” tab. If you are configuring in dual stack (ABAP & JAVA) system like CRM, target host must be ABAP host name and specify the Service No. (5<XX>00). Note: Patch Prefix must be /AdobeDocumentServices/Config?style=rpc
c. Go to “Logon & Security” tab; choose ‘Basic Authentication’ under Logon Procedure. In Logon security Tab, enter ADSUSER and its password.
d. Other fields can be left as defaults.
e. Test the connection. You should be successful.
5. Activate ICF Services
a. Log on to your SAP Web AS ABAP system
b. Choose transaction SICF.
c. Choose default_host → sap → bc → fp in the tree.
d. Choose Service/Virt.Host → Activate
Note: 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 ICF service.
6. Create following Destination Service FP_ICF_DATA_<SID> (Visual Admin)a. Fill the fields URL (http://<hostname>:<HTTP_port>), System ID, Client (if required to be set to specific client), Authentication and user name & password of ADS_AGENT (which was created in ABAP stack) with respect to your target system.
Note: You can get the HTTP_Port number from transaction SICF
b. Client on tab Save and Test
Note: If you choose Save and Test, you can ignore the message Error during ping operation:
Received HTTP response 404.
7. Set up Basic Authentication in JAVA Environment
a. Log on to the Visual Administrator.
b. On the Cluster tab, choose Server <x> → Services → Web Services Security.
c. Choose Web Service Clients → sap.com > tc~wd~pdfobject →
com.sap.tc.webdynpro.adsproxy.AdsProxy*ConfigPort_Document.
d. From the Authentication list, select BASIC.
e. In the User and Password boxes, enter as Username ADSUSER and a Password.
f. Choose Save.
g. The authentication data must be activated. For doing this navigate to Services → Deploy.
h. Choose the button Application.
i. Choose sap.com/tc~wd~pdfobject in the tree.
j. Choose Start Application.
II. Configuration in ABAP & JAVA AS (Dual Stack Systems)
a. In dual stack systems, we need to create both users ADSUSER and ADS_AGNET in ABAP Stack via tcode SU01.
b. User type must be “System”
c. Create role ADSCALLERS and assign it to ADSUSER along with the below shown SAP_BC* roles.
Note: The ADSCALLERS role in SAP NW AS ABAP appears automatically as ADSCALLERS group in the J2EE Engine.
d. Perform the steps from 2 to 7 from the above.
III. Install Credentials for Adobe Document Service (ADS) Interactive forms.1. Place credential file *.pfx in /sapmnt/<SID>/global/AdobeDocumentServices/TrustManagerService/trust/credentials.
Note: You have to get the Adobe credentials from SAP. Please go through the note 736902 for more details. This credential is unique for a customer/client and this is one-time request.
2. Perform the below steps:
a. Log on to the Visual Administrator
b. On the Cluster tab, choose Server <x> --> Services --> Document Services Configuration
c. From the Type field, select the type of credential you are configuring (P12 Record)
d. In the Alias field, enter the alias of the credential you installed (ReaderRights)
e. For a P12 Record, choose Browse to search for the name of the credential and then select.
f. In Password field, enter the password you received together with the credential you installed.
g. Confirm the password again and then click Add.
The page refreshes and the list of registered credentials at the top of the page includes the credential you just added.
3. Restart Java Engine.
4. Execute report FP_TEST_IA_01 via SA38. After giving output device, click on Print preview.
You should see the page in PDF form which means it is working fine.
IV. Configuration Check
A.
➢ Go to SA38
➢ Test program FP_TEST_00
➢ If the FP_TEST_00 form is displayed in the print preview, the ADS configuration is correct.
If the system displays an error message instead of a form, the configuration of ADS is incorrect. Then carry out additional tests. Go for STEP II
B.
➢ Now check RFC connection to ADS by Program FP_PDF_TEST_00 in SA38
➢ If the system displays the version number of ADS, the configuration of the RFC connection is correct. Then Proceed with III
Otherwise you will receive one of the following error messages:
1. If the system displays dialog fields for user and password instead of the version number, the entries for user and password in the RFC connection do not match the entries in user management.
-> Check the user and the password. Continue with point
2. The system displays a "SYSTEM ERROR" with the following text:
ERROR MESSAGE: SOAP Runtime Exception: CSoapExceptionTransport : HTTP send returned with status code"
-> Check or correct the details for target device, service number and path prefix in the RFC connection (transaction SM59).
3. If the system displays an error message stating that there is no valid HTTP connection, then there is no RFC connection to ADS.
__MCE_ITEM____MCE_ITEM__รจ Correct or create the RFC connection (transaction SM59).
C. Check the Setting for Destination Service
In SA38 call FP_CHECK_DESTINATION_SERVICE and FP_CHECK_HTTP_DATA_TRANSFER
a) First of all, execute the program without selecting the option "With Destination Service".
b) Now select the option "With Destination Service" and execute the program again. The system processes the test form, using the destination service.
If the system displays the same message (file size of generated PDF) as it does in a), the configuration of the destination service is correct.
If the System issues error message carry out following steps:
1. Enter the following URL in your Web browser:
http://<server>:<port>/sap/bc/fp/form/layout/fp_test_00.xdp
2. In the dialog box for the user, enter ADS_AGENT and the relevant password.
If the browser displays an error message instead of the XML file,
a) Call Visual Administrator and navigate to Services -> Destinations
b) Extend the setting in field URLunder Connection Settings to:
http://<server>:<port>/sap/bc/fp/form/layout/fp_test_00.xdp
c) Choose 'Save and Test'
If the settings are correct, the system issues the message: "HTTP GET response code 200 Content Type/xml.".
Note: Do not forget to change the URL back to http://<server>:<port>
3. If you get the error FPRUNX004 while executing any of the above tests do the following:
a. Go to transaction SE37
b. Execute the function module FP_GET_LAST_ADS_ERRSTR
After you have called the FP_GET_LAST_ADS_ERRSTR function module, the system will delete the text internally. A second call will, therefore, not return any results.
No comments:
Post a Comment