Deploying Server Definitions
Server definitions are changed using the UF_ADMIN entry point form or equivalent. If you don't want this capability in your deployed applications then don't deploy UF_ADMIN or equivalent to your end-users.
The ability of end-users to edit server settings may have an effect on what you decide to ship in VF_Sy001_Servers.XML when:
- Deploying your Framework to end-user environment for the first time.
- Upgrading your Framework in end-user environments.
Some of the options you have are:
- Don't deploy VF_Sy001_Servers.XML at all. Deploy your application with instructions on how to use UF_ADMIN (or equivalent) so that end-users can define their own unique server environment.
- Centrally deploy VF_Sy001_Servers.XML with all server details predefined in it. No end-user use of UF_ADMIN (or equivalent) would be required for server definition. Normally this is only an option when only a well defined set of server systems is possible.
- Deploy VF_Sy001_Servers.XML with a predefined set of partially completed set of server examples in it. Combine this with instructions to your end-users on how to use UF_ADMIN (or equivalent) to use the shipped examples so as to define their own unique environment.
Scenario: In House Development, Well Known Servers
Scenario: ISV, Single Unknown Server
Scenario: ISV, Multiple Unknown Servers