Setup for Lead Processing via Interactive
Forms 
Purpose
Use this process to set up lead processing using interactive forms.
Prerequisites
· Adobe Document Server (ADS)
You have installed the Adobe Document Server (ADS), which is a component required to render documents in the Adobe Portable Document Format and a part of the Portal Installation. For more information on installing or setting up the ADS, see the corresponding installation and configuration guide in the SAP Service Marketplace at service.sap.com/instguides ® SAP NetWeaver Release 04 ® Installation ® SAP WebAS ® SAP Web AS 6.40 SR1 Installation and Related Documentation ® Adobe Document Services.
· Composite Application Framework Guided Procedures (CAF GP 2.0)
You have installed the CAF GP 2.0 framework, which is required to implement the CELQS and a part of the Portal Installation. For more information, see the SAP Service Marketplace at service.sap.com/instguides ® SAP NetWeaver
Release 04 ® Installation ® SAP CAF ® SAP CAF 2.0 Installation Guide.
· Mailbox
You have installed a mailbox, which is required to send out leads and receive responses.
· Users
¡ Two technology stacks are present within the CELQS:
§ The ABAP stack (CRM Server)
§ The JAVA stack (J2EE Engine, Portal)
The CELQS requires users in both stacks, together with a corresponding user mapping.
¡ Three types of users are relevant to the Java Stack (guided procedures) scenario:
§ GPADMIN:
This user is responsible for all administrative tasks, such as configuring the scenario.
Create a user of type GPADMIN within the portal and assign the following roles:
· com.sap.caf.eu.gp.roles.administration
· com.sap.caf.eu.gp.roles.designtime
· com.sap.caf.eu.gp.roles.runtime
· com.sap.caf.eu.gp.roles.sap_system_user
§ GPUSER:
This user is responsible to instantiate and finally execute the scenario.
The CELQS makes use of the SAP Workflow. The user, whose credentials are used to start the process within the ABAP stack, needs to be known in the JAVA stack as well. This user is of type GPUSER.
Create a user on the portal and map this user against the corresponding user within CRM Server
Assign the following roles:
· com.sap.caf.eu.gp.roles.sap_system_user
GPADMIN and GPUSER are just identifiers for different types of users and not necessarily real user names.
§ GUEST:
Assign the following role to portal user GUEST:
· com.sap.caf.eu.gp.roles.sap_system_user
¡ The following workflow user is relevant to the ABAP scenario:
§ WF-BATCH :
SAP Business Workflow background process steps are executed with the credentials of a special user (business workflow background user, typically WF-BATCH) and not necessarily with the credentials of the user who started the workflow. In this case, also the business workflow background user needs to be known within the Java stack:
Create a user (for the business workflow background user) on the portal and map this user against the corresponding user within CRM Server
Assign the following roles:
· com.sap.caf.eu.gp.roles.sap_system_user
Process Flow
...
1. Create communication connections
Create connections to establish communication between CAF GP 2.0 within the JAVA stack and the CRM Server.
¡ JAVA stack
§ Choose Visual Administrator.
§ Create a JCo-RFC Destination with the following parameters:
· Program ID: GPRuntimeService
· Gateway Host: Gateway host of your CRM Backend System
· Gateway Service: Gateway Service of your CRM Backend System
§ Start the service.
¡ CRM Server
§ Choose transaction SWU3 ® Guided Procedures ® Maintain Guided Procedures Gateway.
§ Enter the Gateway Host and Gateway Service of your CRM Server.
§ Choose SM59 ® TCP/IP connections ® SWF_GP_RUNTIME_900. The name of the RFC destination is generated automatically by the system, and is dependent on the client (Here: 900) to which you logged on.
§ Choose Connection Test and verify that the connection works.
2. Establish Endpoints
Establish endpoints to invoke CAF GP 2.0 from the ABAP stack and to invoke ABAP functions from the Java stack.
¡ Java Stack
§ Log on to the portal with a user of type GPADMIN and choose Administration ® SAP System: Configure Endpoints.
§ Enter the Endpoint Alias Name: CRM_EXT_LEAD_QUAL_DEST and the Endpoint Alias Type: Endpoint Alias for Remote Function Call (RFC)
§ Choose Add and enter the system parameters of your CRM Server.
¡ CRM Server
§ Choose transaction SM59 and create the logical destination CRM_CHM_GP_RUNTIME_SERVICE.
§ Enter the Reference Entry SWF_GP_RUNTIME_900. (Use the name of the RFC Destination which has been created with transaction SWU3.)
3. Configure Adapters
This step enables the CAF GP 2.0 to access the mailbox, which is required to send out leads and receive the answers from the external partners.
¡ Java Stack
§ Log on to the Portal with a user of type GPADMIN and choose Administration Interactive Forms: Configure Adapters -> Select Adobe Forms -> Add.
§ Enter the system settings of your mailbox:
· Protocol: A protocol supported by your mail server
· Server: Your mail server
· Folder Name: A mailbox folder that is scanned periodically for responses from your external partners
· User name: The user name, which is required for logging on to the mailbox.
· Personal mail box: User
· Service user mailbox: domain\user\mailboxname
· Password: ****** - the user’s password
· Client: The section before the @, for example, leads@sap.com
· Domain: The section after the @, for example, leads@sap.com
§ Ensure that CAF GP 2.0 is enabled for mail processing, by choosing Visual Administrator ® service caf/eu/gp/model and activating the following parameters:
· mailconnector_start_thread
· formqueue_processor_start_thread
¡ CRM Server
No actions are required.
4. Importing CAF GP 2.0 Content
The content for the CRM External Lead scenario is shipped within the ABAP stack. To run the scenario, the content must first be imported into the Java-Stack.
¡ Java Stack
§ Log on to the portal with a user of type GPADMIN.
§ Choose Administration ® Transport ® Import transport request.
§ Step 1:
Select the source system and choose an endpoint which points to your CRM Server.
If no endpoint is available as yet, proceed as described in Step 4.
§ Step 2:
Choose Request ->All Requests to see a list of available requests. Choose the request CRM_EXT_LEAD_QUAL_DELIVERY.
§ Step 3:
Release request by choosing Release Request.
The content required to execute the CELQS is now imported into the Java stack.
§ Verify the import by performing the following steps:
· Log on to the portal with a user of type GPADMIN.
· Choose Design Time -> CRM_EXT_LEAD_QUAL.
You can now view the following objects:
· CRM_EXT_LEAD_QUAL_FORM
· CRM_EXT_LEAD_QUAL_PREFILL
· CRM_EXT_LEAD_QUAL_VALIDATE
¡ CRM Server
No actions are required.