java ,spring,Hibernate

how to get the result set data from the procedure

2010-11-17T05:10:00.000-08:00

ORACLE Retrivind data from a procedure

CREATE OR REPLACE PROCEDURE GET_ANS_TO_EDIT (
ARG_CAT_ID in varchar2,
ARG_LOB_ID_LIST in MKD_CHAR_ARRAY,
ARG_COUNTRY_CD_LIST in MKD_CHAR_ARRAY,
ARG_STATE_CD_LIST in MKD_CHAR_ARRAY,
ARG_QSTN_SEQ_LIST in MKD_NUM_ARRAY,
ARG_SEQ_QID_LIST in MKD_CHAR_ARRAY,
ARG_PAGE_NO in number,
ARG_ROWS_PER_PAGE in number,
ANSWER_COUNT out number,
PAGE_NO out number,
ANSWER_CURSOR out SYS_REFCURSOR,
STATUS out number)
IS
BEGIN
DECLARE
TOTAL_PAGES number;
START_REC_NO number;
END_REC_NO number;
LOB_SP_ID char(2);
BEGIN
STATUS:=0;
IF ARG_LOB_ID_LIST IS NULL THEN
DBMS_OUTPUT.PUT_LINE ('Lob list is empty.');
STATUS:=1;
RETURN;
END IF;

IF ARG_CAT_ID = 'C5' THEN
SELECT column_value INTO LOB_SP_ID FROM TABLE(ARG_LOB_ID_LIST)
WHERE ROWNUM < is_dashboard_country =" 'D'" country_cd="s.COUNTRY_CD" country_last_update_dt =" s.COUNTRY_LAST_UPDATE_DT" cat_id =" ARG_CAT_ID" lob_id =" l.LOB_ID" lob_last_updated_dt =" l.LOB_LAST_UPDATED_DT"> 0 THEN
TOTAL_PAGES := CEIL(ANSWER_COUNT/ARG_ROWS_PER_PAGE);

START_REC_NO := 0;
END_REC_NO := ARG_ROWS_PER_PAGE;

PAGE_NO := ARG_PAGE_NO;

IF PAGE_NO > TOTAL_PAGES THEN
PAGE_NO := TOTAL_PAGES;
END IF;

-- calculate next record start record and end record
IF PAGE_NO > 0 THEN
START_REC_NO := ABS((PAGE_NO-1)*ARG_ROWS_PER_PAGE);
END IF;

IF ANSWER_COUNT < (START_REC_NO+ARG_ROWS_PER_PAGE) THEN END_REC_NO := ANSWER_COUNT; ELSE END_REC_NO := START_REC_NO + ARG_ROWS_PER_PAGE; END IF; START_REC_NO := START_REC_NO + 1; OPEN ANSWER_CURSOR FOR SELECT QCSL.QSTN_ID, QCSL.SEQ_NO, QCSL.QSTN_SHRT_TX, QCSL.QSTN_LONG_TX, QCSL.LOB_ID, QCSL.LOB_DESC, a.ANSW_SHRT_TX, a.ANSW_LONG_TX, a.ANNOTATION_TX, QCSL.COUNTRY_DESC, QCSL.STATE_CD, QCSL.STATE_DESC, QCSL.ANSID, QCSL.RNUM FROM (SELECT * FROM ( SELECT TBL.*, ROWNUM as RNUM FROM ( SELECT q.QSTN_ID, q.SEQ_NO, q.QSTN_SHRT_TX, q.QSTN_LONG_TX, l.LOB_ID, l.LOB_DESC, cs.COUNTRY_DESC, cs.COUNTRY_CD, cs.STATE_CD, cs.STATE_DESC, cs.ANSID, cs.COUNTRY_LAST_UPDATE_DT, cs.STATE_LAST_UPDATE_DT, q.QSTN_LAST_UPDATE_DT FROM TQUESTION q, TLOB l, (SELECT CNTYSTATE.*, ROWNUM as ANSID FROM ( SELECT c.country_cd , c.country_desc, c.COUNTRY_LAST_UPDATE_DT, s.state_cd, s.state_desc, s.STATE_LAST_UPDATE_DT FROM tcountry c, TSTATE_PROVINCE s WHERE c.IS_DASHBOARD_COUNTRY = 'D' AND c.COUNTRY_CD=s.COUNTRY_CD AND c.COUNTRY_LAST_UPDATE_DT = s.COUNTRY_LAST_UPDATE_DT AND c.EXP_DT IS NULL AND s.EXP_DT IS NULL AND (c.COUNTRY_CD in (SELECT column_value FROM table(ARG_COUNTRY_CD_LIST)) OR s.STATE_CD in (SELECT column_value FROM table(ARG_STATE_CD_LIST))) ORDER by UPPER(c.country_desc), UPPER(s.state_desc) ) CNTYSTATE) cs WHERE q.CAT_ID = ARG_CAT_ID AND q.LOB_ID in (SELECT column_value FROM table(ARG_LOB_ID_LIST)) AND q.SEQ_NO in (SELECT column_value FROM table(ARG_QSTN_SEQ_LIST)) AND q.EXP_DT IS NULL AND q.LOB_ID = l.LOB_ID AND q.LOB_LAST_UPDATED_DT = l.LOB_LAST_UPDATED_DT AND l.EXP_DT IS NULL ORDER BY q.SEQ_NO ASC, UPPER(l.LOB_DESC) ASC, cs.ANSID ASC) TBL WHERE ROWNUM <= END_REC_NO ) WHERE RNUM >= START_REC_NO) QCSL LEFT OUTER JOIN TANSWER a
ON QCSL.QSTN_ID = a.QSTN_ID
AND QCSL.QSTN_LAST_UPDATE_DT = a.QSTN_LAST_UPDATE_DT
AND QCSL.COUNTRY_CD = a.COUNTRY_CD
AND QCSL.STATE_CD = a.STATE_CD
AND QCSL.COUNTRY_LAST_UPDATE_DT = a.COUNTRY_LAST_UPDATE_DT
AND QCSL.STATE_LAST_UPDATE_DT = a.STATE_LAST_UPDATE_DT
AND a.EXP_DT IS NULL;
END IF;

EXCEPTION
WHEN NO_DATA_FOUND THEN
STATUS := 1;
DBMS_OUTPUT.PUT_LINE ('status 1');
DBMS_OUTPUT.PUT_LINE (SQLERRM);
WHEN OTHERS THEN
DBMS_OUTPUT.PUT_LINE ('status 2');
DBMS_OUTPUT.PUT_LINE (SQLERRM);
STATUS := 2;
END;
END;

//How to handle in java

String callStatement = "{ call get_ans_to_edit(?,?,?,?,?,?,?,?,?,?,?,?) }";
dbConnection = getConnection(entityName);
prepStatement = dbConnection.prepareCall(callStatement);
oracle.sql.ArrayDescriptor num_array_type =
oracle.sql.ArrayDescriptor.createDescriptor("MKD_NUM_ARRAY", dbConnection);
oracle.sql.ArrayDescriptor str_array_type =
oracle.sql.ArrayDescriptor.createDescriptor("MKD_CHAR_ARRAY", dbConnection);
// Prepare Lob list
String lobIds[] = (String[]) editInfo.getLobList().toArray();
java.sql.Array lob_list = new
oracle.sql.ARRAY(str_array_type, dbConnection, lobIds);
// Prepare country state list
List countryCombo = (List) editInfo.getCountryList();
ArrayList countryList = new ArrayList();
ArrayList stateList = new ArrayList();
for(int j=0; j < countrystate =" countryCombo.get(j).toString().split("> 1) {
if (countryState[1] != null && !stateList.contains(countryState[1])) {
stateList.add(countryState[1]);
}
}
else {
if (countryState[0] != null && !countryList.contains(countryState[0]))
{
countryList.add(countryState[0]);
}
}
}

String cntryCds[] = new String[countryList.size()];
countryList.toArray(cntryCds);
java.sql.Array cntry_list = new
oracle.sql.ARRAY(str_array_type, dbConnection, cntryCds);
String stateCds[] = new String[stateList.size()];
stateList.toArray(stateCds);
java.sql.Array state_list = new
oracle.sql.ARRAY(str_array_type, dbConnection, stateCds);
Integer questionNos[] = new Integer[editInfo.getQuestionSeqNoList().size()];
editInfo.getQuestionSeqNoList().toArray(questionNos);
java.sql.Array qstn_list = new
oracle.sql.ARRAY(num_array_type, dbConnection, questionNos);
java.util.List seqQstnIdList = editInfo.getSequenceQstnIdList();
String seqQstnId_list[] = new String[seqQstnIdList.size()];
seqQstnIdList.toArray(seqQstnId_list);
java.sql.Array seqQstnId_array = new
oracle.sql.ARRAY(str_array_type, dbConnection, seqQstnId_list);

PageInfo pageInfo = editInfo.getPageInfo();
if (pageInfo != null) {
cPageNo = pageInfo.getCurrentPaginationIndex();
iPageNo = cPageNo;
}
prepStatement.setString(1, categoryId);
prepStatement.setObject(2, lob_list, oracle.jdbc.OracleTypes.ARRAY);
prepStatement.setObject(3, cntry_list, oracle.jdbc.OracleTypes.ARRAY);
prepStatement.setObject(4, state_list, oracle.jdbc.OracleTypes.ARRAY);
prepStatement.setObject(5, qstn_list, oracle.jdbc.OracleTypes.ARRAY);
prepStatement.setObject(6, seqQstnId_array, oracle.jdbc.OracleTypes.ARRAY);
prepStatement.setInt(7, cPageNo);
prepStatement.setInt(8, iShowRows);
prepStatement.registerOutParameter(9, oracle.jdbc.OracleTypes.INTEGER);
prepStatement.registerOutParameter(10, oracle.jdbc.OracleTypes.INTEGER);
prepStatement.registerOutParameter(11, oracle.jdbc.OracleTypes.CURSOR);
prepStatement.registerOutParameter(12, oracle.jdbc.OracleTypes.INTEGER);
prepStatement.execute();

iTotalRows = prepStatement.getInt(9);
cPageNo = prepStatement.getInt(10);
status_cd = prepStatement.getInt(12);
if (CATEGORY_LOB_SPECIFIC_DATA.equals(categoryId.trim())) {
isLobSpecific = true;
}
qsView.getResultStatus().setSuccessStatus(status_cd);
StringBuffer htmlResult = new StringBuffer();
if (status_cd == 0 && iTotalRows > 0) {
dbResults = (ResultSet) prepStatement.getObject(11);
iTotalPages=((int)(Math.ceil((double)iTotalRows/iShowRows)));
// if current page is grater then number of pages then set iPage to 0
if (iPageNo > iTotalPages) {
iPageNo = iTotalPages;
cPageNo = iPageNo;
}
if(iPageNo==0) {
iPageNo=0;
cPageNo=1;
}
else{
cPageNo=iPageNo;
iPageNo=Math.abs((iPageNo-1)*iShowRows);
}
//// calculate next record start record and end record
if(iTotalRows<(iPageNo+iShowRows))
{
iEndResultNo=iTotalRows;
}
else
{
iEndResultNo=(iPageNo+iShowRows);
}
iStartResultNo=(iPageNo+1);

PEGA12

2010-07-29T01:00:00.000-07:00

PEGA11

2010-07-29T00:01:00.000-07:00

PEGA10

2010-07-28T23:50:00.000-07:00

PEGA9

2010-07-28T22:52:00.000-07:00

PEGA8

2010-07-28T22:33:00.000-07:00

PEGA7

2010-07-28T02:58:00.000-07:00

PEGA6

2010-07-28T00:24:00.000-07:00

PEgA5

2010-07-27T01:53:00.000-07:00

PEGA4

2010-07-26T23:54:00.000-07:00

PEGA3

2010-07-26T03:38:00.000-07:00

PEGA2

2010-07-26T01:21:00.000-07:00

PEGA

2010-07-21T04:37:00.000-07:00

CLASS STRUCTURES AND HIERARCHY DESIGN

•System Architecture
•Understand the difference between a Business Rules Engine (BRE) and a Business Process Management System(BPMS)

Business Rules Engine (BRE) is a software system that manages business rules, it separates the business rules from the application code.
Engine Types
•Inference
–Derives a conclusion based on a knowledge base
–Answers questions when a user or application submits them
–Example: Should this customer be allowed a mortgage?
•Reactive
–Detects and reacts to patterns of events occurring
–Performs an action automatically when a certain rule is violated
–Example: Alert a manager when certain items are out of stock
No User Interface
•External systems communicate through open interfaces with the Rules Engine
-----------------------------------------------------------------------------------------------
Business Process Management System (BPMS) is a software system which allows for the direct execution of business processes.
•Removes the costly and time intensive development of process specific software
•Allows the full business process to be defined
•Can invoke external services to perform business operations
•Can send messages to human workers requesting they perform certain tasks
•Can call a Business Rules Engine to make automated decisions
•Provides a process driven User Interface
•Pega Rules Business Rules Engine
•Separates business logic from your mission-critical applications and enables your enterprise to capture, manage and execute your business policies and practices
•Pega Rules Provides
•An inference engine to perform dynamic business decision making
•A reactive engine using declarative rules that are used only when underlying data changes
•This combination of rule types and processing approaches provides
•Rapid time to production
•Increased ROI
---------------------------------------------------------------------------------------------
Identify the elements that comprise Process Commanders Java EE architecture

PRPC Architecture Overview
•Secure, scalable, upgradeable application framework based on a declarative object mode
•Shared UI components, business logic, and data model
•Standard data model
•Integrated tool set for extending the data model, business logic, and user interface
•Pre-built services designed specifically for BPM
•Designed to integrate with an organization’s existing IT infrastructure

Architecture Key Concepts
•Application Server
•Java
•Java Enterprise Edition
•Multi Tired Architecture
•Enterprise Java Beans
•Servlets
•Java Server Pages
•Java Data Base Connectivity

Describe the function of each component of the process commander architecture

•Application Server is a software dedicated to the serving (running) of other applications
–Facilitates
»Programming productivity
»Provides dedicated standard API’s
»Response to demand
»Provides scalability, load-balancing, (re)configuration, deployment
»Integration with existing systems
»Provides standard services
»SOAP
»Message Queue
»DB Access
»Security
•Java is an object-oriented programming language developed by Sun Microsystems
–Syntax is similar to C
–Is compiled to byte code which is run by a Java Virtual Machine
•Java Virtual Machines (JVM) are available for many different platforms
–Java code can be run on any platform that provides a suitable JVM

Java vs. JavaScript
–Originally developed by Netscape
–Is typically interpreted by a Web Browser
»Does not use a JVM
–Only similarity to Java is the “C like” syntax
•Java Enterprise Edition is a platform for developing and running distributed multi-tier architecture Java applications
–Formerly known as Java 2 Platform, Enterprise Edition (J2EE)
•The Java EE platform is defined by a specification
–Platform vendors must agree to certain conformance requirements in order to declare their products as Java EE compliant
•Multi Tired Architecture is a client-server architecture in which an application is executed by more than one distinct software agent
•The Java EE standard facilitates a multi-tiered architecture
–Often referred to as n-tier architecture

•Enterprise java Bean is a server-side component that encapsulates the business logic of an application
•EJB’s are deployed in an EJB container within the application server

•Java Servlets are Java programming language classes that dynamically process requests and construct responses
Servlets are deployed in a web container within the application server
Typically generate HTML

Reusability and Hierarchy Design
Define reusability and its impact on application design
Reusability Of assets across an organization is integral to the success of a project
By gathering the right requirements, and applying the principles of reusability and class
hierarchy design heuristics, you will always create systems that deliver on the value
promised . Ultimately, the reusability requirements drive the selection of your class
hierarchy design pattern .
Describe the difference between application reusability and organization reusability
Application – Assets are specific to an application and common to more than one business unit
For example, all divisions across BIG have some type of Policy Administration
Organization – Assets common across multiple divisions or applications
For example, LDAP integration
Understand the difference between one – Off application and a reusable application
Generalized
Define a common interface for its sub-application
Defers some of or all of its implementation to application assets defined in its sub-applications
The assets that an generalized application declares but does not implement are called generalized assets.A solution framework is an generalized application

Specialized
Applications that are not generalized are called specialized applications
One –Off application is a specialized one.
Identify the scope of reusable components within a company’s organizational diagram
We can create reusable components for an organization, divisions and units and also for a group of users. We can design these components where ever the similar kind of functionality is seen across divisions, units and organizations.
Design and create an organizational structure comprised of an organization, divisions, and business units
In PRPC the following rules are used for creating organization, Divisions, and Business Units.
Data-Admin-Organization
Data-Admin-OrgDivision
Data-Admin-OrgUnit

--------
Understand the concept and benefits of building on a common application layer
If we want to develop a frame work which can be used by different independent vendors to implement solutions upon that we need to build a common application layer. This layer can be reused and customized according to the requirements. The basic functionality will be residing in this common application layer.
For example if we develop a application layer for a banking domain, the same can be used by independent software vendors to develop/customize the application.
Design and implement reusable class structure with appropriate top, divisional, and class group levels and work classes.
Always while designing the class structure, the best practice is we should apply class level ‘sense’ according to the business hierarchical structure of the organization.
Organization --- Division --- Unit levels can be transformed to
Top level class --- Divisional level --- Class group level with respect to PRPC. Each class group level will be a unit / application where in different process can be initiated. By Default PRPC is shipped with and Organization called Pega.com.
---------------
Classes and Class Groups/ Work Pools
Create Classes and Class Groups
A Class group is an instance of the Data-Admin-DB-ClassGroup. A class group instance causes the system to store the instances corresponding to two or more concrete classes that have a common key format in a single database table. Class groups are commonly used to cause the system to store instances of similar or related Work- concrete classes together in one relational database table.
While Creating the class group we need to specify the key for the group. Generally it is pyID.
Understand the purpose of a class group and its relation to the application’s database and a user’s work pool
Different work types (classes derived from the Work- base class) are grouped in to one class group and when this class group is added to a user in his access group, user can work on through each work type of each class groups. Class groups so added are called as Work pools.
Instances of Data-Admin-DB-Table are used for mapping the classes and class groups with DB tables. At any point of time, if a class is not mapped to any DB table, it’s instances are stored in it’s super class’s mapped table. The principle is recursive.
All the classes belonging to the class group will have the same keys of the class group.

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

Describe the difference between the abstract and concrete classes
Abstract Classes can contain any rule type
Cannot contain instances
Great for reuse
The name of a abstract class must end with a dash (-).
Concrete classes hold persistent objects, known as instances
Names must not end with a dash (-)
Names should define the type of work being performed.
Understand the concept of top-level and base classes
Top level classes are always abstract and inherit from the @baseclass.
Top level class is an abstract class that has the ultimate base class @baseclass as parent but
is not one of the standard base classes.
@baseclass is called as the ultimate base class. And its immediate child classes like Data-,
Work-, Assign- etc are called as base classes.

---------------
Tips for Rule Set Hierarchy design
Limit the number of RuleSets to the minimum amount necessary
Create a RuleSet only if it has a reasonable chance of holding rules
Use the Initial Setup Wizard to create the organizational RuleSet
Use the Application Accelerator to create the first RuleSet needed for each application
A RuleSet can inherit features from other, prerequisite RuleSets and also from lower-numbered versions of itself
As a best practice, update the RuleSet Version rules created by the Application Accelerator to identify Pega-ProCom:04-02 as a prerequisite to each of your application RuleSets
Understand the Connection between Classes and Rulesets
While creating a new class you need to Identify the RuleSet version number that applies to the class. The Archive tools depend on this version. The Export Archive tool includes this class instance if you export this RuleSet version or a higher-numbered version.
However, version information in class rules is not used for rule resolution. You cannot define multiple class rules with the same class name but different versions.

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

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

Versioning at configuration management controls the exact application behavior, at development time it controls the access to the developers.
Understand how to provide users with access to Rulesets
We can add rulesets at either at Organization or at Division or at access group, but not at the unit. It is not mandatory to add the rulesets either at Organization, division and the access group. We can add at all these places, at the same time we can refrain by not adding at any of these places.
Significance of adding rulesets at Organization: We can add one or more rulesets to organization for providing access to all the users belonging to that organization to the specified Ruleset. Assume an application like “leave application” which needs to be accessed by all the employees of organization, and then perhaps we may like to add leave application’s rulesets at Organization level.
Significance of adding rulesets at Division: We can add one or more rulesets to division for providing access to all the users belonging to that division. Assume an application like “Loan application” of a bank which needs to be accessed only by the employees of Loans division, then perhaps we may like to add Loan application’s rulesets at Loan division level, so that other divisions in the same organization can not have access the Ruleset

-------

Significance of adding rulesets at Access Group: We can add one or more rulesets to access group when we think that security needs to be controlled basing on the specific job function. Assume that an application like “Heart allocation request application” is being developed for all the Project Managers in Virtusa for making resource requests for their projects. Then we can think of adding this application Ruleset in an access group called “PM”, so that all PMs across all the divisions in Virtusa can access this application.
Understand the reasons of locking rule sets
You can use the Security tab to lock the Ruleset by requiring developers to enter a password when they update the Ruleset, or add or update version instances for the Ruleset.
We can avoid tampering/misuse of rules (assets) by locking the rule set when the application is shipped for production.
Describe rule resolution, how it works, and how it impacts rule set hierarchy design
Picking up right rule at right time is called as rule resolution. Process by which Process Commander decides which rule (of a series of possible rules) will be used to execute an action.
-------
Dynamic selection of rule involves the following steps
Business process
Product
Organization
Ruleset and version
Date
Time
Circumstance
Security
We have to design the rule set hierarchy considering the process of rule resolution. At run time it checks for the order we have configured rule sets in the access group. We have to check for where exactly a particular rule fits in the organization and accordingly we need to create multiple rule sets to modularize the application into different rule set constituents.

Availability of the rules: Availability is an important aspect of any rule for it to be considered by Rule resolution algorithm. pyRuleAvailable property represents whether a given rule is available or not ? At any point of time, this property can be set with either of the following four values
YES : Indicates that this rule is available. Rules with a Yes value are visible to rule resolution processing and executed.
NO : Indicates that is rule is not available and become invisible to the rule resolution algorithm for all users (including yourself). The No setting is useful in experimentation and troubleshooting to assess the effect of two rule versions.
Ex : If you are setting “No” status for a rule of version 01-01-03, still 01-01-01, 01-01-02, 01-01-04 of same rule are visible to rule resolution algorithm
BLOCKED : This is a stronger form of No because it affects all lower-numbered versions of the rule and it makes all lowered numbered including this version not to be visible to rule resolution algorithm. Note : A blocked rule does not prevent rule resolution from finding (and running) higher-numbered versions
Ex: If you are setting “BLOCKED” status for a rule of version 01-01-03, only upper versions like 01-01-04….. of same rule are available to rule resolution algorithm. Lower version like 01-01-01 and 01-01-02 are not available for rule resolution algorithm
FINAL : We need to set availability to Final if we want this rule to be available (equivalent to Yes), but want to prevent others from overriding this rule in any other RuleSet. A final rule can be superceded by a higher-numbered version (in the same RuleSet), but not by any version in any different RuleSet.
A rule is said to be available only when it’s availability is either “Yes” or “Final”

Understand the impact of RuleSet versioning on the deployment and migration of rules
You can use these tools to copy a product or RuleSet from one Process Commander system to another. (Also called migrating or moving, this procedure doesn't alter or delete the source rules.)
For example, you can move a product from a smaller development or test Process Commander system into a production Process Commander system. The source and destination systems may have different servers, operating systems, database vendors, Web server software vendors and so on. Information inside the ZIP file consists entirely of XML documents in Unicode characters.
Confirm that you have a working Operator ID with a PegaRULES:SysAdm4 access role on both the source system and destination system.
Confirm that the Process Commander version number of the destination system is not less than the version number of the source system. Don't attempt to move a RuleSet created in version 05-01-06 into a system based on version 04-02-01.
Review the RuleSets version rules to be included. Note the prerequisite RuleSets and versions they reference. If moving more than one RuleSet, note whether and how they are interdependent.
On the destination system, access the Rules by Type Explorer. Confirm that the destination system includes all the prerequisite RuleSets and versions needed.
On the source system, create a Product rule or Product Patch rule if you need to include data instances or an installation activity in the ZIP archive.
On the source system, examine the All Checkouts report to make sure none of the rules to be migrated is checked out. Choose the View > Rules > All Checkouts menu item to produce this report.
On the source system, use Rules per RuleSet, Version, Class report (in the Rule Reports area of the Monitor Activity slice to estimate a count of rules to be included in the ZIP archive. (The reports show only up to 10,000 rules. The ZIP archive may contain more than 10,000 rules.)
Export the ZIP archive.
Copy the ZIP archive to the destination system.
Import the ZIP archive.
Adjust your access group as necessary to provide access to the uploaded RuleSets and versions.
Log off, then log in with the updated access group, and review the uploaded results. If they are satisfactory, this may be a good moment to lock the imported RuleSets and versions.
Consider whether a new class group and work type structure is appropriate for deployment of the application.

Application Rule
Explain the purpose of application rule
Rule-Application is the place where we specify the RuleSet lists so that this list can be shared across multiple user configurations. This ensures the following benefits:
Reduce the namespace problems
Smaller and efficient caching
A user can have multiple applications.
Allows users to have different privileges across different applications.
Previously though multiple applications are allowed, it’s only through the mixed ruleset lists i.e., the Rulesets required are combined as a single long list. So multiple applications coexist in the single ruleset list.
The PegaRules 5.1 is so developed to adopt the application focused user configuration. Rule-Application alone remains as the center where we mention the rulesets list, which the user has access to. If the user works with a particular application, then that particular ruleset list becomes the pxThread’s active ruleset list.
Understand the connection between application rules, Rule Sets and rule resolution
In the rule resolution process the engine checks for the application rules which are configured in the access group and also the order in which the rule sets are configured in Rule-Application also important.

-------------------
Units of Work
Define and understand the differences between the basic units of work and their associated work classes:
Work-Object-
A work object is the primary unit of work completion in an application, and the primary collection of data that a flow operates on.
As an application is used, work objects are created, updated, and eventually closed (resolved).
Every work object has a unique ID (property pyID), an urgency value, and a status (property pyStatusWork).
Work-Cover-
A cover is a work object that is also a parent to one or a few other related work objects. Typically one work party — such as the customer party — is present in the cover work object and also present in all of the covered work objects associated with it. The covered work objects are the children in a parent-child relationship.
Internally, a cover is a work object in a concrete class derived from the Work-Cover- abstract class.
A cover work object provides a means to coordinate processing of the related work objects. Normally, the system resolves a cover work object once all its "member" covered work objects are resolved. The standard ticket rule Work-Cover-.AllCoveredResolved alerts a cover flow that all the member work objects have been resolved.
Locking a covered work object normally also locks the cover work object. This is desirable as the cover work object may contain totals, balances, counts or other derived information that require single-threaded access. Normally, the cover work object is added to the clipboard using a page named pyCoverPage; the covered work object is on a page named pyWorkPage.
The covered work objects may be of various work types. However, the work type of the cover and the work type of the covered objects must all belong to the same work pool.
Work-Folder-A folder is a work object in a concrete class that inherits from the Work-Folder- class. A folder object holds a collection of one or more other work objects (which themselves may be basic work objects, other folders, or covers) providing access for analysis and reporting.
By convention, the work object ID of folders has the format F-99999.
In contrast to covers:
One work object may be associated with multiple folders, but only with one cover.
Members of a folder can belong to various work types, which need not be all in a single work pool.
The relationships between folder work objects and their contents may be many-to-many.

Understand the inheritance structure of work classes
@baseClass
Work-
Cover-
Folder-
Object-

Understand when to inherit from work-object- versus work-cover-

Generally we use Work-Object- inheritance for individual work objects, if we want to process multiple dependent work objects which are tightly coupled, covers (work-cover-) can be used. If the work objects are not tightly coupled then we can use Folders for resolution of multiple tasks.

Explain how a work object ID is defined
A work object ID is the permanent, external identifier of a work object, the value of property Work-.pyID.
Prefixes and suffixes
For every work object, either the prefix or suffix must be present. Normally the system assigns a permanent work object ID automatically as a work object is created. The standard utility activity named Work-.GenerateID uses the standard properties pyWorkIDPrefix and pyWorkIDSuffix in its computation.
For example, the prefix of work object Q-1432 is Q. The prefix of the work object MORT-763-K4 is MORT. The suffix of work object 15378-DR is DR.
If you don't specify a prefix, the Work-.GenerateID activity uses W as the prefix and no suffix. The Work-Cover-.GenerateID activity uses C as the default prefix. Conventionally, the F prefix identifies folder work objects.
The internal class Data-UniqueID supports work object numbering, and ensures that work object IDs are unique system-wide, not just within an application or organization.

Wizards and Accelerators
Understand the purpose and output of external setup wizard
An optional step during installation or upgrade of a Process Commander system, the External Setup wizard creates a starter kit of rules and data instances based on a single input text value.
Ordinarily, the External Setup wizard is not started from within the Process Commander portal.
For example, if the installer enters Alpha, the External Setup wizard creates these instances:
A RuleSet named Alpha and a Version 01-01-01
An organization Alpha.com, a division AlphaDiv in the organization, and a unit AlphaUnit within the division
A top-level abstract class Alpha- referenced in the Organization data instance
An application rule AlphaApp
A workbasket named default@Alpha.com
A work group named default@Alpha.com
An Operator ID named Administrator@Alpha.com, linked to the Developer portal and the application rule.
--------
Understand what needs to be created prior to and after running the Application Accelerator in advanced mode
Pre Application Accelerator set up
Create Rule Sets
Add new Rule Sets to application rule
Reset your Ruleset Access
Create new classes
Post-Accelerator manual Entry Complete Set up of your application
Create RuleSet and RuleSet versions
Create classes
Add new class group to work classes

-------------------
Understand the purpose and output of the Application Accelerator when run in advanced mode
Streamlines the process of setting up the foundation for your application
Guides you through the initial development steps when you construct a new application
Allows you to build the elements of your application from the Class Group down
Application Accelerator Creates
A RuleSet and version for the application which is added to your access group
A simple class structure, including covers and work-related classes
A class group (work pool) and supporting database table
Work object and cover prefixes
Properties and models
Work parties
Work object forms (harness and section rules) with your application properties added
One or more basic flows
Workbaskets, worklists, and work groups

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

Application Guardrails
Identify the guard rails and describe their intent
Adopt an Iterative Approach
Establish a Robust Foundation
Do Nothing That Is Hard
Limit Custom Java
Build For Change
Design Intent-Driven Processes
Create Easy-To-Read Flows
Monitor Performance Regularly
Calculate and Edit Declaratively, Not Procedurally
Keep Security Object-Oriented Too

-----------

Know how to validate guardrail compliance when building an application
The Application Preflight tool performs a number of checks on the rules in the currently selected application. These checks are designed to encourage good design and implementation practice, such as codified in the SmartBuild guardrails and elsewhere.
A rule in your application may work correctly and save without errors, but still be marked with a warning (). The Application Preflight tool summarizes these warnings.
For example, a decision table rule may contain two rows that conflict — give a different result for the same inputs. You can save the rule and execute it within your application, because the uppermost row of the table is used at runtime, and other conflicting rules are ignored. However, the conflict may indicate that the rule was not entered correctly.
You may perform the preflight check at any time during development. As a best practice, use the preflight tool before locking a version of a RuleSet, and research each warning message.

Tutorial Refrences

2008-01-07T10:30:00.001-08:00

RMI Pdf : http://notes.corewebprogramming.com/student/RMI.pdf

: http://java.sun.com/javase/technologies/core/basic/rmi/index.jsp
: http://java.sun.com/docs/books/tutorial/rmi/index.html

Hibernate Queries

2008-01-07T10:30:00.000-08:00

Reference :http://www.hibernate.org/hib_docs/reference/en/html/index.html
Reference for Xdoclet : http://www.warfrog.com/hibernatetutorial/
Examples to use Criteria
........................
for (Iterator iter = session.createCriteria(SpecialEditionCD.class).list().iterator(); iter.hasNext();) {
SpecialEditionCD secds = (SpecialEditionCD) iter.next();
System.out.println(secds.getTitle()+" : "+secds.getNewFetures());
}

for (Iterator iter = session.createCriteria(InternationalCD.class).add(Restrictions.ilike("languages", "Te%")).list().iterator(); iter.hasNext();) {
InternationalCD secds = (InternationalCD) iter.next();
System.out.println(secds.getTitle()+" : "+secds.getArtist());
}

Query query = session.createQuery("select c.purchaseDate,c.cost from CD c,SpecialEditionCD s where c.id= s.id and c.id = 1");
List li = query.list();

CoreJava

2008-01-03T22:51:00.000-08:00

Encription and decription using Java

import java.security.spec.AlgorithmParameterSpec;
import java.security.spec.KeySpec;
import javax.crypto.Cipher;
import javax.crypto.SecretKey;
import javax.crypto.SecretKeyFactory;
import javax.crypto.spec.PBEKeySpec;
import javax.crypto.spec.PBEParameterSpec;

public final class EncriptDecript {
/** Encrypt algorithm */
public final static String DES = "DES";
/** Encrytp encoding */
public final static String UTF8 = "UTF8";
/**
* The key format: password-based encrypt with MD5 and DES.
*
* @value
* @see javax.crypto.spec.PBEKeySpec
*/
public static final String PBE_WITH_MD5_AND_DES = "PBEWithMD5AndTripleDES";

private static byte[] salt = { (byte) 0xA9, (byte) 0x9B, (byte) 0xC8,
(byte) 0x32, (byte) 0x56, (byte) 0x35, (byte) 0xE3, (byte) 0x03 };
/** Number of interaction used to prepare the parameter to the ciphers. */
private static final int INTERACTION = 19;
/**
*

*
Create the key

*
Prepare the parameter to the ciphers

*
Create the ciphers

*
Encode the string into bytes using utf-8

*
Encrypt

*
Encode bytes to base64 to get a string

*

*
* @param secret
* The password to be decrypted.
* @return a plain password.
* @throws Exception
* a generic exception caused during the decrypt process.
*/
public static String encrypt(String plain,String passphrase) throws Exception {

KeySpec keySpec = new PBEKeySpec(passphrase.toCharArray(), salt, INTERACTION,1);
SecretKey key = SecretKeyFactory.getInstance(PBE_WITH_MD5_AND_DES)
.generateSecret(keySpec);
Cipher ecipher = Cipher.getInstance(key.getAlgorithm());
AlgorithmParameterSpec paramSpec = new PBEParameterSpec(salt,
INTERACTION);
ecipher.init(Cipher.ENCRYPT_MODE, key, paramSpec);
byte[] utf8 = plain.getBytes(UTF8);
byte[] enc = ecipher.doFinal(utf8);
return new sun.misc.BASE64Encoder().encode(enc);
}

/* @param secret
* The password to be decrypted.
* @return a plain password.
* @throws Exception
* a generic exception caused during the decrypt process.
*/
public static String decrypt(String secret,String passphrase) throws Exception {
KeySpec keySpec = new PBEKeySpec(passphrase.toCharArray(), salt,
INTERACTION,1);
SecretKey key = SecretKeyFactory.getInstance(PBE_WITH_MD5_AND_DES)
.generateSecret(keySpec);
byte[] dec = new sun.misc.BASE64Decoder().decodeBuffer(secret);
Cipher dcipher = Cipher.getInstance(key.getAlgorithm());
AlgorithmParameterSpec paramSpec = new PBEParameterSpec(salt,
INTERACTION);
dcipher.init(Cipher.DECRYPT_MODE, key, paramSpec);
byte[] utf8 = dcipher.doFinal(dec);
return new String(utf8, UTF8);
}

}
Example:To usse EncriptDecript
publilc class TestEncription{
public static final String SALT_PASSWORD = "wDC2mArpqswol8v6ba4leQ==";
public static void main(String [] args)
{
String password="abcd";
String encriptedPassword = ECSPassword.encrypt(password,SALT_PASSWORD);
String decriptedPassword = ECSPassword.decrypt(encriptedPassword ,SALT_PASSWORD);
}
Encription and Decription Using Javascript:

/*
* A JavaScript implementation of the RSA Data Security, Inc. MD5 Message
* Digest Algorithm, as defined in RFC 1321.
* Version 2.1 Copyright (C) Paul Johnston 1999 - 2002.
* Other contributors: Greg Holt, Andrew Kepert, Ydnar, Lostinet
* Distributed under the BSD License
* See http://pajhome.org.uk/crypt/md5 for more info.
*/
/*
* Configurable variables. You may need to tweak these to be compatible with
* the server-side, but the defaults work in most cases.
*/
var hexcase = 0; /* hex output format. 0 - lowercase; 1 - uppercase */
var b64pad = ""; /* base-64 pad character. "=" for strict RFC compliance */
var chrsz = 8; /* bits per input character. 8 - ASCII; 16 - Unicode */
var key = "example" /* key used for encryption */
/*
* These are the functions you'll usually want to call
* They take string arguments and return either hex or base-64 encoded strings
*/
function hex_md5(s){ return binl2hex(core_md5(str2binl(s), s.length * chrsz));}
function b64_md5(s){ return binl2b64(core_md5(str2binl(s), s.length * chrsz));}
function str_md5(s){ return binl2str(core_md5(str2binl(s), s.length * chrsz));}
function hex_hmac_md5(data) { return binl2hex(core_hmac_md5(key, data)); }
function b64_hmac_md5(data) { return binl2b64(core_hmac_md5(key, data)); }
function str_hmac_md5(data) { return binl2str(core_hmac_md5(key, data)); }
/*
* Perform a simple self-test to see if the VM is working
*/
function md5_vm_test()
{
return hex_md5("abc") == "900150983cd24fb0d6963f7d28e17f72";
}
/*
* Calculate the MD5 of an array of little-endian words, and a bit length
*/
function core_md5(x, len)
{
/* append padding */
x[len >> 5] = 0x80 << ((len) % 32); x[(((len + 64) >>> 9) << a =" 1732584193;" b =" -271733879;" c =" -1732584194;" d =" 271733878;" i =" 0;" olda =" a;" oldb =" b;" oldc =" c;" oldd =" d;" a =" md5_ff(a," d =" md5_ff(d," c =" md5_ff(c," b =" md5_ff(b," a =" md5_ff(a," d =" md5_ff(d," c =" md5_ff(c," b =" md5_ff(b," a =" md5_ff(a," d =" md5_ff(d," c =" md5_ff(c," b =" md5_ff(b," a =" md5_ff(a," d =" md5_ff(d," c =" md5_ff(c," b =" md5_ff(b," a =" md5_gg(a," d =" md5_gg(d," c =" md5_gg(c," b =" md5_gg(b," a =" md5_gg(a," d =" md5_gg(d," c =" md5_gg(c," b =" md5_gg(b," a =" md5_gg(a," d =" md5_gg(d," c =" md5_gg(c," b =" md5_gg(b," a =" md5_gg(a," d =" md5_gg(d," c =" md5_gg(c," b =" md5_gg(b," a =" md5_hh(a," d =" md5_hh(d," c =" md5_hh(c," b =" md5_hh(b," a =" md5_hh(a," d =" md5_hh(d," c =" md5_hh(c," b =" md5_hh(b," a =" md5_hh(a," d =" md5_hh(d," c =" md5_hh(c," b =" md5_hh(b," a =" md5_hh(a," d =" md5_hh(d," c =" md5_hh(c," b =" md5_hh(b," a =" md5_ii(a," d =" md5_ii(d," c =" md5_ii(c," b =" md5_ii(b," a =" md5_ii(a," d =" md5_ii(d," c =" md5_ii(c," b =" md5_ii(b," a =" md5_ii(a," d =" md5_ii(d," c =" md5_ii(c," b =" md5_ii(b," a =" md5_ii(a," d =" md5_ii(d," c =" md5_ii(c," b =" md5_ii(b," a =" safe_add(a," b =" safe_add(b," c =" safe_add(c," d =" safe_add(d," bkey =" str2binl(key);"> 16) bkey = core_md5(bkey, key.length * chrsz);
var ipad = Array(16), opad = Array(16);
for(var i = 0; i < hash =" core_md5(ipad.concat(str2binl(data))," lsw =" (x" msw =" (x">> 16) + (y >> 16) + (lsw >> 16);
return (msw <<>>> (32 - cnt));
}
/*
* Convert a string to an array of little-endian words
* If chrsz is ASCII, characters >255 have their hi-byte silently ignored.
*/
function str2binl(str)
{
var bin = Array();
var mask = (1 << i =" 0;">>5] = (str.charCodeAt(i / chrsz) & mask) << (i%32); return bin; } /* * Convert an array of little-endian words to a string */ function binl2str(bin) { var str = ""; var mask = (1 << i =" 0;">>5] >>> (i % 32)) & mask);
return str;
}
/*
* Convert an array of little-endian words to a hex string.
*/
function binl2hex(binarray)
{
var hex_tab = hexcase ? "0123456789ABCDEF" : "0123456789abcdef";
var str = "";
for(var i = 0; i <>>2] >> ((i%4)*8+4)) & 0xF) +
hex_tab.charAt((binarray[i>>2] >> ((i%4)*8 )) & 0xF);
}
return str;
}
/*
* Convert an array of little-endian words to a base-64 string
*/
function binl2b64(binarray)
{
var tab = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/";
var str = "";
for(var i = 0; i < triplet =" (((binarray[i">> 2] >> 8 * ( i %4)) & 0xFF) <<>> 2] >> 8 * ((i+1)%4)) & 0xFF) <<>> 2] >> 8 * ((i+2)%4)) & 0xFF);
for(var j = 0; j <> binarray.length * 32) str += b64pad;
else str += tab.charAt((triplet >> 6*(3-j)) & 0x3F);
}
}
return str;
}
Example:
call this method in javascript: by passing the string to encript:
hex_hmac_md5(pwd);