Monday, June 8, 2009

Configuration of Adobe Document Services


 

STEP 1: Installing a credential for Adobe Document Services


 

In order to work with Adobe Document Services you need to install a valid credential.


 

To install a credential perform following steps:

Extract the archive

Copy the file <filename>.pfx to the directory

<INST_DRIVE>:\usr\sap\J2E\SYS\global\AdobeDocumentServices\TrustManagerService\

trust\credentials


 

Register the password for credential as described below:

Log on to the Visual Administrator (<INST_DRIVE>:\usr\sap\J2E\JC00\j2ee\admin\go.bat)


 

On the Cluster tab, choose Server 0 -> Services -> Document Services Configuration

On the Runtime tab, select Credentials

Choose Browse to search for the name of the credential and then select

In the Alias field, enter the alias of the credential you installed, for example ReaderRights (Entries for the name of the credential are case-sensitive)

In Password field, enter the password you received together with the credential you installed (filename.txt in the archive). Confirm the password again and then click Add

Restart the following services for the changes to take effect: PDF Manipulation Module, Document Services Trust Manager. To perform this, right-click on the repective service choose Stop and after the service has stopped, Start it again

Restart also the application com.adobe/AdobeDocumentServices located at

Server 0 -> Services -> Deploy (radio button Application)


 

STEP 2: Creating a User in SAP Netweaver AS Java for Basic Authentication


 

Use

In some cases the user ADSUser was not created during installation. This user is required for the secure communication between the Web Dynpro application and the Java system where the Adobe document services are installed.

Creating the User ADSUser and Assigning the Security Role

1. Log on to the Visual Administrator.

2. On the Cluster tab, choose Server <x> → Services → Security Provider.

3. On the User Management tab, choose Create Group to create a group called ADSCallers, if the group does not exist. In the dialog that follows, enter the name and choose OK.

4. Choose Create User. The Create New User dialog box is displayed.

5. In the User name, Password, and Confirm password boxes, enter ADSUser for the user name and type a password.

6. Choose the Tree tab in the right panel. In the User Tree, select ADSCallers, and then choose OK.

7. On the Policy Configuration tab, in the Components area, select

com.adobe/AdobeDocumentServices*AdobeDocumentServicesAssembly.jar.

8. On the Security Roles tab, select ADSCaller from the Security Roles list


 

Note: The ADSCaller security role was created when your system was installed. You should not assign this security role to users other than the system user that you will use for accessing Adobe document services.

9. In the Mappings area, choose Add, which is assigned to Users. A dialog Choose Users or Groups is displayed.

10. Choose the Tree tab.

11. In the User Tree, under the ADSCallers group, select the ADSUser you just created and choose OK. This assigns the new user to the ADSCaller security role


 

Defining ADSUser as Technical User


 

To prevent, that the password for the ADSUser expires, do following:

1. Log on to the User Management of your AS Java:

http://<AS Java server> :< http port> → User Management

2. Display the user ADSUser.

3. Choose Modify.

4. In the Security policy field, change the setting from Default to Technical User

5. Save.


 


 

STEP 3: Setting Up Basic Authentication in a Java Environment

Use

This procedure applies for the scenario of interactive forms. Set up Basic Authentication to access the Java version of the PDF object. This procedure describes you the configuration steps and applies when the Adobe document services and the Web Dynpro runtime are installed on the same J2EE Engine. Then under Destination the URL is set to Default.

Prerequisites

The user ADSUser was created and configured during installation of Adobe document service.


 

Procedure

To set up Basic Authentication in a Java environment:

1. Log on to the Visual Administrator.

2. On the Cluster tab, choose Server <x> → Services → Web Services Security.

3. Choose Web Service Clients → sap.com > tc~wd~pdfobject → com.sap.tc.webdynpro.adsproxy.AdsProxy*ConfigPort_Document.

4. From the Authentication list, select BASIC.

5. In the User and Password boxes, enter as Username ADSUser and a Password.

6. Choose Save.

7. The authentication data must be activated. For doing this navigate to Services → Deploy

8. Choose the button Application.

9. Choose sap.com/tc~wd~pdfobject in the tree.

10. Choose Stop Application.

11. For restarting the application choose Start Application.


 

Note: If the Adobe document services and the Web Dynpro runtime environment are not installed on the same J2EE Engine, you have to configure a Custom URL.


 


 

How to Check if ADS is Configured


 

How to Check if ADS is Configured:


 

    Log on to the Visual Administrator

    (<INST_DRIVE>:\usr\sap\J2E\JC00\j2ee\admin\go.bat)


 

  • On the Cluster tab, choose Server 0 -> Services -> Document Services Configuration


     

  • On the Runtime tab see the Credential.


 

How to check if ADSUser was created:


 

Log on to the Visual Administrator.


 


  • On the Cluster tab, choose Server <x>

    Services

    Security Provider.


     

  • On the User Management tab, Please see for a group called ADSCallers, Check for the ADSUser in this group.


 


 

SDM Cannot Start J2EE Cluster

SDM Cannot Start J2EE Cluster

Problem

If you see one of the following messages in the SDM logs or in the SDM Remote GUI Client deployment result panel:

SDM could not start the J2EE cluster on the host HOST_NAME! The online deployment is terminated.
A timeout occurred during the cluster running verification!

or

SDM could not stop the J2EE cluster! The offline deployment is terminated.
com.sap.sdm.apiint.serverext.sdmprovided.JStartupControllerException: A timeout occurred during the cluster stopped verification!

or

SDM could not start the J2EE cluster on the host <host_name>! The online deployment is terminated.
A timeout occurred during the cluster running verification!

then this generally means that the SDM feature "automatic start/stop of SAP J2EE Engine" was enabled (since SP6 release this is the default SDM behavior) and a timeout occurred when SDM tried to start/stop the J2EE Engine.

Solution

The default timeout is 1800000 milliseconds(=30 minutes), so if the environment where the J2EE Engine is started or stopped has lower computing capabilities, then the process itself will be slower and the timeout should be increased.

Open command prompt in directory /usr/sap/<SID>/<INSTANCE_NAME >/SDM/program and execute:

sdm j2eeenginestartstop mode=automatic timeoutmillisec=<increased_timeout>

SDM cannot Connect to J2EE Engine

SDM cannot Connect to J2EE Engine

Problem

A frequent situation is when SDM is not able to connect to the J2EE Engine due to incorrect security credentials stored in the SecureStore FS.

Secure Store FS is the place where SDM gets security credentials for connecting to the J2EE Engine. The following error can be viewed in the SDM logs or the SDM Remote GUI Client deployment result panel:

ERROR: Cannot connect to Host: [HOST_NAME] with UserName:[USER_NAME]
Check your Login Info.
Exception is:
com.sap.engine.services.jndi.persistent.exceptions.NoPermissionException
Exception during getInitialContext operation
Wrong security principles/credentials

this means that administrator, user and/or password have been changed using the Visual Admin tool, but were not changed in the secure store.

Solution

You should start configtool.bat(.sh) located in /usr/sap/<SID>/<INSTANCE_NAME >/j2ee/configtool.

You can check in the Secure Store whether the user name and password are correct. (The password cannot be seen but you can overwrite it with the correct one.)

Another solution for this situation can be found in SAP Note 701654.

If the administrator user is locked and therefore you cannot connect with SDM nor in any other way (Visual Admin, Telnet, Web application), one possible solution is to unlock the administrator user using SAP Note 669848.

SDM Troubleshooting

SDM Server Fails to Start

Problem

If you try to start the SDM server and either:

...

It fails to start with exit code 8

  1. Text such as the following exists in SDM:

    SDM is currently detached from JStartupFramework. Forward this information to the JStartupFramework (disable SDM process).

This means that SDM is currently in what is called standalone mode.

Solution

To start it using the JStartupFramework, you should set it to integrated mode. Open the command prompt in directory /usr/sap/<SID>/<INSTANCE_NAME >/SDM/program and execute:

sdm jstartup mode=integrated

Note that depending on your command interpreter, the param name, equal sign and param value may be enclosed with quotation marks(").

After executing the command, try to start the SDM server again.

Welcome to SAP NW Administration Tutorials

Welcome to SAP NW Administration Tutorials