Administering Windchill ESI
Administering Windchill ESI involves configuring and modifying some or all of the following:
• Windchill ESI Preferences
• Distribution Target Attributes
• Windchill Remote Procedure Call (RPC) Definitions
• TIBCO Components
As a Windchill ESI administrator, you can perform the above using the administration utilities described below:
Preference Management Utility
The Preference Management utility allows users to view and set preferences, such as display and search options, to enhance their Windchill experience, and allows administrators to view and set preferences for various application contexts, such as projects, products or organizations.
Windchill ESI preferences fall into the following two general categories:
• Preferences that are configurable. These include preferences that are used with the standard Windchill ESI product without being modified.
• Preferences that are used in the customization of Windchill ESI. These include preferences that should only be modified when customizing Windchill ESI. Windchill ESI provides a number of customization points that allow the Windchill ESI environment to be modified and extended to suit the varying list of different business needs. For more information refer to the following guides:
◦ Windchill Enterprise Systems Integration Customizer's Guide - Oracle Applications (Windchill Enterprise Systems Integration 自訂指南 - Oracle Applications)
◦ 《Windchill Enterprise Systems Integration Customizer's Guide - SAP R/3》
For information on using the Preference Management utility, refer to the online help.
Manage Distribution
This utility allows you to create or edit a distribution target (which is essentially an ESITarget object) in Windchill. For more information about the Distribution Target Attributes, see the following guides:
• 《Windchill Enterprise Systems Integration Installation and Configuration - SAP R/3》
• Windchill Enterprise Systems Integration Installation and Configuration - Oracle Applications (Windchill Enterprise Systems Integration 安裝及組態 - Oracle Applications)
Windchill Delegate Administration Utility
The standard Windchill ESI Remote Procedure Call (RPC) definitions are created at the time of installing Windchill ESI services. RPC definitions are stored in the LDAP directory that was created when Info*Engine was installed. Generally you do not need to modify the standard RPC definitions for Windchill ESI unless you are customizing your environment. The RPC definitions can be accessed using the Info*Engine Property Administration utility or an LDAP browser. For more information on how to customize Windchill ESI, see the following sections:
• Windchill Enterprise Systems Integration Customizer's Guide - Oracle Applications (Windchill Enterprise Systems Integration 自訂指南 - Oracle Applications)
• 《Windchill Enterprise Systems Integration Customizer's Guide - SAP R/3》
TIBCO Utilities
The following table lists the utilities provided with the TIBCO software that are used to perform various administrative tasks. For more information on these utilities refer to the following sections:
• 《Windchill Enterprise Systems Integration Installation and Configuration - SAP R/3》
• Windchill Enterprise Systems Integration Installation and Configuration - Oracle Applications (Windchill Enterprise Systems Integration 安裝及組態 - Oracle Applications)
Utility
|
Purpose
|
TIBCO EMS Administration tool
|
Configures EMS queues for tasks such as authenticating and setting permissions for various users.
|
TIBCO Administrator
|
Supports security administration as well as monitoring and management of processes and machines. The TIBCO Administrator consists of the following:
• TIBCO Administration Server
• A web-based TIBCO Administrator graphical user interface (GUI) to deploy or un-deploy the default ESI EAR and customized EAR and after deployment to start or stop the process archive and adapter services for the deployed application.
|
TIBCO Designer
|
Provides a GUI that supports the following:
• Configuring adapters at design-time
• Designing processes
• Configuring deployments
• Deploying the integration project
|