Tuesday 13 July 2010

Finding WSH (Work Station Handler) Port in PeopleSoft

For 3 tier access using application designer we need to configure WSL port and start the same. using psadmin. But WSL after listening the request from the client, hands it over to WSH i.e Work Station handler. We can specify WSL port no in Appserver configuration but WSH is alloted any available port no. near in series to WSL port.

To find out the port no on which WSH is running and connected client machines, please run the following command.
for eg. our WSL port is 7890
netstat -a | grep 78[0-9][0-9]



In the output window, we can see that 7892 port no is also shown with a connection status of ESTABLISHED for 3 client machines. So we can say that WSH port no being used is 7892.
WSL i.e Work Station Listener is ready and listening for more client requests.

If you want to learn how to setup 3 tier connection using application designer, please go through my past blog enteries.

Monday 12 July 2010

Generating Key Store and Trust Store using Keytool

What is a keytool?
Keytool is a key and certificate management utility. It enables users to administer their own public/private key pairs and associated certificates for use in self-authentication. It also allows users to cache the public keys (in the form of certificates) of their communicating peers.

What is a keystore?
Keytool stores the keys and certificates in a keystore. The default keystore implementation implements the keystore as a file. It protects private keys with a password. A keystore contains private keys, and the certificates with their corresponding public keys. A keystore is a database of key material. Key material is used for a variety of purposes, including authentication and data integrity. There are various types of keystores available, including "PKCS12" and Sun's "JKS.

In PeopleTools 8.49 keytool is located in PS_HOME/jre/bin

Generating public/private key pair using keytool
keytool -genkey -alias hrms -keyalg RSA -keystore pskey.keystore -storetype JKS

hrms - it is alias name, any name can be entered to identify the server or instance
pskey.keystore - name of the keystore

After running this command , several user input are required regarding the site to generate the keypair. These values are unique for every site.
The keypair that is generated has both public and private key combination. If we want to share out public key with other sites for authentication and communication purposes we need to export the public key from the keystore and share it. Other party needs to import this public key in their keystore.

Exporting public key from keypair
keytool -export -alias hrms -keystore pskey.keystore -rfc -file pshrms.cert
Enter keystore password:

Public key is exported in a form of certificate file which can be shared with another party. While exporting public key, password for keystore is required that was created in previous command.
This is also a self signed certificate. Ideally one should a signed certificate from a CA eg. Verisign, Geo Trust etc.

What is a TrustStore?
A truststore is a keystore which is used when making decisions about what to trust. If you receive some data from an entity that you already trust, and if you can verify that the entity is the one it claims to be, then you can assume that the data really came from that entity.
An entry should only be added to a truststore if the user makes a decision to trust that entity. By either generating a keypair or by importing a certificate, the user has given trust to that entry, and thus any entry in the keystore is considered a trusted entry.

Creating TrustStore and importing public key

keytool -import -alias hrms -file pshrms.cert -storetype JKS -keystore hrms.truststore

Using the above command, you can also import public certificates from other sites.

To view contents of a cert in keystore
keytool -printcert -file pshrms.cert


Read more about keystore, PKI and public key at these links:
http://en.wikipedia.org/wiki/Public_key_infrastructure
http://download.oracle.com/docs/cd/E17476_01/javase/1.3/docs/tooldocs/win32/keytool.html
http://en.wikipedia.org/wiki/Public-key_cryptography

Friday 9 July 2010

Using Find and Grep together


 find ./ -name configuration.properties | xargs grep -H "9030"

Wednesday 21 April 2010

Creating public synonym of all the tables under SYSADM schema

Creating public synonym for a single table is easy in oracle but at times we might  need to create public synonym for all the tables under a schema. In
Peoplesoft, we might use it for below purpose:
        a. To help other Database users to directly access SYSADM tables without  prefixing owner name eg. sysadm.PSOPRDEFN.
        b. To create 2nd access id and granting rights on tables of primary access id.

1. Generating Script for Creating Public synonyms
        Open the SQL Tool and run the following commands.

        SQL> Spool synonyms.sql;

        SQL> select 'create public synonym ' ||table_name||  ' for ' ||owner||'.'||table_name ||';' from dba_tables where owner='SYSADM';

        SQL> spool off;

        Open synonyms.sql in a text editor.
        This file would contain the sql to create public synonym for all the tables in SYSADM schema.There would be multiple entries as shown below
        'CREATEPUBLICSYNONYM'||TABLE_NAME||'FOR'||OWNER||'.'||TABLE_NAME||';' .
        These entries can be simple replaced with blank space.

        We are left with script that be executed to create public synonym of all SYSADM'S table.

2. Granting rights on these public synonyms to another userid.

        SQL> Spool grantsyn.sql;

        SQL> select 'grant select on ' ||table_name|| ' to sysadm2 ;' from dba_tables where owner='SYSADM';

        SQL> spool off;

        OR

        SQL> Spool grantsyn.sql;

        SQL> select 'grant select on ' ||synonym_name|| ' to  sysadm2;' from dba_synonyms where owner='SYSADM';

        SQL> spool off;

3. Run synonyms.sql
4. Run grantsyn.sql

Tuesday 13 April 2010

Using Putty with XManager

1.Installing and Starting Xmanager
Download the Xmanager and install the software on windows machine where graphical display is required. After installation is complete, go to Start > Programs > Xmanager3 > Xmanager – Passive
This will start the Xmanager is passive mode and xmanager will run in background.

2.Configuring Putty
Go to Session and enter the hostname of the server. Make sure SSH is chosen as Connection Type.

Go to SSH – X11 and Enable X11 forwarding. In X display location,enter localhost:0. Hit Open.

3. Using putty for graphical display
Login into the server and start xclock. Output will be a graphical clock displayed on the local windows machine.

This completes the configuration of Putty for graphical display with Xmanager.

Monday 5 April 2010

How to find number, and user for failed login attepts in PeopleSoft

In log file APPSRV_MMDD.LOG (located in <PS_HOME>/appserv/<DOMAIN_NAME>/logs, note each successful or failed login attempt. 
See example below:
PSAPPSRV.3644 (21) [03/26/08 09:43:38 GetCertificate](3) PeopleSoft ID and Password authentication failed. Invalid password for user VP1@kdriver-us.us.oracle.com.
PSAPPSRV.3644 (21) [03/26/08 09:43:38 GetCertificate](1) (NET.502): VP1@kdriver-us.us.oracle.com is an Invalid User ID, or typed the wrong password.  User ID and Password are required and case-sensitive.  Make sure typing in the correct upper and lower case.

Monday 22 March 2010

Information Center for PeopleTools 8.5


Oracle Metalink has Information center for all the PeopleTools Releases that consists of all the information regarding particular PeopleTools

Link for PT 8.5 Information Center
https://support.oracle.com/CSP/main/article?cmd=show&type=NOT&id=1073297.1

Wednesday 3 February 2010

Weblogic Study Material


http://download.oracle.com/docs/cd/E13222_01/wls/docs81/index.html#1123978

Wednesday 20 January 2010

Get our exclusive subscription-only PeopleSoft tips once per month!

How was the blog? Help us in getting better