您所在位置： &
&nbsp&&nbsp&nbsp&&nbsp
Peoplesoft系统员工自助操作手册V2.0.docx 15页
本文档一共被下载：
次 ,您可全文免费在线阅读后下载本文档。
下载提示
1.本站不保证该用户上传的文档完整性，不预览、不比对内容而直接下载产生的反悔问题本站不予受理。
2.该文档所得收入(下载+内容+预览三)归上传者、原创者。
3.登录后可充值，立即自动返金币，充值渠道很便利
需要金币：350 &&
Peoplesoft系统员工自助操作手册V2.0
你可能关注的文档：
··········
··········
威高集团Peoplesoft系统用户操作手册-- 自助服务创建日期:控制编码:当前版本:2.0目录第一章用户手册惯例及系统通用操作31.1系统连接与访问方式31.1.1客户端和浏览器要求31.1.2网络要求31.1.3单点登录31.2用户登录与更改密码41.2.1用户登录41.2.2更改密码5第二章员工自助62.1功能概述62.2操作说明62.2.1查看信息62.2.2修改信息修改手机号码修改邮箱信息10第三章用户手册惯例及系统通用操作133.1系统概述133.2手册术语133.2.1操作约定133.2.2页面常见按钮/图标解释14文档控制15用户手册惯例及系统通用操作系统连接与访问方式客户端和浏览器要求威高集团安装的PeopleSoft系统是当前最新版本——PeopleSoft 9.2。新版本中除了增加和完善部分新功能之外，在视觉美观方面也大大增强。如欲获得最佳视觉体验，请使用较高版本的浏览器，如Internet Explorer 7.0或以上版本、Chrome28或以上版本、Mozilla Firefox 3.5或以上版本。网络要求网络方面，根据威高集团人力资源部要求，PeopleSoft系统能够通过外网及内网访问。访问地址如下：外网：1:8070/内网：2/ 单点登录员工可通过云办公快捷路径登录Peoplesoft系统，访问方式如下图所示：用户登录与更改密码用户登录[操作步骤]：【打开地址】打开浏览器，在地址栏输入PeopleSoft系统登陆地址，打开页面；或者通过云办公e-HR平台链接进入；【输入用户】输入“用户ID”和“密码”；【登录】点击“登录”按钮进行登录。【提示】1、系统用户名和密码区分大小写；2、登录系统之后，用户看到的界面上的菜单因用户的权限不同而存在差异。用户仅可以查看和使用职责权限范围内的菜单。3、用户首次登陆之后，浏览器一般会自动记住用户登录时选择的登录语言和用户名，用户下次打开登陆界面时，输入密码即可。4、威高集团员工登录系统，用户名均为员工工号，密码初始化时为员工身份证号码后6位，包含字母。首次登陆系统后，请及时修改密码。更改密码[操作步骤]：【打开菜单】 用户登录系统之后，在界面左侧的菜单列表下方可见“更改密码”菜单，点击菜单，进入修改密码页面； 【修改密码】在“更改密码”页面输入当前密码和新密码；新密码规则参照备注。【确认修改】点击“更改密码”按钮确认修改，系统显示“密码已保存”提示，表示密码修改成功。员工自助功能概述员工可通过员工自助服务的功能，实现自助查看个人基本信息、教育经历信息、培训信息等人事信息以及个人薪资单，并且支持员工进行个人电话、邮箱等信息的修改。操作说明查看信息[系统路径]：主菜单&自助服务&个人信息&员工自助（或者通过下图中主页快捷链接进入）[操作步骤]：[查看人事信息]：按照系统路径，或者点击主页，直接进入查看个人人事信息页面，如下图：点击进入之后，首先可以看到的是个人“基本信息”，教育经历信息、培训信息、工作经历信息、合同信息、联系人信息等呈现折叠状态，如需查看可点击每类信息前的，即可展开相应的信息：[查看薪资单信息]：点击“薪资单”，点击“开始期间”和“结束期间”框后的放大镜，选择“开始期间”和“结束期间”，点击“搜索”按钮，即可查看相应期间内的薪资单；备注：薪资单：系统支持查看从2015年12月至今的工资单；日历组：员工可通过日历组ID判断当前薪资单为月度工资、奖金还是节日费；应发合计：应发合计=基本工资+奖金+津贴+加班假期工资+补发补扣等其他薪资项－劳动者因个人原因缺勤或旷工造成的工资或者奖金减少的部分；修改信息目前支持人事信息中手机号码和电子邮件的修改。修改手机号码[系统路径]：主菜单&自助服务&个人信息&员工自助[操作步骤]： [进入修改页面]：按照系统路径，点击“手机号码”前的，进入手机号码修改页面[修改信息]： 在电话信息栏输入修改之后的个人电话。[保存]：修改之后点击。[返回自助界面]：点击路径的员工自助，返回至员工自助界面。修改邮箱信息[系统路径]：主菜单&自助服务&个人信息&员工自助[操作步骤]： [进入修改页面]：按照系统路径，点击“电子邮件”前的，进入电子邮件修改页面[修改电子邮件]：修改公司邮箱栏中的电子邮件地址。[保存]：修改之后点击。[返回自助界面]：点击路径的员工自助，返回至员工自助界面。用户手册惯例及系统通用操作系统概述威高集团人力资源管理信息系统平台为PeopleSoft HCM系统。本操作手册用于描述威高集团各级人力资源管理部门未来处理日常人事业务的系统操作。本文档及培训过程中提及的PeopleSoft HCM系统、PeopleSoft系统、PS系统、HR系统，
正在加载中，请稍后...
23页32页35页52页106页97页16页12页12页12页PeopleSoft系统日常维护手册_百度文库
两大类热门资源免费畅读
续费一年阅读会员，立省24元！
PeopleSoft系统日常维护手册
阅读已结束，下载文档到电脑
想免费下载本文？
定制HR最喜欢的简历
下载文档到电脑，方便使用
还剩14页未读，继续阅读
定制HR最喜欢的简历
你可能喜欢下次自动登录
现在的位置:
& 综合 & 正文
PeopleSoft Architecture && Overview
PeopleSoft 登录过程详解
Oracle 数据库角色
The PeopleSoft Internet Architecture (PIA) is a server-centric component architecture that enables secure end user access to PeopleSoft applications. Its components include the following:
o Internet Access Device
o Web Server
o Application Server
o Database Server
Each component fulfills a unique niche within the system, all of which are described in the PeopleSoft Internet Architecture Components lesson of this course.
With PIA there is no "traditional" client. Workstations simply need to have a supported browser installed. No other applets or connectivity software is needed on the workstation that runs the browser because all processing occurs
at the server level. Dynamic HTML, rendered by the Application Server, is passed to the Web Server and sent on to a supported browser interface.
PeopleSoft Integration Technologies:
oApplication Messaging - System-to-system communication.
oComponent Interfaces - Transactions from external systems to PeopleSoft. oApplication Engine - Used in batch application processing.
oFile Layouts - Used for integration with legacy systems.
PIA supports pure internet access for all PeopleSoft applications. It enables you to take advantage of all of the PeopleSoft intranet and internet solutions, as
well as the PeopleSoft Integration Technologies, such as Application Messaging.
These technologies streamline integration of PeopleSoft applications with other PeopleSoft applications, custom internal systems, eMerchants, and customer trading partner systems. By supporting the open flow of information between
systems, the PeopleSoft Integration Technologies provide true internet- based system integration.
The PeopleSoft Internet Architecture delivers intuitive, high-performance, HTML-based thin client applications that run on any machine with internet access. PIA deploys all transactions through a web browser.
Benefits of Browser-Based Deployment
oMinimizes the Training Effort
oReduces Application Deployment Costs
oLowers Client Hardware Requirements
oAllows Extensive Portability
There are two basic access methods with the PeopleSoft Internet Architecture:
(1) Directly, through a delivered homepage dedicated only to PeopleSoft applications, or
(2) Through a portal that may contain non-PeopleSoft content references. Both of these deployment options are further discussed in the PeopleSoft Development and Deployment lesson of this course. Both options provide the benefits listed above of browser-based
deployment.
Minimizes the Training Effort:
o Simple access
o Intuitive web look and feel
Less training is needed because most people with access to computers are very familiar with the look and feel of web pages, and know how to navigate within web browsers like Yahoo! . End users just click a hyperlink
to enter the PeopleSoft applications.
Reduces Application Deployment Costs:
o HTML-based for low bandwidth access
o HTML and JavaScript deployed to the browser
o No client installations required
Browser-based applications are easily deployed to end users. By placing a hyperlink in an email or on a corporate website, users can access the applications just like they access any other website. The cost of deploying browser-based
applications is close to zero.
Lowers Client Hardware Requirements:
o Robust, scalable server-centric architecture
o Supports thousands of concurrent users
Because the browser-based applications put very small demands on the client machine, the end user does not need a high-end, expensive computer to use PeopleSoft applications. This means lower costs to customers, as they will not need
to upgrade their client machines in order to use the latest PeopleSoft release.
Allows Extensive Portability:
o Web browser independence
o Client operation system independence
HTML browser-based applications are very portable across client operating systems. As long as the end user has a currently supported browser that is JavaScript 1.1 compliant, access to PeopleSoft applications can be through a Windows,
Mac, Linux, or Unix client machine. From an end user's perspective, browser-based application deployment of PeopleSoft applications is cost-effective and easy to use.
Because PIA is completely server-based, client machines to this architecture can be nearly any kind of internet-enabled device, including:
o Web browser running on a PC or Macintosh
o Wireless device or cell phone
o External or third-party system
These devices use the standard internet technologies: HTTP, HTML, WML, and XML.
A web browser running on a workstation (client) using the HTTP protocol is the most common internet access. The browser does not download any applets nor does it require any plug-ins. Rather, a servlet installed on the Web Server
facilitates all browser connections to the Application Server through JOLT.
When the browser sends a request to the Web Server, it is forwarded to the Application Server. The Application Server sends only the following back to the browser:
o JavaScript
The client workstation is free of any processing responsibility because there are no PeopleSoft executables on the client. This is why PeopleSoft Internet Architecture is termed an "architecture without a client."
With PeopleSoft Internet Architecture, only a single sign-in is needed between PeopleSoft databases. This is possible by leveraging Web Browser cookies that store a unique access token for users when they are initially authenticated.
The token in the browser cookie is used to re-authenticate users when they connect to other PeopleSoft systems. This way, a user does not have to go through the sign-in process again. The browser cookie is stored in memory and never written to disk. It is
encrypted by the Web Server and check-summed to prevent snooping and tampering.
As you can see, there is no "traditional" client involved in PeopleSoft Internet Architecture. The system sends pure HTML to a supported browser interface, while all processing occurs at the server level.
The Web Server must be Java-enabled so that it can run the PeopleSoft-delivered Java Servlets that are installed as part of PeopleSoft Internet Architecture. One of these is the Portal Servlet, which relays all inbound and outbound transaction requests for
the browser.
Using JOLT, the Web Server communicates browser requests to the Application Server. The pure HTML that the Application Server generates is formatted and presented in the browser by the Portal Servlet.
Together the Web Server and the Application Server make up the middle-tier of PIA; however, the Application Server does most of the work.
The Application Server is the core of PeopleSoft Internet Architecture. It handles messages from the Web Server through JOLT and executes all PeopleSoft business logic. In addition, it maintains the SQL connection to the Database
Server for both browser requests and for the PeopleSoft development environment. PeopleSoft uses TUXEDO to manage database transactions.
At execution time, the Application Server fetches the most recent application definitions from the Metadata Repository of the Database Server. The Application Server caches the definitions in memory and executes the business rules, based on the definitions.
Definitions such as pages, are created using the Application Designer tool in the PeopleSoft 8 development environment.
The Application Server consists of numerous PeopleSoft services and server processes that handle transaction requests. One of these server processes, PSAPPSRV, performs all application processing for a PeopleSoft internet session
and generates the HTML to be displayed in the browser. For example, it is the PSAPPSRV process of the Application Server that builds and loads the pages which are then transmitted to the browser, as requested, through the Web Server.
As you can see, the Application Server is truly the heart of PeopleSoft Internet Architecture.
Just as in the PeopleSoft three-tier architecture, with the PeopleSoft 8 Internet Architecture, information is stored on the Database Server in three types of tables: System Catalog Tables, PeopleTools Tables, and PeopleSoft Application
Data Tables. Each table type contains specific information that is related to running PeopleSoft applications.
The PeopleSoft database is the repository for all information that is managed by PeopleSoft applications. Not only is application data stored in the database, but the PeopleSoft metadata is also maintained in the database. Metadata is what drives PeopleSoft
Internet Architecture. Because PeopleSoft architectures have always been metadata-driven, PeopleSoft has been able to make the leap from client/server to internet-based applications without having to completely rewrite existing applications.
Several internet-related definitions were enhanced in PeopleTools 8.4 to enable full internet application development. These are the HTML Catalog, images, and style sheets. Just like fields, records, pages, menus, and other definitions,
these definitions are stored in the PeopleTools Tables of the Database Server, and are fully upgradeable.
Multiple Application Servers can be connected to a single Database Server, which simultaneously handles the Application Server connections and development environment connections.
PeopleSoft 8 Development Environment Features
oUses PeopleTools (Application Designer)
oBuilds on core competencies
oProvides full upgrade support
oLeverages the power and flexibility of:
- PeopleCode
- Workflow
- Application Messaging
- Application Engine
- Component Interfaces
oExpands on application developers' existing development skills
oLeverages the metadata repository
One of the best features of the PeopleSoft 8 Internet Architecture is that it continues to use Application Designer to develop and upgrade applications. Developers can quickly build, deploy, and support internet applications with
the look and feel of easy-to-use websites, with tools that are already familiar to them.
With PeopleTools 8.4, the development environment is Windows-based. Therefore, although the majority of end users connect to PeopleSoft 8 by using their browser, application developers and system administrators needing access to PeopleTools
will continue to use Windows workstations. When working in the PeopleSoft 8 development environment, connections to the database can be made directly, or indirectly through the Application Server.
PeopleSoft Development Functions
oApplication Development. The PeopleTools 8 development environment continues to use the Application Designer tool.
oQuery Design. Queries are designed in the PeopleTools 8 development environment, while end users execute queries through browser-based applications.
oCrystal Report Design. Some aspects of Crystal must be handled through Windows.
oTree Design. Tree design and modification are done through the Windows-based Tree Manager, while end users are able to view Tree definitions from a web browser.
onVision Report Design. With PeopleTools 8.4, the reporting tools listed above can also be used for development via the web. This list specifies objects that can be viewed or executed from a web browser.
To enable full internet application development, PeopleSoft 8 includes three definitions that are maintained in Application Designer. These definitions are related to web page design. These include: HTML stored in the PeopleSoft HTML
Catalog, images, and style sheets.
The HTML Catalog gives you flexibility in designing internet applications. HTML definitions are created and modified using the Application Designer tool, then stored in the HTML Catalog in the database. There are two ways in which
HTML is placed on a web page. HTML definitions may be called from the HTML Catalog to dynamically assemble a page, or HTML areas may be placed on a page along with traditional PeopleSoft page controls such as radio buttons and drop-down lists.
Images are important to all internet applications. They are used to improve the look and usability experience for the end user in virtually every web page on the internet. Because images are so important to internet applications,
PeopleSoft 8 provides the ability to store them in the PeopleSoft database. Images are used in application designs just like records, fields, pages, and other PeopleSoft definitions. And, just like those definitions, images can be upgraded.
Images are primarily used fo however, they can also demonstrate a simple function, such as an arrow on a push button, or when referenced on a hyperlink. Two of the most commonly used images, image definitions
and image fields can be referenced on a PeopleSoft page. Image definitions (JPG, GIF, and others) are stored as definitions in the PeopleTools Tables on the database and can be upgraded. Image Fields are stored in record fields and are only displayed at run
time through PeopleSoft Internet Architecture.
A default cascading style sheet is delivered with every PeopleSoft 8 application. Style sheets are used to build web pages. They offer a consistent set of GUI attributes that can be applied across multiple application pages. Designing web pages using style
sheets provides a consistent look and feel to any application accessed by users through internet browsers. The PeopleSoft-delivered style sheet may be copied then customized, or completely new style sheets can be developed. All of these are stored as definitions
in the PeopleTools Tables of the database.
These are just a few of the design features of the PIA development environment. In addition to applying these definitions to application pages, many existing definitions - such as push buttons - can be converted for web page functionality
by using the Application Designer tool.
PIA provides end users with direct access to PeopleSoft applications through a homepage like the one above. Each PeopleSoft 8 product is delivered with a homepage that provides basic portal-driven navigation and search key capability.
Users can search, use hyperlinks, use favorites, and navigate to numerous PeopleSoft applications with a single sign-in.
PeopleSoft applications can also be deployed using portal technology. All PeopleSoft 8 applications are delivered portal-enabled and can run through a browser inside any portal. However, PeopleSoft 8 offers four customizable portal
solutions. The Enterprise Portal platform sits on top of PIA and provides built-in security, a personalized homepage, and pagelets for accessing information such as company news and events. Resources from across the enterprise can be integrated into the portal.
PeopleSoft applications are only part of the Enterprise Portal. Enterprise Portals enable end users to handle information coming from various resources throughout the extended enterprise. In addition to PeopleSoft, users can access
email, business applications, stock quotes, and other internet content all woven together to provide a seamless integration point.
The Enterprise Portal platform provides you with the infrastructure required to create, maintain, and upgrade your own enterprise portal. The Enterprise Portal dramatically expands on the basic portal functionality that is part of the PeopleTools technology.
In addition to the Enterprise Portal, five prebuilt portal solutions are available. Each of these portal solutions snap into the Enterprise Portal foundation and provide out-of-the-box integration with all PeopleSoft applications.
Each of the five prebuilt portal solutions was built to manage role-based access for a specific audience as listed below:
o Customer Solution: Customers and prospects
o Employee Solution: Contractors, temps, and employees
o Supplier Solution: Extended partnerships and supply chain
o Campus Solution: Students, faculty, staff, and alumni
o CFO Solution: Business and finance managers
PeopleSoft Portal Solutions:
oEmployee Portal. A comprehensive solution that provides all needed enterprise content to employees, including prebuilt business process integration.
oSupplier Portal. Created to improve buy-side eCommerce and enable a company's suppliers to interoperate more effectively with the organization.
oCustomer Portal. Created to help build stronger customer relationships and improve sell-side eCommerce performance.
oCFO Solution. Enables business and finance managers to predict, measure, and manage business more effectively. They can track key performance areas and stay informed of the progress towards achieving corporate goals.
oCampus Solution. An ad-free webtop where students can register for classes, faculty can post grades, staff can check to-do lists, and alumni can sign up for events. By combining PeopleSoft Enterprise Portal with the appropriate Portal Pack, a website can be
created that delivers anytime, anywhere information tailored to the individual requirements of constituents.
The list above summarizes the purpose of each of the three prebuilt portal solutions.
This is an example of the Employee Portal product. Navigation pagelets provide users quick access to both PeopleSoft and non-PeopleSoft transactions. These pagelets are built using information architecture that provides navigation,
search, and taxonomy features to organize and logically display information for easy retrieval. Navigation pagelets, such as the Quick Navigation pagelet above, dynamically build a menu for role- based access to PeopleSoft applications.
PeopleSoft Portal Benefits:
oPeopleSoft portals are a natural extension of eBusiness solutions for customers, employees, and suppliers.
oPrebuilt portal solutions are fully integrated with all PeopleSoft eBusiness applications.
oThe PeopleSoft Enterprise Portal is a feature-rich portal that can be used with or without other PeopleSoft products.
oPrebuilt portal solutions dramatically lower customer implementation costs by providing out-of-the-box PeopleSoft integration.
当PeopleSoft Windows客户端进程（如Application Designer）进行三层连接的时候，会连接到应用服务器，每个应用服务器进程在启动的时候就与数据库之间建立了一个两层的连接。PIA通常指代第四层。浏览器连接到Servlet，Servlet再连接到应用服务器。任何想要连接到数据库的进程必须通过PeopleSoft用户或者Operator ID识别自身。登录过程的目的是安全的验证PeopleSoft
operator（已通过密码验证）能够访问PeopleSoft数据库。当一个PeopleSoft Windows客户端进程启动的时候，会出现一个登录对话框，如下图所示：
如果以如下的命令方式启动登录过程的话，可以抑制登录会话框的出现：
pside.exe -ct Oracle -cd HRDMOVM -co PS -cp PS
为了更好的看到PeopleTools程序与数据库建立两层连接的实际过程，下面一步步的展示进程的PeopleSoft trace。
一、进行初始连接
与7.5x相比较，PeopleTools 8 中第一次连接到数据库的特征发生了变化。从版本8开始，不管PeopleSoft操作者是谁，所有的PeopleSoft进程都连接到同一个低安全性的数据库用户，即Connect ID.
对于Windows客户端程序，各种各样的设置，包括Connect ID的用户名和密码，都在配置管理器中进行设置，如下图。数据库名和用户ID设置Windows客户端登录窗口中的默认值。这个工具也会加密Connect ID的密码。
配置管理器本质上是一个在客户端设置注册值的工具，如下图：
Windows客户端进程，如Application Designer会读取这些注册表值。
如果所有的PeopleSoft数据库不使用相同的Connect
ID和密码，客户端进程（主要是指Application Designer）就不能够在不改变这些注册值的情况下以两层模式连接到所有的数据库。尤其是不能够直接在数据库之间迁移Application Designer项目，因为Application Designer必须以两层模式登录到两个数据库，它会尝试使用同一个Connect ID登录到两个数据库。这个问题的解决办法就是将项目从源数据库导出到一个flat文件中，然后将该文件导入到目标数据库。
配置管理器也可以用于安装和卸载Windows开始菜单中的快捷键、ODBC驱动以及本地的PeopleTools可执行文件。
运行在Windows服务器中的应用服务器进程和进程调度器进程不使用注册表中的值。它们所有的设置都从配置文件中读取，在其他操作系统中也一样。
PeopleSoft应用服务器进程、COBOL程序以及AE进程执行相似的登录步骤。它们详细的连接信息不是保存在应用服务器配置文件psappsrv.cfg中，就是保存在进程调度器配置文件psprcs.cfg中。如下所示：
以下内容截取自psprcs.cfg
以下内容截取自psprcs.cfg
;=========================================================================
;=========================================================================
; Database Signon settings
;=========================================================================
DBName=HRDMOVM
DBType=ORACLE
UserId=APPUSER
UserPswd=APPUSER
ConnectId=people
ConnectPswd=peop1e
ServerName=
StandbyDBName=
StandbyDBType=
StandbyUserId=
StandbyUserPswd=
; Database Signon settings
;=========================================================================
DBName=HRDMOVM
DBType=ORACLE
UserId=APPUSER
UserPswd=APPUSER
ConnectId=people
ConnectPswd=peop1e
ServerName=
StandbyDBName=
StandbyDBType=
StandbyUserId=
StandbyUserPswd=
PeopleTools 客户端trace可以显示登录过程中执行的所有的SQL操作，如下所示：
Trace Data...
----------
--------------------&
Tuxedo session opened {oprid='PS', appname='TwoTier',addr='//TwoTier:7000', open at 057C00D0, pid=1064}
Cur#0.1064.HCM91 RC=0 Dur=2.267000 Create Connection Info=Primary/HCM91/people/ Handle=057E7BC8
任何PeopleSoft进程的第一个操作就是以ConnectPswd连接到ConnectId，如上面加粗的部分所示。
对于Oracle，SQL*NET连接字符串是people/peop1e@HCM91（trace中没有显示密码）。连接字符串中的TNS服务名HCM91来自登录会话框中输入的PeopleSoft数据库名字。如果一个Oracle数据包含多个PeopleSoft数据库，每个PeopleSoft数据库名字必须有一个TNS服务名对应，而且所有的TNS服务名必须指向同一个Oracle 连接字符串.
TNS服务名也必须存在于默认的SQL*Net域中，因为PeopleSoft不会在连接字符串中指定任何域。在如下的例子中，一个Oracle数据库包含两个PeopleSoft数据库，因此有两个TNS服务名。
HCM91, HCM91_Q =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = HCM91)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = hcm91)
HCM91, HCM91_Q =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = TCP)(HOST = HCM91)(PORT = 1521))
(CONNECT_DATA =
(SERVICE_NAME = hcm91)
其中SERVICE_NAME指代Oracle SID，即Oracle数据库实例。
二、直接使用内存共享连接（UseLocalOracleDB）
当SQL*Net客户端进程和数据库位于同一个物理服务器上时，该进程可以通过共享内存直接连接到数据库，而不用使用Oracle监听器或者任何其他网络协议。这种方法会提供更好的性能，消耗更少的CPU时间。
通过共享内存进行的连接有时也叫作IPC（Interprocess Communication）连接。因为在Unix上，连接使用IPC资源，而且在SQL*Net配置文件中指定了IPC协议。早期的Oracle版本中，IPC协议叫作bequeath协议。
如果在连接字符串中没有将TNS服务名附加到用户名和密码之后，SQL*Net就进行共享内存连接。数据库实例通过ORACLE_SID环境变量指定。
如果应用服务器配置文件中的UseLocalOracleDB选项设置为1，如下所示：
以下内容截取自psappsrv.cfg
以下内容截取自psappsrv.cfg
[Database Options]
;=========================================================================
; Database-specific configuration options
;=========================================================================
SybasePacketSize=
UseLocalOracleDB=1
ORACLE_SID=HCM91
EnableDBMonitoring=1
PSDB Maximum Cursors=
[Database Options]
;=========================================================================
; Database-specific configuration options
;=========================================================================
SybasePacketSize=
UseLocalOracleDB=1
ORACLE_SID=HCM91
EnableDBMonitoring=1
PSDB Maximum Cursors=
此时SQL*Net连接字符串就简单的只是用户名和密码了。PeopleSoft不会附加上TNS服务名，也不会使用tnsnames.ora文件了。
进程调度器用于启动批处理和报表进程，也可以像上面一样进行配置。在这种情况下，进程调度器以及其产生的COBOL或AE进程也进行直接内存共享连接。
实际上，应用服务器或者进程调度器与数据库共存在于一个服务器上的情况很少见了。一个非常合理的理由就是Oracle数据库许可授权通常基于数据库服务器上的CPU数目，即CPU数目越多，Oracle数据库软件许可证的价格就越高。如果数据库服务器也运行了PeopleSoft中间件，那么PeopleSoft中间件也会消耗你购买的用于数据库许可的CPU。
考虑到性能，PeopleSoft建议将UseLocalOracleDB设置成1。这种方式下，连接到数据库不需要Oracle监听器，因此这种数据库连接应该比使用IPC key稍快。然而对于整体响应时间的比例而言，收效甚微。设置UseLocalOracleDB=1也会使应用服务器和进程调度器对ORACLE_SID环境变量的值比较敏感，虽然ORACLE_SID也可以在配置文件中进行设置。
然而，我建议保持UseLocalOracleDB=0的设置，然后在tnsname.ora文件中指定一个IPC key，如下所示：
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = ORA11gR2))
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = HRDMOVM)(PORT = 1521))
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = ORA11gR2))
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = HRDMOVM)(PORT = 1521))
这种情况下，所有运行在数据库服务器上的SQL*Net客户端都进行IPC连接。‘
如果一个连接到数据库的客户端进程偶然终止了，而没有从数据库服务器断掉，特别是当等待数据库的响应时，Oracle影子进程还是会继续运行。当PSAPPSRV或PSQRYSRV进程终止或者因等待一个长时间运行的SQL查询返回结果而超过了Tuxedo服务超时时间，就会出现这种情况。也可以在PeopleSoft操作者安全概要中设置查询超时时间。PeopleSoft不会清理数据库会话所持有的资源，因此在sqlnet.ora文件中应该总是设置SQLNET.EXPIRE_TIME以启用Oracle Terminated
Connection Timeout。这项机制可以清理掉断掉的shadow process。
下面是SQLNET.EXPIRE_TIME的说明：
#sqlnet.expire_time = 10
########################
#Possible values: 0-any valid positive integer! (in minutes)
#Default: 0 minutes
#Recommended value: 10 minutes
#Purpose: Indicates the time interval to send a probe to verify the
client session is alive (this is used to reclaim watseful
resources on a dead client)
#sqlnet.expire_time = 10
########################
#Possible values: 0-any valid positive integer! (in minutes)
#Default: 0 minutes
#Recommended value: 10 minutes
#Purpose: Indicates the time interval to send a probe to verify the
client session is alive (this is used to reclaim watseful
resources on a dead client)
三、获取Owner ID
连接到了Oracle数据库之后，登录进程的第一项任务就是判断哪个数据库schema包含PeopleSoft数据库。下面的几行PeopleTools客户端trace展示了PSDBOWNER表是如何将数据库映射到schema上的。
1-4 09.51.33 0.000000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 COM Stmt=SELECT&span style="color: rgb(255, 0, 0);"& OWNERID&/span& FROM PS.PSDBOWNER WHERE DBNAME=:1
1-5 09.51.33 0.000000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 Bind-1 type=2 length=5 value=&span style="color: rgb(255, 0, 0);"&HCM91&/span&
1-4 09.51.33 0.000000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 COM Stmt=SELECT OWNERID FROM PS.PSDBOWNER WHERE DBNAME=:1
1-5 09.51.33 0.000000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 Bind-1 type=2 length=5 value=HCM91
根据传入的DBNAME获取OWNERID。
包含PeopleSoft数据库的schema叫作Owner ID。直到成功登录，登录程序明确的引用了该schema中的三个对象。因此在安装过程中，SELECT权限被明确的通过Data Mover脚本赋予给了这三张表，如下所示：
GRANT SELECT ON PSSTATUS TO PEOPLE;
GRANT SELECT ON PSOPRDEFN TO PEOPLE;
GRANT SELECT ON PSACCESSPRFL TO PEOPLE;
GRANT SELECT ON PSSTATUS TO PEOPLE;
GRANT SELECT ON PSOPRDEFN TO PEOPLE;
GRANT SELECT ON PSACCESSPRFL TO PEOPLE;
安装程序本身是连接到了包含这几张的的schema上，所以在GRANT命令中没有指定schema名字。
PS.PSDBOWNER表允许PeopleSoft在一个Oracle或其他数据库中管理多个PeopleSoft数据库。该表包含一行数据，将PeopleSoft数据库的名字映射到其所属Oracle schema上。给同一个PeopleSoft数据库取两个名字也是可能的。可以在该表中添加一行数据，这两个数据库名字映射到同一个OWNERID即可。如下几种情况可能会用到这种特性：
如果正在变更一个PeopleSoft数据库的名字，在过渡期间，这两个名字都有效。
如果生产数据库被复制到一个只读的报表数据库中，你可能希望在不改变数据库的情况下查询该数据库。
不管使用哪种方式，对于每一个在PS.PSDBOWNER表中指定的数据库名称（DBNAME），在默认的SQL*Net 域中都必须有一个相应的TNS服务。所以可见PSDBOWNER表中的DBNAME并不是指代PeopleSoft数据库名称，而是指TNS服务名，PeopleSoft数据库还是得靠OWNERID说了算。PeopleSoft数据库名称只是逻辑上的一个概念，实际在Oracle数据库中就是一个schema下的一些表集合。一个OWNERID对应一个PeopleSoft数据库。
如果在PS.PSDBOWNER表中没有皮质TNS连接字符串的条目，就会提示”登录用户名或密码无效”。该错误实际上包含了登录过程中所有的错误，因此不要只限于检查用户ID和密码问题。
四、检查PeopleTools的版本
下一项任务就是保证登录程序当前所试图连接的PeopleSoft数据库的PeopleTools版本和客户端的相同。PeopleTools表结构在主要的PeopleTool发行版本（8.1到8.4）中总是在变化。从PeopleTools 8.x 开始，在小版本（如8.50到8.51）之间有些许结构上的变化。大小版本号记录在数据库表PSSTATUS.TOOLSREL列中：
PeopleTools客户端trace显示客户端从PSSTATUS表中查询PeopleTools版本：
1-6 09.51.33 0.001000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 COM Stmt=SELECT OWNERID,TOOLSREL, TO_CHAR(LASTREFRESHDTTM,'YYYY-MM-DD HH24:MI:SS'), TO_CHAR(LASTCHANGEDTTM,'YYYY-MM-DD
HH24:MI:SS') FROM SYSADM.PSSTATUS
1-7 09.51.33 0.001000 Cur#1.1064.HCM91 RC=0 Dur=0.001000 COM Stmt=SELECT DBID FROM SYSADM.PSSTATUS
1-6 09.51.33 0.001000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 COM Stmt=SELECT OWNERID,TOOLSREL, TO_CHAR(LASTREFRESHDTTM,'YYYY-MM-DD HH24:MI:SS'), TO_CHAR(LASTCHANGEDTTM,'YYYY-MM-DD
HH24:MI:SS') FROM SYSADM.PSSTATUS
1-7 09.51.33 0.001000 Cur#1.1064.HCM91 RC=0 Dur=0.001000 COM Stmt=SELECT DBID FROM SYSADM.PSSTATUS
注：DBID列是在8.46版本中引入的。
将PeopleTools从一个版本升级到另一个版本的过程中，有一步是运行一个PeopleSoft提供的“rel”脚本。该脚本（如下）重建那些结构发生了变化的表，以及更新TOOLSREL列中的PeopleTools版本号。
以下内容截取自rel851.sql
以下内容截取自rel851.sql
UPDATE PSSTATUS SET TOOLSREL='8.51',
LASTREFRESHDTTM = SYSDATE
UPDATE PSSTATUS SET TOOLSREL='8.51',
LASTREFRESHDTTM = SYSDATE
比较版本的操作不会针对PeopleTools补丁级别，即8.50任何补丁级别（如8.50.09）都能够成功的连接到数据。People不会在补丁发行版本中改变PeopleTools的结构。
如果在登录过程中版本号不比配，就会在客户端PC 上显示一个错误对话框（如下图）。该错误指示要么是安装过程出错，要么是使用了错误的可执行文件。
另外需要注意的是，在四层模式中，PIA servlet的版本必须精确匹配应用服务器的版本，否则也会连接失败。如8.50.09的servlet不能够链接到8.50.08的应用服务器。在三层模式中，Windows客户端程序同样如此，比如Application Designer或者nVision。
在应用服务器中，每个PeopleSoft应用服务器进程启动时都会执行PeopleTools版本测试。PeopleTools 8.43引入的PSWATCHSRV服务器进程例外。该进程会检测以及杀死已经成了了僵尸进程的服务器进程，而且这个进程根本不会连接数据库。
当应用服务器启动时，会将消息写到APPSRV.LOG文件中，如下：
截取自APPSRV_&MMDD&.LOG
截取自APPSRV_&MMDD&.LOG
PSAPPSRV.6812 (0) [09/06/12 10:20:12](0) PeopleTools Release 8.51 (WinX86) starting. Tuxedo
server is APPSRV(99)/2
PSAPPSRV.6812 (0) [09/06/12 10:29:12](1) GenMessageBox(0, 0, M): Security Table Manager (Get):
&span style="color: rgb(255, 0, 0);"&The database is at release 8.48. The PeopleTools being run require databases at release 8.51.&/span&
PSAPPSRV.6812 (0) [09/06/12 10:29:12](0) Server failed to start
PSAPPSRV.6812 (0) [09/06/12 10:20:12](0) PeopleTools Release 8.51 (WinX86) starting. Tuxedo
server is APPSRV(99)/2
PSAPPSRV.6812 (0) [09/06/12 10:29:12](1) GenMessageBox(0, 0, M): Security Table Manager (Get):
The database is at release 8.48. The PeopleTools being run require databases at release 8.51.
PSAPPSRV.6812 (0) [09/06/12 10:29:12](0) Server failed to start
五、检查Operator密码
下一步是检索存储在PSOPRDEFN表中PeopleSoft用户的加密密码。
1-8 09.51.33 0.000000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 COM Stmt=SELECT VERSION,OPERPSWD, ENCRYPTED, SYMBOLICID, ACCTLOCK FROM &span style="color: rgb(255, 0, 0);"&SYSADM.PSOPRDEFN&/span& WHERE OPRID = :1
1-9 09.51.33 0.000000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 Bind-1 type=2 length=2 value=PS
1-8 09.51.33 0.000000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 COM Stmt=SELECT VERSION,OPERPSWD, ENCRYPTED, SYMBOLICID, ACCTLOCK FROM SYSADM.PSOPRDEFN WHERE OPRID = :1
1-9 09.51.33 0.000000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 Bind-1 type=2 length=2 value=PS
下面显示检索后的结果：
SYMBOLICID
---------- ------------------------------ ---------- ------------------------ ----------
9qSGfTd2aRl/N+N4B7ZUz72qJe6=
SYMBOLICID
---------- ------------------------------ ---------- ------------------------ ----------
9qSGfTd2aRl/N+N4B7ZUz72qJe6=
检索出密码之后再验证用户输入的或者配置文件中设置的密码是否匹配。
六、获取访问密码
操作者的访问概要是从PSOPRDEFN.SYMBOLICID字段中获取的，用于在PSACCESSPRFL表中查找ACCESSID和ACCESSPSWD。
1-10 09.51.33 0.001000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 COM Stmt=SELECT ACCESSID,ACCESSPSWD, ENCRYPTED FROM SYSADM.PSACCESSPRFL WHERE SYMBOLICID = :1
1-11 09.51.33 0.000000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 Bind-1 type=2 length=7 value=SYSADM1
1-10 09.51.33 0.001000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 COM Stmt=SELECT ACCESSID,ACCESSPSWD, ENCRYPTED FROM SYSADM.PSACCESSPRFL WHERE SYMBOLICID = :1
1-11 09.51.33 0.000000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 Bind-1 type=2 length=7 value=SYSADM1
PSACCESSPRFL表在PeopleTools 7.5中就存在，但是在登录过程中不会检查该表，因为在PSOPRDEFN表中也存在加密的访问密码。在PeopleTools 8 中，访问密码只存在于PSACCESSPRFL中。
七、以Access ID身份重新连接数据库
找到了Access ID以及密码之后，登录进程从数据库断开，然后以Access ID账户登录到数据库。
1-12 09.51.33 0.001000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 Disconnect
1-13 09.51.33 0.002000 Cur#0.1064.notSamTran RC=0 Dur=0.002000 Destroy Connection Handle=057E7BC8
1-14 09.51.35 2.267000 Cur#0.1064.HCM91 RC=0 Dur=2.267000 Create Connection Info=Primary/HCM91/SYSADM/ Handle=057E7BC8
1-15 09.51.35 0.003000 Cur#1.1064.notSamTran RC=0 Dur=0.002000 Open Cursor Handle=057E7BC8
1-16 09.51.36 0.003000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 CEX Stmt=select pt_tde_encrypt_alg from psoptions
1-17 09.51.36 0.001000 TDE Encryption Algorithm: ''
1-18 09.51.36 0.000000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 COM Stmt=SELECT TO_CHAR(SYSTIMESTAMP,'YYYY-MM-DD-HH24.MI.SS.FF') FROM PSCLOCK
1-12 09.51.33 0.001000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 Disconnect
1-13 09.51.33 0.002000 Cur#0.1064.notSamTran RC=0 Dur=0.002000 Destroy Connection Handle=057E7BC8
1-14 09.51.35 2.267000 Cur#0.1064.HCM91 RC=0 Dur=2.267000 Create Connection Info=Primary/HCM91/SYSADM/ Handle=057E7BC8
1-15 09.51.35 0.003000 Cur#1.1064.notSamTran RC=0 Dur=0.002000 Open Cursor Handle=057E7BC8
1-16 09.51.36 0.003000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 CEX Stmt=select pt_tde_encrypt_alg from psoptions
1-17 09.51.36 0.001000 TDE Encryption Algorithm: ''
1-18 09.51.36 0.000000 Cur#1.1064.HCM91 RC=0 Dur=0.000000 COM Stmt=SELECT TO_CHAR(SYSTIMESTAMP,'YYYY-MM-DD-HH24.MI.SS.FF') FROM PSCLOCK
PeopleSoft应用会执行更多的检查操作，用于判断操作者是否被允许连接，以及在应用或者设计工具中判断他们能够执行操作的程度。但是在此处，登录进程进行到这里就已经完成了登录操作。
但是PeopleSoft的这一系列的登录过程会使如下几种操作变得困难：
判断哪一SQL片段属于哪一个用户
使用Oracle资源管理器或者资源概要为不同的用户类型设置不同的资源利用阈值
从PeopleTools 7.53 开始，PeopleSoft使用DBMS_APPLICATION_INFO包帮助辨别用户的会话。
需要注意的是：Access ID的名称不是来自PS.PSDBOWNER.OWNERID字段，而是来自PSACCESSPRFL.ACCESS_ID字段。
在PeopleSoft数据库安装的过程中，会创建两个数据库角色PSUSER和PSADMIN，如下面的脚本所示：
以下内容截取自psroles.sql：
set echo on
spool psroles.log
DROP ROLE PSUSER;
DROP ROLE PSADMIN;
CREATE ROLE PSUSER;
GRANT CREATE SESSION
TO PSUSER;
CREATE ROLE PSADMIN;
ANALYZE ANY,
CREATE SESSION, ALTER SESSION,
CREATE TABLESPACE, DROP TABLESPACE,
CREATE ANY
TABLE, ALTER
ANY TABLE,
SELECT ANY
INSERT ANY
TABLE, UPDATE
ANY TABLE, COMMENT
ANY TABLE,
CREATE ANY
PROCEDURE, ALTER
ANY PROCEDURE,
EXECUTE ANY
PROCEDURE, DROP
ANY PROCEDURE,
CREATE ANY
INDEX, DROP
ANY INDEX,
CREATE ANY INDEXTYPE,
DROP ANY INDEXTYPE,
&&&&推荐文章:
【上篇】【下篇】