In this section:
See Getting Started with DTP Enterprise Pack for additional information about administrating Extension Designer and Policy Center, including backing up, restoring, and upgrading. |
See Requirements.
You should use the same local user to install enterprise pack with DTP. This is to enable full integration and avoid potential issues in some environments. The user should have a local home directory, not a network shared directory.
By default, Enterprise Pack is installed in [DTP_HOME]/dtpservices, but you can install the applications on different servers if necessary. They should both, however, be installed on the same network.
On Windows, they should use the same domain (Active Directory) and the server's FQDN (Fully Qualified Domain Name) should be resolved by a DNS name server.
On Linux, the domain name must be configured and the server's FQDN should be resolved by a DNS name server.
For the full duration of your DTP and Policy Center implementation, you should only integrate one DTP server with one instance of Policy Center. This is because Policy Center requires DTP's project list to be consistent so that accurate information is displayed. The following scenarios describe potential issues regarding this requirement and how to resolve them:
Scenario | Resolution |
---|---|
Moving DTP to new server | If you are migrating to new DTP, be sure to move the Enterprise Pack installation at the same time so that all internal data is consistent. |
Lost DTP and data | If DTP data is lost, reset the Policy Center database when DTP is brought back online. All previously stored data will no longer be valid. |
Set testing against production | A separate Enterprise Pack installation should be deployed for each environment. |
Setting Default Ports for Connected Services
You can specify a default host and port for applications connecting to DTP using the services API. This enables you to redirect users to the appropriate URL if you need to enforce SSL, for example. DTP Enterprise Pack applications, for example, use the services API to communicate with Report Center.
Locate the <default-server-url>
element and provide a valid URL:
<default-server-url>http://example.host.com:port</default-server-url> |