General Discussion (new posts) http://www.peoplesoftwiki.com/forum/c-84391/general-discussion Posts in the forum category "General Discussion" - Something about PeopleSoft you want to start a discussion about? Fri, 30 Jul 2010 05:12:27 +0000 http://www.peoplesoftwiki.com/forum/t-213028#post-680087 PeopleSoft Internet Architecture Diagram: PeopleSoft Internet Architecture Diagram http://www.peoplesoftwiki.com/forum/t-213028/peoplesoft-internet-architecture-diagram#post-680087 Wed, 20 Jan 2010 23:42:08 +0000 Praj 52320 Derek Tomei's blog, A Day in the Life of a PeopleSoft Professional contains a link to a PDF PeopleSoft Internet Architecture Diagram. Thanks Derek, very handy.

]]> http://www.peoplesoftwiki.com/forum/t-192567#post-620349 Debugging / Tracing XML Publisher: Debugging / Tracing XML Publisher http://www.peoplesoftwiki.com/forum/t-192567/debugging-tracing-xml-publisher#post-620349 Thu, 29 Oct 2009 21:58:33 +0000 Praj 52320 Didn't realise XML publisher had a debugging / tracing option, but this great post by PeopleSoft / Oracle tips goes through how to turn it on.

I tested this on a unix system, and set the log path to a folder I created: $PS_HOME/log/XMLP. Note that the LogDir doesn't like environment variables, e.g. I had to hard code the path to $PS_HOME and it will throw an error if you specify a location it can't write to.

]]> http://www.peoplesoftwiki.com/forum/t-192344#post-619617 Using Oracle Database Links: Using Oracle Database Links http://www.peoplesoftwiki.com/forum/t-192344/using-oracle-database-links#post-619617 Wed, 28 Oct 2009 22:14:53 +0000 Praj 52320 The PeopleSoft DBA Blog has a great article that explains good and bad uses of Oracle database links. Definitely worth a read if you use them at your organisation. As pointed out, potential alternatives include using application messaging or materialized views. Like most things, they can work very well if used in the right way.

]]> http://www.peoplesoftwiki.com/forum/t-188724#post-608947 Print Project Alternative for PeopleCode: Print Project Alternative for PeopleCode http://www.peoplesoftwiki.com/forum/t-188724/print-project-alternative-for-peoplecode#post-608947 Wed, 14 Oct 2009 23:38:07 +0000 Praj 52320 A work colleague put me onto this great tip for modifying the XML in your exported project definition so that you can view PeopleCode in a better format.

A couple of catches:

  • Once you format the project XML it is no longer valid for re-import. So make a copy of it when doing this.
  • You need an additional file PeopleCodeViewer.xsl to exist in the same directory as your edited project XML. The source for this file is on the site, but doesn't work with a straight copy and paste so, here's a formatted version of it (note all credit goes to the original site for this code)
  • Simply open your edited project XML file in a browser to see the formatted results.
 <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform"> <xsl:template match="/root"> <html> <header> <xsl:variable name="project" select="instance[@class='PJM']" /> <h1> Project: <xsl:value-of select="$project/rowset/row/szProjectName" /> </h1> <h3> Description: <xsl:value-of select="$project/rowset/row/szProjectDescr" /> </h3> </header> <body> <xsl:for-each select="instance[@class='PCM']"> <table> <tr> <td> <h5> <xsl:value-of select="rowset/row/szObjectValue_0" />: <xsl:value-of select="rowset/row/szObjectValue_1" />: <xsl:value-of select="rowset/row/szObjectValue_2" />: <xsl:value-of select="rowset/row/szObjectValue_3" />: <xsl:value-of select="rowset/row/szObjectValue_4" /> </h5> </td> </tr> <tr> <td> <pre> <xsl:value-of select="peoplecode_text" /> </pre> </td> </tr> </table> </xsl:for-each> </body> </html> </xsl:template> </xsl:stylesheet>
]]> http://www.peoplesoftwiki.com/forum/t-157492#post-486726 Development Flow: Development Flow http://www.peoplesoftwiki.com/forum/t-157492/development-flow#post-486726 Fri, 22 May 2009 01:47:44 +0000 Praj 52320 I'm using the term development flow to refer to the way in which you develop in PeopleSoft.

A typical approach is something like this:

  1. Develop in your master development environment
  2. Migrate to your development testing environment
  3. Test in your development testing environment

For basic development, this approach works fine. However, I find that for more complex development, I like this approach better:

  1. Prototype in a prototype/sandbox development environment.
  2. Once you are happy with your prototype and have performed some basic tests, recreate (do not migrate) the changes in your master development environment.
  3. Migrate to your development testing environment
  4. Test in your development testing environment

The prototype first approach works really well when you aren't sure what your final solution will look like and you need to feel your way towards it. It does however require three development environments instead of two.

Everyone is different, but I figure it's useful to know how different people work. If you have a different approach or suggestion, please comment.

]]>