I want to take services of Accounts

I want to take services of Accounts: "Please contact me for giving services of Accounts"

Read More

Check Physical memory on HP UNIX

grep -i Physical /var/adm/syslog/syslog.log

Read More

PeopleSoft SQR Flags

-ZIFD:\PSHOME\sqr\pssqr.ini
-iD:\PSHOME\sqr
-fc:\temp\setspace.lis

Read More

How Is SSL for LDAP Implemented on PeopleTools 8.50?

How Is SSL for LDAP Implemented on PeopleTools 8.50?

·         Prior to PeopleTools 8.50, LDAP over SSL dealt with the cert7.db or in  PT 8.48 & 8.49 depending on app server platform the Oracle Wallet Manager.  This db file contains the Trusted Root certificate of the Certificate Authority that issued the Server Certificate of the LDAP server and configure LDAP Business interlinks for SSL.

·         In 8.50, for LDAP over SSL, the cert7.db or Oracle Wallet is no longer needed as Java Naming and Directory Interface (JNDI) has replaced Oracle and Netscape libraries. JNDI is a Java API for a directory service that allows Java software clients to discover and look up data and objects via a name. Like all Java APIs that interface with host systems, JNDI is independent of the underlying implementation.

·         JNDI is delivered along with PeopleTools. There is no need of additional installations like in PT 8.48 & 8.49 the Oracle Client DB install required on UNIX, AIX, or LINUX platforms, or Netscape libraries required on Windows and Solaris.

·         Certificates are no longer needed in the appserver domain either. They are managed from database. The same certificates can be used across the platforms without any packaging. PeopleCode for LDAP transactions do not need to hold the path of the certificates.

How Things Work

·         The Root CA certificate has to be installed into the PeopleSoft database.

·         The server certificate has to be installed in the Directory server.

·         Since the certificates are managed in the database, SSL_DB parameter in the LDAP_SEARCH and LDAP_BIND Business Interlinks is not needed for the SSL transactions. However, changing the value of SSL_DB will not create any harm.

·         The certificates can be added to or deleted from this location: Main Menu > PeopleTools > Security > Security Objects > Digital certificates.

·         When a certificate is added or removed from the database, the appserver has to be bounced to see the effect.

·         Some Root CA certs are delivered out of the box. Care should be taken so that they do not create unexpected behavior.

·         It is not possible to use a certificate for specific SSL transactions. Once added, the certificate will be applicable for all SSL connections.

·         Though any name can be given to the Root CA certs, a meaningful name is recommended.

·         The JNDI will pick one certificate after the other until it finds a valid certificate. You cannot alter the order of the certificate processing.

·         When upgrading to PeopleTools 8.50, your certificates should be added to the Digital certificates page.

·         Since the certificates will be available in the database, the Business Interlink SSL_DB parameter in the LDAP BI transactions will not be of  any significance.

To Set Up SSL With Your Directory, the Following Steps Need To Be Done

(Extract from Peoplebooks)

Peoplebooks: Employing LDAP Directory Services

·         Adding your Root Certificate to the Digital Certificates

-          Navigate to PeopleTools > Security > Digital Certificates

§  The list of installed certificates appears.

§  Click the + (plus sign) button in the last row of the displayed certificates.

§  A blank row appears.

§  Select Root CA from the Type drop-down list box.

§  Enter a meaningful name as the alias of this certificate in the Alias field.

§  Click the Issuer Alias field prompt button.

§  The name of the Alias automatically populates the Issuer Alias field.

§  Click the Add Root link.

§  The Add Root Certificate page appears. Minimize the browser window.

§  Open the root CA certificate with a text editor and copy the contents.

§  Maximize the browser and paste the contents into the text box.

§  Click the OK button to see the new digital certificate.

§  Reboot the application server.

§  Select Test connectivity from Directory > Directory setup > "Test connectivity tab" to test.

Read More

COBOL SQL TRACING in PeopleSoft

COBOL SQL TRACING

INSTRUCTIONS

PART I – IDENTIFY THE TRACE SETTING

The trace setting that you choose to use will be determined by a single number that is the sum of the values corresponding to each option that you wish to include. These are the values for each of the options available to you:


1 = SQL Statements

2 = SQL statement variables

4 = SQL connect, disconnect, commit and rollback

8 = Row Fetch (indicates that it occurred, not data)

16 = All other API calls except SSBs

32 = Set Select Buffers (holds values of columns to be selected.

64 = Database API specific calls

128 = COBOL statement timings

256 = Sybase Bind information

512 = Sybase Fetch information



So if you only wanted to trace the SQL Statements, SQL Statement variables and Row Fetch, you would use 11 (1 + 2 + 8 = 11).



If your analyst provides you with a setting to use, use that setting.



If you do not know which setting to use, use 255.



PART II – PROCESS SCHEDULER TRACING



The easiest method for getting a cobol SQL trace of a process is to use the tracing options that are available to us when the job is run via the Process Scheduler. If the problem is occuring during a remote call (online) job only, and/or you cannot replicate the problem using the equivalent batch process, then you’ll need to go to PART III for App Server tracing instructions.



Step 1 – Identify the job that you will be tracing



Go to the Run Control Page of the job you wish to trace. In my case, I am going to trace a process called Student Refunds, and so I will go to that page. Once there, I will press the Run button one time:

This will take you to the page where you can then note the name of the process you are running:

Step 2 – Set the trace


Once you have this information, go to Peopletools, Process Scheduler, Process Types and find the default parameters for all Cobol SQL jobs using your platform. In my case, I will use the NT/Win2000 platform on an Oracle database:

Copy these default parameters to your clipboard (make sure you get the entire string in when you do the copy:

Now go to Peopletools, Process Scheduler, Processes, Override Options and find the job that you are tracing, which you did at the very beginning of this step. You can then change the Parameter list value to Override and paste the default options that you just copied to your clipboard into this parameter list field:

Now locate the pair of forward slashes between INSTANCE and DBFLAG in the parameter list and insert your trace setting in between these two slashes (in my case I am using 255:

Save the page, and tracing is now set for this specific process. You can now run the process normally from your usual run control page.

Step 3 – Retreive the trace

To retrieve the trace that you just ran, go to the process scheduler page (from the run control page or from Peopletools navigation) and find the job that you just ran. Once you find your job, drill down on Details:

And then drill down on View Log/trace:

And you can then find the trace:

PART III – TRACING ON THE APP SERVER

Step 1 – Set the trace on the App Server Configuration File

TraceSQLMask is the variable that you will set. Use the value that you determined in Part I. If you do not know what setting to use, use 255.

Once the trace has been set on the App Server, ALL remote call cobol jobs will be traced, so use this judiciously in your production environment. Once you have retreived the trace, be certain to turn it off.

Step 2 – Retrieve the trace


Once the job has been completed, you can turn off the trace at the App Server and retrieve the trace. The trace will be located in:

/Appserv//Logs/

On peopletools 8.49 and above it will be under c:/users/psft...


The name of the trace will start with ‘cobsql_xxxxxx.trc’ where xxxxxx is a date time stamp indicating when the trace was made.

Read More

Dot profile of Oracle user for PeopleSoft Installation on UNIX

        set -u
        trap "echo 'logout'" 0

# Set up the shell variables:
        EDITOR=vi
        export EDITOR
stty erase ^?
export JAVA_HOME=/opt/java6
export ORACLE_BASE=/u01/app/oracle/product
export ORACLE_HOME=/u01/app/oracle/product/11.2.0/dbhome_1
export PATH=$ORACLE_HOME/bin:$PATH
export CLASSPATH=$ORACLE_HOME/product/jlib/product_jar_file
export LD_LIBRARY_PATH=$ORACLE_HOME/lib:/usr/lib:/opt/java6/lib
export SHLIB_PATH=$ORACLE_HOME/lib:/opt/java6/lib
export LIBPATH=$ORACLE_HOME/lib:$ORACLE_HOME/lib:/opt/java6/lib
export TNS_ADMIN=$ORACLE_HOME/network/admin
TMPDIR=/u01/tmp
TMP=/u01/tmp
export TMP TMPDIR

Read More

USER_PROFILE MESSAGE SETUP 8.4X <> 8.48

*** Setting PT 8.47 ***

1) Setup the local gateway pointing to 8.48 PSIGW. (This is a workaround since there are some issues when integrating pre 8.48 Tools versions with PT 8.48 using differents gateways versions.)

2) The both nodes (default local and remote) should be pinging successfully.

3) Setup InAsync/OutAsync Transactions messages in the Node Definition

8.47 Default Local Node (PSFT_CR) – added In/OutAsyn transaction for USER_PROFILE message.

8.47 Remote Node (PSFT_LM - 8.48) – added In/OutAsync transaction for USER_PROFILE message

4) Make sure you have uncommented the follow peoplecode for USERMAINT Component (savepostchange event)

  If %Mode = "A" Then

         &MSG.CopyRowset(&USERPROFILECHANGE);

         %IntBroker.Publish(&MSG);

      Else

         &MSG.CopyRowsetDelta(&USERPROFILECHANGE);

         %IntBroker.Publish(&MSG);

      End-If;

5) Then, publish a new USER_PROFILE message. You can do this by changing the User Description on User Profile page (PeopleTools > Security > User Profile).

Changed Description field to Ash, Alex Admin 3

6) Make sure the message was sent successfully through Message Monitor page

Checking in the 8.48 side

8.47 side is done!

*** Setting 8.48 ***

1) Make sure the both nodes are pinging successfully (Default Local – PSFT_LM, Remote – PSFT_CR)

2) Open USER_PROFILE Service Operation (PeopleTools  > Integration Broker > Integration Setup > Service Operations)

3) Make sure Update_User_Profile peoplecode is active in the Handlers page tab.

Handler’s details:

4) Create 2 new Routings

-          (Inbound Routing – FROM 8.47 TO 8.48)

-          (Outbound Routing – FROM 8.48 TO 8.47)

Inbound Routing – Details:

Outbound Routing – Details:

5) Make sure you have uncommented the follow peoplecode for USERMAINT Component (savepostchange event)

  If %Mode = "A" Then

         &MSG.CopyRowset(&USERPROFILECHANGE);

         %IntBroker.Publish(&MSG);

      Else

         &MSG.CopyRowsetDelta(&USERPROFILECHANGE);

         %IntBroker.Publish(&MSG);

      End-If;

6) Then, publish a new USER_PROFILE message. You can do this by changing the User Description on User Profile page (PeopleTools > Security > User Profile).

Changed Description field to Ash, Alex Admin 4

7) Make sure the message was sent successfully through Message Monitor page

Checking PT 8.47 Side

PT8.48 side is done!

Read More