Getting Started With PeopleSoft Enterprise Components

This chapter provides information about getting started in the following PeopleSoft Enterprise Component areas:

• PeopleSoft Directory Interface

• Common Objects and Components

• PeopleSoft Active Analytics Framework

• Enterprise Integration

Getting Started With PeopleSoft Directory Interface

Setting up to use the PeopleSoft Directory Interface requires you access components in PeopleSoft PeopleTools to define and activate nodes and transactions, create authentication and user profile maps, and so on. You also access components in PeopleSoft Enterprise Components to configure and load the directory.

See Using PeopleSoft Directory Interface.

Implementation Guidelines

Consider these guidelines for best results.

• LDAP Searches. Some LDAP searches may generate LDAP referrals to other servers participating in your directory. You must be able to ping by hostname all servers in the directory from the application server. If any server is unreachable by hostname from the application server, you can add a line for the server to the hosts. Your directory information tree must have user entries at the leaf level. This is required when an entry needs to be moved from one branch to another. The entry needs to be at the leaf level so that the system can read user attributes, one of which is the password. file on the application server.

• Entry Limit. In the directory, configure the entry limit value to be larger than the number of rows that you expect will be returned. The default value is usually not sufficient.

• Directory Tree. Your directory information tree must have user entries at the leaf level. This is required when an entry needs to be moved from one branch to another. The entry needs to be at the leaf level so that the system can read user attributes, one of which is the password.

• The following items apply to implementations that use Microsoft Active Directory:

  • The registry key HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Schema Update Allowed must be present and set to a nonzero DWORD on the Active Directory FSMO Role Owner.

  • When creating structural object classes in Microsoft Active Directory, you need to specify containment. PsftJobs can be children of the following classes of objects only: builtinDomain, organizationalUnit, and domainDNS.

  • You must add the server names in the Directory Setup component as they appear on the DNSHost Name attribute on the server entries under the CN=Sites entry.

Getting Started With Common Objects and Components

PeopleSoft Enterprise Components provides objects and components that can be used by various PeopleSoft applications. For set up or implementation information of the following components, refer to each chapter.

See Using Datasets.

See Using Interactive Reports.

See Setting Up the Credit Card Interface.

Getting Started With PeopleSoft Active Analytics Framework

PeopleSoft Active Analytics Framework is a closed-loop decision-making system comprising a suite of tools. Refer to the following chapter for an overview of the framework:

See Understanding PeopleSoft Active Analytics Framework.

The framework includes:

• Components for building and managing policies.

  See Building and Managing Policies.

• A data library for registering terms.

  See Setting Up the Data Library.

• Components for creating and managing contexts.

  See Managing Contexts.

• An action framework.

  See Setting Up the Action Framework.

• Components for setting log options and registering elements of the framework.

  See Administering the Framework.

• Considerations for technical users, such as creating custom operator expressions, trigger points, a new action type and so on.

  See Considerations for Enabling the Framework.

Getting Started With Enterprise Integration

PeopleSoft enterprise integration technology includes various features and utilities. The elements you use will depend on your PeopleSoft application.

If you are using integration points, the following sections may be helpful:

See Integration Point Naming Standards.

See PeopleSoft Design Patterns.

See Setting Up PeopleSoft Messaging Integration Points.

See Setting Up Related Languages.

See Setting Up and Maintaining Message Errors.