Creating Repository Folders

If you use My webMethods Server as your repository, you are advised to create your e-form folders in the Public Folders section of the My webMethods Server taxonomy. Wherever you locate the templates and instances folders, you must determine and apply the folder permissions you want to use.

By default, Public Folders are configured to provide write access for all authentication users. You may want to restrict write access for the templates folder to template administrators only and provide read-only access for a wider set of users.

The instances folder will typically need write access for another set of users (generally not all users), without the ability to delete instances, which would be provided to instance administrators.

Aside from the two points mentioned above, there are no limitations to or requirements for the folder structure you implement. Creating aliases for these folders is not required; however, aliases are useful if it is likely that the location of the folders will change if the environment will be moved from testing to production. Aliases are also useful if you plan to create custom CAF portlets that interact with these folders.

When you create e-form folders in your content repository, keep the following points in mind:

Always locate your template folders and your instance folders in the same repository.

Do not mix templates and instances in the same folder. If you decide to use your repository to store both templates and instances, you must create separate folders for templates and instances.

Do not mix e-form documents in the same instances folder. You must create a separate instances folder for each e-form document you want to work with.

For example, if you create an e-form document FormA, and another e-form document FormB, you must create separate instances folders for FormA and FormB.

Maintain different e-form template types in separate templates folders (this is recommended but not required).

Here is just one example of an e-form templates and instances folder arrangement for four e-forms, two created with LiveCycle and two created with InfoPath:

Note:

The use of Adobe LiveCycle e-forms with task applications may require you to define a location for PDF versions of your LiveCycle forms. For more information, see Adobe Design Time Considerations for Task Applications and Making Adobe E-form Instances Available at Run Time.