Designing and Implementing Business Process Models : Implementing E-form Support for BPM : Configuring and Deploying an E-form Environment : Configuring an E-form Environment
Configuring an E-form Environment
You can create and deploy multiple e-form environments. For example, if your organization uses multiple paths to e-form documents in your repository, you must create and deploy an e-form environment for each one.
Similarly, if you have multiple repositories for your e-forms, you can create and deploy one or more environments for each repository location. For example, if you have different e-form repositories for different business units, you can create a separate environment for each repository.
Configuring an e-form environment consists of the following general actions:
*Define a repository server by specifying the physical connection information for the repository (also referred to as a logical server in Central Configuration), as well as the path to the e-form folders within the repository.
*Define one or more hosts where an Integration Server and Process Engine are running. This defines the target location(s) for deploying the environment.
*Map the repository server to the Integration Server host(s).
*Map the endpoint information for the host(s) by specifying a transport type and port for the host system(s).
*Verify the configuration.
To create an e-form environment
1. Log on to My webMethods using an account that has permissions for configuring an e-form environment (the Administrator account has these permissions by default).
2. In My webMethods: Navigate > Applications > Administration > System-Wide > Environments > Define Environments.
3. In the Environments window, click Add Environment.
4. In the Environment Information window:
a. Type an environment name, such as "InfoPath E-form Environment."
b. Type a description for the environment, such as "Contains InfoPath E-form Templates and Instances folders."
5. Click Save.
6. In the Environments window, click the link created by the new environment in the Environment Name column.
7. On the Design Servers tab of the Environment Configuration window, click Add.
8. On the Add Logical Servers dialog box, click E-forms Server in the Select Logical Servers list. This specifies that you are creating an e-form environment.
9. Click OK.
10. Click the Configure Servers tab.
11. If it is not already expanded, expand the E-forms Server entry in the Configuration column.
12. Click the E-forms Configuration link.
13. Define the repository connection information by typing the following:
*Friendly Name—this is configured by default as a concatenation of the repository server host name and server port. However, you can enter any text value (spaces are not allowed). This value is used to display a user-friendly name in Software AG Designer for the repository server that is hosting the e-form folders. This field has a character limit of 256.
Note:  
If you deploy more than one environment to the same Integration Server host, the Friendly Name must be unique for each environment.
*Server Host—the host name or IP address of the repository server. Enter only the host name or IP address; URL descriptors are not used.
*Server Port—the e-form port number for the repository server. If you are using My webMethods Server as your repository, accept the default value of 10999. You can specify a different port number as described in Changing the My webMethods Server Repository Port or Name.
*Server Path—the path within the server to the location of the e-form folders. If you are using My webMethods Server as your repository, accept the default value of mwsRepository. This field has a character limit of 1024. You can specify a different path name as described in Changing the My webMethods Server Repository Port or Name.
*Server User—the name of an existing user account with permission to access the contents of the e-form folders. For My webMethods Server, the default value is Administrator. This field has a character limit of 256.
*Server Password—the password for the specified user account. This field has a character limit of 256.
*Server Listening Path—the path to the e-form folder that will contain the instances that will be used to start a new business process. For example, if you are using My webMethods Server as your repository, with an Instances folder in Public Folders, the path would be /Public Folders/Instances. This field has a character limit of 1024.
Note:  
If you are creating an environment that defines only the location of your e-form templates, leave this value empty. If you do so, use caution with the environment. As it does not have an instance folder defined, it must not be used with a process model. Consider defining a friendly name such as, "Environment1_Templates_Only."
*Server Template Path—the path to the e-form folder that contains the templates that will be used by Software AG Designer. For example, if you are using My webMethods Server as your repository, with a Templates folder in Public Folders, the path would be /Public Folders/Templates. This field has a character limit of 1024.
Note:  
If you are storing your templates in a different repository from your e-form instances (or in a file system), leave this value empty. If you are storing your templates in a different repository you must create a separate environment to define the location of your templates.
14. Click Save.
15. Click the Define Hosts tab. On this tab, you define one or more Integration Server hosts. When you deploy this environment, it will be deployed to the host(s) defined here.
16. Click Add Host.
17. On the Add/Edit Host dialog box:
*Type a display name for the Integration Server host.
*Type the host name or IP address of the Integration Server host.
18. Click OK. If you want to add additional Integration Server hosts, repeat steps 16 and 17.
19. Click the Map Servers tab.
20. Click the Edit icon in the ACTIONS column to map an individual logical server, or click Map All. This maps your repository server to the Integration Server host(s).
21. Click the Map Endpoints tab. The default values are already configured on this tab, and the tab is automatically marked as configured. Do not change the http transport type.
Note:  
Accept the default port value of 15006 for hosts where you have only one Integration Server running on the specified host (unless you have a pre-existing port conflict). If you have two or more Integration Servers running on the same host hardware, you must take care to specify a separate port number for each Integration Server instance on that host. To change the e-form listener port definition, see Changing Host Port Numbers.
22. Click the Map DB Pools tab. There are no values to configure on this tab, and the tab is automatically marked as configured.
23. Click the Validate tab. If the configuration report indicates that you do not have a valid configuration, make changes to the environment configuration as needed and return to the Validate tab to re-validate the configuration.
Note:  
It is possible to obtain a valid configuration report but still have a configuration that will not work correctly. For example, a typographical error in a folder path or user account name will still be accepted as valid, although it will not work correctly when deployed.
24. Click Finish to return to the Define Environments page.
Copyright © 2016 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback