Configuring General System Parameters

Use

Before you start using Guided Procedures (GP), you must configure its system parameters so that it runs properly.

Below you can find a list of all configuration parameters that you require for using GP. This list does not include parameters for special applications such as the Bounced Mails Framework and composite forms.

Prerequisites

You have access to the Config Tool of the Application Server Java (AS Java).

For more information, see Config Tool .

Procedure

  1. Open the Config Tool.
  2. Navigate to cluster-data →template - <name of template> → instance - <name of instance>  → services  → caf/eu/gp/model.
  3. Modify the required system parameters:
    1. On the Service properties screen, select a parameter from the table.
    2. In the Custom value field, enter a value for the parameter.
    3. Choose Set.

      The new value appears in the Value column.

    You can apply the procedure above for the following general system parameters:

    Parameter Parameter description

    system.workflow.engine.local.threads

    Determines the number of worker threads the GP Workflow Engine uses.

    • Default value: 2
    • Possible values: 1 through10

    system.type

    Determines the system type installation. By default, there is no value for this property.

    pfw.dt.er.template.show

    Determines whether the event resolution template is displayed in the design time.

    • Default value: false
    • Possible values:
      • true (the template is displayed)
      • false (the template is not displayed)

    devobj.after_import_processing

    Determines whether imported objects need to be post-processed in the Administration workset or are directly available for the GP design time.

    Post-processing includes:

    • Checking the existing object authorizations
    • Additional semantic check for specific object types

    For more information about this Administration workset functionality, refer to:

    Importing Transport Requests

    Postprocessing Imported Objects

    • Default value: true
    • Possible values:
      • true (post-processing)
      • false (no post-processing)

    devobj.content_release

    The value set is assigned to each new object created as the release information.

    • Default value: none
    • Possible values: freely selectable

    devobj.producer

    If the default value is retained, the system does not create new versions for SAP-specific objects. To modify SAP-specific objects, customers need to create copies of them first. Working with copies effectively ensures for the customer that any modifications made to SAP-specific objects are not lost when the system is updated (in this case, the objects would be overwritten by SAP / SAP partners).

    • Default value: SAP
    • Possible values: freely selectable. However, modifications should only be made by SAP or SAP partners.

    http.server.base.url

    Base URL of the AS Java instance on which GP runs.

    smtp.server

    Sets the mail server for SMTP-based exchange of e-mails and composite forms.

    • Default value: none
    • Possible values: freely selectable depending on the mail servers available. The value can be an IP address or a domain, for example mail.sap.corp.

    smtp.service_user_mail

    Sets the sender address for outgoing e-mails. This parameter directly refers to the parameter smtp.server.

    • Default value: none
    • Possible values: freely selectable

    system.fallbacklang

    Sets the alternative language of the system.

    • Default value: en (English)
    • Possible values: the common language codes for all languages in which the portal was delivered

    transport.translation.contact.name

    Sets the developer to be contacted by translators. This parameter is only relevant outside SAP if a customer-specific NWDI transport environment exists.

    • Default value: none
    • Possible values. name or user ID of contact person