Application Engine Restart options with Snaps

Restart Facility

Restart Facility?

When there is an Abnormal Termination or Failure of an AE, we can restart the request from the same point where it got errored out i.e. the last successful Check Point.

Ways to Disable/Enable Restart facility?

1) Program Properties:

· In AE Program Properties – Advanced Tab – Disable Restart Check box.

1) Configuration Manager:

· In Configuration Manager – Profile Tab – Edit button – Process Scheduler Tab – Disable Restart check box.

 3) Command Line:

· Include the −DR Y option in the Command Line of PSAE.EXE.

How many ways we can Restart the AE Program?

·   From the Command Line.

This Option normally useful to the developers not for the end users.

C:\PT8.45\bin\server\WINX86\psae.EXE -CT <DBType> -CS <ServerName> -CD <DBName> -CO <OPRID> -CP <Password> -R <RncntlID> -AI <AE Name> -I <Process Instance>

·   From a Process Request page.

Open Process Scheduler by selecting PeopleTools, Process Scheduler, and System Process Requests.

Locate the Run Control ID of the program you need to restart.

To display the details of the failed process, click the Process Detail link.

On the Process Request Details page, select Restart Request, and click OK.

Required steps to implement restart facility?

·   One State Record should be SQL table.

·   Disable Restart should not be checked in Program Properties and Configuration Manager.

mutually exclusive Actions? and Why?? With Example

 What are the mutually exclusive Actions? and Why?? With Example

SQL and Call Section are mutually exclusive to avoid the Data Conflicts and Deadlocks.

Assume Call Section and SQL Actions are allowed in one Step.

Assume an Update SQL is there in one Step which updates ABC Table. So curser will be opened on ABC Table.

And Assume a Call Section is there in the same Step which calls the other Section which is having another SQL on the same ABC Table.

As the cursor is already opened, when it tries to execute 2^nd SQL, Deadlocks and data conflicts will arise.

So to avoid these situations, Call Section is not allowed when there is an SQL Action in a Step and vice versa.

Sample Program:

Assume Call Section and SQL Actions are allowed in one Step.

Include Update SQL in one Step and from the same Step call the other Section which is having Delete SQL on the same table.

Ex:

Main Section Step1 SQL UPDATE ABC SET SALARY = SALARY + 1000 WHERE EMPLID = ‘XYZ’ CallSection Call the Section1 Section1 Step1 SQL DELETE FROM ABC WHERE EMPLID = ‘XYZ’

In Main Section – Step1 – SQL Action – Salary will be update for XYZ employee and it will not Commit. Then it calls the Section1.

In Section1 – Step1 – SQL Action – It deletes XYZ employee and as there are no other Actions it will try to Commit. As there is an uncommitted SQL, conflict will occur.

Since Call Section and SQL are Mutually Exclusive we have to write the same code in other way.

Main Section Step1 SQL UPDATE ABC SET SALARY = SALARY + 1000 WHERE EMPLID = ‘XYZ’ Step2 SQL DELETE FROM ABC WHERE EMPLID = ‘XYZ’

In Main Section – Step1 – SQL Action – Salary will be update for XYZ employee. Since there are no other Actions, while coming out from Step it issues the Commit.

In Main Section – Step2 – SQL Action – It deletes XYZ employee Row and since there are no other Actions it issues the Commit.

Since there are 2 Step Level Commits there will not be any chances to exist Deadlocks.

Actions in Application Engine

  What’s the Sequence of execution?

DoWhen, DoWhile, DoSelect, PeopleCode, SQL / CallSection, LogMessage, DoUntil, XSLT.

Ocean of Peoplesoft

This is Ocean of PeopleSoft Blogs

https://googledrive.com/host/0B7HLZGYLM09haGdkWk1rYkh3MjA/PS-BlogRoll.html