如何配置 PeopleSoft 测试环境？
您在测试环境中更改了哪些项目以使它们在生产中脱颖而出？您如何进行这些更改？ 我知道你可以改变PS LOGO，但是你在测试环境中还改变了什么？ 颜色、字体等
What are some the items you change in your test environments to make them standout from production, and how do you go about make these changes? I know you can change the PS LOGO, but what else do you change in your test environments? Colors, fonts, etc.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
改变配色方案并不是太困难。 如果您想走这条路并需要帮助，我将很乐意提供帮助。
其他客户端只需将环境名称放入 PIA 问候语中即可。 这也很容易：
http://peoplesofttipster.com/2007/06/13 /using-the-pia-welcome-message/
不过，我还没听说有人改变字体。
亲切的问候
邓肯
Changing the colour schemes isn't too difficult. If you want to go down that route and need a helping hand I'll be happy to assist.
Other clients just put the environment name in the PIA Greeting. That's easy too:
http://peoplesofttipster.com/2007/06/13/using-the-pia-welcome-message/
I've not heard of anyone changing fonts though.
kind regards
Duncan
刷新数据库时，请确保更改包含数据库名称、Web URL 等的工具表。 测试数据库名称将出现在门户菜单中。
更改字体需要更改所有样式表定义，这是一个非常令人头痛的问题。 我想您可以在应用程序设计器、PS_TEXT 等中编辑一些基本样式表属性。 并在测试环境中更改它们。 也许只改变一些就足够了。
大多数测试环境也在某种程度上开放了安全性，仅仅是因为测试人员和开发人员可能需要访问所有内容。 因此，人们的菜单将比生产时的菜单大得多。
When you refresh a db, make sure you change tools tables that have dbname, web urls, and so on. The test db name will appear in the portal menu.
Changing the fonts would require changing all the style sheet definitions, a major headache. I guess you could go in and edit some basic style sheet attributes in app designer, PS_TEXT, et.al. and change those in a test environment. Maybe just changing a few would be enough.
Most test envs also open up security to some degree, simply because testers and developers likely need access to everything. So people's menus are going to be much larger than in production.
这是我们所做的相对较小的更改，将工具栏中的“Home”链接替换为除 prod 之外的环境名称。 它还被合并到刷新脚本中以动态地提取 DBNAME。
update psmsgcatdefn set message_text = 'DBNAME', descrlong = '环境名称主目录替换' where message_set_nbr = '95' and message_nbr = '401';
This is the relatively small change we made, to replace the "Home" link in the toolbar with the name of the environment eveywhere but prod. It was also incorporated in the refresh scripts to pull in the DBNAME dyanmically.
update psmsgcatdefn set message_text = 'DBNAME', descrlong = 'Environment name home replacement' where message_set_nbr = '95' and message_nbr = '401';
需要注意的事项：
文件路径 - 如果您打开文件进行读取（尤其是写入）以与外部系统通信，那么您需要确保您没有踩到生产的脚趾。
我认为 Web 服务也需要相同的重新路由，这样您就不会“命中”实时外部生产 Web 服务。
我认为 Web 服务也需要相同的重新路由，这样您就不会“命中”实时外部生产 Web 服务
电子邮件。 工作流程或其他子系统可能会向用户或外部各方发送电子邮件。 您需要确保这些电子邮件是测试电子邮件，而不是真正的收件人。
items to watch for:
file paths - if you open files for reading, and especially writing, to communicate with external systems, then you need to make sure you are not stepping on Production toes.
I would assume web services would also need the same re-routing so you don't "hit" live external production web services.
emails. workflow or other subsystems are liable to fire off emails to users or external parties. you need to make sure those emails are tester emails instead, not real addressees.