Tuesday, July 27, 2010

Portal Strucure

Portal Structure

PSPRSMDEFN is a Portal Structure Definition table. A good example is to use this table to find portal path for a specific component.

PSPRSMPERM: Shows the permission lists that are assigned to a portal registry structure (content reference). The permission list name is under field PORTAL_PERMNAME.

Thursday, July 15, 2010

Pside Params

Pside parameters

HIDE

Use to hide the PeopleSoft Application Designer interface. Always use this parameter when performing a command line Copy process.

-CT

Source database type.

Enter the type of source database to which you are connecting (for example, ORACLE, SYBASE, and so on).

-CS

Source server name.

Enter the name of the source database server for the database to which you’re connecting.

-CD

Source database name.

Enter the name of the source database to which you're connecting, as you would enter it into the PeopleSoft Login dialog box.

-CO

Source user ID.

Enter the PeopleSoft user ID to use to sign in to the source database.

-CP

Source user password.

Enter the password for the specified user ID for source database.

-TS

Target server name.

Enter the name of the target database server for the database to which you’re connecting.

-TD

Target database name.

Enter the name of the target database to which you're connecting, as you would enter it into the PeopleSoft Login dialog box.

-TO

Target user ID.

Enter the PeopleSoft user ID to use to sign in to the target database.

-TP

Target user password.

Enter the password for the specified user ID for the target database.

-LF

Log file name.

Enter the name of the file in which error messages are logged during the command line Upgrade Copy process.

-PJC

Source project name.

Enter the name of the project that is to be copied from the source database to the target database. This project should be available in the source database before starting the command line Upgrade Copy process to target database.

-PJB

Project name.

Enter the name of the project to be built. This project should be available in the database before starting the command line project build.

-PJTF

Copy Project To File project name.

Enter the name of the project to be copied from the source database to the file.

-PJFF

Copy Project From File project name.

Enter the name of the project to be copied from the file into the source database.

-FP

Project file path.

Enter the path to the project for a Copy to File or Copy From File process.

-OVD

Override dependencies (0 or 1).

Enter 1 to override the checks for unapplied dependency incidents during the Copy From File process and to perform the copy even if the project's dependency incidents have not been applied to the source database.

-CL

Commit limit.

Enter the Commit limit (a number greater than 0) for the number of objects to be copied or compared before a commit is issued. Example: -CL 150

-AF

Audit flags on records (0 or 1).

Enter 1 to keep the target audit flags as is. Enter 0 to take them from the source database. Example: -AF 0

-DDL

Data definition language (DDL) on records and indexes (0 or 1).

Enter 1 to keep the target database DDL flags as is. Enter 0 to take them from the source database. Example: -DDL 0

-PPL

Portal registry structures permission list references.

Enter 1 to keep the target portal registry permission list references as is. Enter 0 to take them from the source database.

-EXP

Export project definition (0 or 1).

Enter 1 to export the project definition to the target database when using the Database Copy process. Not applicable for Copy Project to File process.

-OBJ

Object types to copy

List the object types as numbers with commas as delimiters. For example, if you choose records and indexes alone for copying, use the appropriate numbers for records and indexes from the Definition Type Selection table. For records, the number is 0, and for the indexes, the number is 1. Example: -OBJ 0,1

-RST

Reset done flags (0 or 1).

Enter 1 to reset the done flags before initiating the Copy process. Enter 0 to not reset them. Example: -RST 0

-OVW

Overwrite existing project (0 or 1). Enter 1 to overwrite any existing projects with the same name in the specified path during the Copy Project To File process, or in the database in the Copy Project From File process. Enter 0 to not overwrite existing projects. This applies to the Copy Project To and From File processes only.

-LNG

Copy languages.

List the language codes with commas as delimiters, or enter ALL to select all available languages. For new languages that are not listed in the Language Selection table, use the xlat short name from the LANGUAGE_CD field in the translate table. For example, if you choose English and Spanish for copying, enter the appropriate codes for English and Spanish from the Language Selection table. For English, the code is ENG, and for Spanish, the code is ESP. Example: -LNG ENG,ESP.

-CFD

Keep Target ChartField PageField Display Size.

(Number 1 or 0). This parameter indicates whether or not the target chartfield page field display size attributes are to be kept, or whether they should be set from source during copy. See Upgrade Options for more information.

Enter 1 to keep the target chartfield page field display size attributes.

Enter 0 to set these attributes from the source values.

-CFF

Keep Target ChartField Field Format.

(Number 1 or 0) This parameter indicates whether or not the target chartfield field format attributes are to be kept, or whether they should be set from the source during Copy. See Upgrade Options for more information.

Enter 1 to keep the target chartfield field format attributes.

Enter 0 to set these attributes from the source values.

Monday, July 12, 2010

Report Repository Tables

PS_CDM_LIST
PS_CDM_AUTH
PS_CDM_TEXT
PS_CDM_FILE_LIST
PS_CDM_TRANSFER
PS_CDM_TRNFR_RJCT
PS_CDM_LIST_ARCH

Tuesday, July 6, 2010

Tuxedo commands

psadmin - applicaiton server - tuxedo command line

boot commands:

> boot -y (boot the domain normally, if there is an error encountered continue to boot the domain.

Unlike if you boot via psadmin it will shut the domain down)

> boot -y -w (This a fast boot, as the -w switch states to boot all the servers in parallel, and not one by one)

> boot -g JSLGRP( using the -g option states that you are going to boot by server group, every server in tuxedo is assigned to an individual server group)

boot -g PUBSUB

boot -g JREPGRP

> boot -i 10 (every server has an individual server id assigend to it, you can get this info when you do a server stats from psadmin and look under the SRVID column)

shutdown commands:

Eaisest to hardest

> stop -y (this means stop the application server normally, and bring everything down cleanly and clean up IPC)

> stop -y -c (This means stop the application server normally even if clients are attached)

> stop -y -c -w 0 (This means stop the application server normally even if clients are attached and the -w stands for wait 0 seconds to do it shutdown now)

> stop -y -c -w 0 -k KILL (This is the worst form of ahutdown as this sends a KILL signal to Tuxedo, and shoudl only be used as a last resort.) If you elicit this command you must then repeat the command stop -y -c -w 0 as this will then bring down the BBL and clean upi IPC. When you use the kill the BBL does not have time to cleanup IPC as this is a forced kill, so to ensure that nothing for the doamin exists in IPC you have to shutdown the BBL.

---------------------------- Other stop commands------------------------------------------------------------------------------------------------------

> stop -g JSLGRP (using the -g option states that you are going to stop by server group, every server in tuxedo is assigned to an individual server group

> stop -g PUBSUB

LOOK AT FOR TUNING

> stop -i 10

You can also use the stop command if you want to stop an server that is stuck trying to execute a ICPanel. If you see memory going up on the machine you can see if there are any process or PSAPPSRVs spinning trying to execute a panel request. If you look at task mananger a see a request consuming a lot of memory compared to the other server procsses you can assume that the server is spinning on a Panel or someother request.


suspend (susp) {-q qaddress | -g groupname | -i srvid | -s service |

-I interface} ...

---------------------------------------------------------------------------

Suspend the indicated resources.

> help psc

printservice (psc) [-m machine] [-g groupname] [-i srvid] [-q qaddress]

[-s service] [-a {0|1|2}]

---------------------------------------------------------------------------

Print information for the specified service.

resume (res) {-q qaddress | -g groupname | -i srvid | -s service |

-I interface} ...

---------------------------------------------------------------------------

Resume (unsuspend) the indicated resources.