Thursday, June 30, 2016

SES: - Validation failed : Call back URL does not match with Target Location URL (262,1313)

When running validation on the Search Instance “Call Back Properties”, the validation fails with the error:




The cause of the error is that the Search Instance “Call back URL” and the Integration Broker “Target Location URL” are not the same – both the URLs need to have the exact same value or they will not pass validation, resulting in the “Call back URL does not match with Target Location URL” error.
Compare the Search Framework “Call Back” URL value to the Integration Broker “Target Location” URL as follows:
Check Integration Broker “Target Location” URL:
  1. Navigate to PeopleTools -> Integration Broker -> Configuration -> Service Configuration
  2. Click “Setup Target Locations”
  3. Check the “Target Location”
  4. Get the URL mentioned in the Target Location field.
Update the Call Back Properties Section
  1. Navigate to PeopleTools, Search Framework, Administration, Search Instance
  2. Go to the Call Back Properties section and update the URL value in the “URL” field.
  3. Hit Save.
After you update the URLs to be the same value, then rerun the Search Instance “Call Back Validation” to verify it is successful.

Useful Stuff for PeopleSoft Upgrade (PSPROJECTITEM)


Useful Stuff for PeopleSoft Upgrade:
*******************************

Projects
  • PSPROJECTDEFN — Project header table
  • PSPROJECTITEM — Definitions in the project
Fields
  • PSDBFIELD — Fields in the system
  • PSXLATITEM — Translate Values
Records
  • PSRECDEFN — Record header table (record types)
  • PSRECFIELD — Fields in the record (subrecords not expanded)
  • PSRECFIELDALL — Fields in the record (subrecords expanded)
  • PSKEYDEFN — Indexes
  • PSTBLSPCCAT — Tablespaces
  • PSRECTBLSPC — Records’ tablespace assignments
Pages
(Note: Pages still have the name panels in the PeopleTools table names)
  • PSPNLDEFN — Page header table
  • PSPNLFIELD — Page controls (field types/FIELDTYPE)
  • PSPNLHTMLAREA — Static HTML Areas on Pages
  • PSPNLCNTRLDATA — stores additional attributes for Page controls
  • PSPNLFIELDEXT — stores additional attributes for Page controls
  • PSPTPNLRTEDITOR — new PeopleTools 8.50 table that stores attributes relating to the rich-text editor for long character fields.
Components
(Note: Components still have the name panel group in the PeopleTools table names)
  • PSPNLGRPDEFN — Component header table
  • PSPNLGROUP — Pages in the components
Component Interface
  • PSBCDEFN — header record; one row for each component interface
  • PSBCITEM — one row for each property
Menus
  • PSMENUDEFN — Menu header table
  • PSMENUITEM — Items (components) on the menu
Security
  • PSCLASSDEFN — Permission List header table
  • PSAUTHITEM — Menu items granted security by permission lists
  • PSROLEDEFN — Role header table
  • PSROLECLASS — Permission Lists in roles
  • PSOPRDEFN — User ID header table
  • PSROLEUSER — Roles granted to users
  • PSAUTHBUSCOMP — Access to Component Interfaces
Process Scheduler
  • PS_PRCSDEFN — Process Definition Header
  • PS_PRCSDEFNGRP — Process Group
  • PS_PRCSDEFNPNL — Component
  • PS_PRCSJOBDEFN — Job Header
  • PSPRCSRQST — Process Request Instances
  • PS_PRCSJOBITEM — Job Processes
Portal
  • PSPRSMDEFN — Content References and Folders
  • PSPRUHTABPGLT — Portal User HP Tab Pagelet
  • PSPRUHDEFN — Homepage definition (from here)
  • PSPRUHTAB — Homepage Tab (from here)
  • PSWEBPROFNVP — Web Profile Settings
Change Control
  • PSCHGCTLHIST — shows history of locked definitions with project name, incident, and description
  • PSCHGCTLLOCK — shows definitions that are currently locked
Application Engine
  • PSAEAPPLDEFN — header record; 1 row per app engine
  • PSAEAPPLSTATE — state records assigned to app engines
  • PSAEAPPLTEMPTBL — temp tables assigned to app engines
  • PSAESECTDEFN — sections
  • PSAESTEPDEFN — steps
  • PSAESTEPMSGDEFN
  • PSAESTMTDEFN — actions (action types)
HTML Definitions
  • PSCONTDEFN — header record; last update time, etc.
  • PSCONTENT — stores actual text in the HTML definition
SQL Definitions
  • PSSQLDEFN — header record; last update time, etc.
  • PSSQLTEXTDEFN — stores actual text in the SQL definition
File Layout Definitions
  • PSFLDDEFN — header record; last update time, etc.
  • PSFLDSEGDEFN — stores the segments for each layout
  • PSFLDFIELDDEFN — stores the fields for each layout
Workflow
  • APPR_RULE_DETL – Approval Rule Defn Details
  • APPR_RULE_FIELD – Approval Rule Defn Route Cntl
  • APPR_RULE_AMT – Approval Rule Amounts
  • RTE_CNTL_LN – Route Control Profile Line
  • RTE_CNTL_RUSER – RoleUser Route Cntl Profiles
  • RTE_CNTL_TYPE – Route Control Type
  • RTE_CNTL_HDR – Routing Control Type
  • PSWORKLIST — list of work items for each user
  • PS_WF_INSTSTATUS — description of the status
Timings
  • BAT_TIMINGS_LOG
  • BAT_TIMINGS_DTL
  • BAT_TIMINGS_FN

Thanks to Shyam:


Field Name
Values
PROJECTNAME
Name of the Project in Upper case
OBJECTTYPE
0=Record
1=Index
2=Field
3=Field Format
4=Translate Values
5=Page
6=Menu
7=Component
8=Record PC
9=Menu PC
10=Query View
11=Tree Structures
12=Trees
13=Access Group
14=Colors
15=Styles
16=Business Pro Map
17=Business Process
18=Activity
19=Roles
20=Process Definitions
21=Server Definitions
22=Process Type Definitions
23=Job Definitions
24=Recurrence Definitions
25=Message Catalog Entry
26=Dimensions
27=Analysis Model
28=Cube Template
29=Business Interlink
30=SQL
31=File Layout Definitions
32=Component Interface
33=App Engine Programs
34=App Engine Sections
35=Message Nodes
36=Message Channels
37=Messages
38=Approval Rule Sets
39=Message PC
40=Subscription PC
41=Not Used
42=Componenten Interface PC
43=Application Engine PC
44=Page PC
45=Page Field PC
46=Component PC
47=Component Record PC
48=Component Record Field PC
49=Image
50=Style Sheet
51=HTML
52=File Reference Objects
53=Permission List
54=Portal Registry Definitions
55=Portal Registry Structure
56=URL Definitions
57=Application Package
58=Application Package PC
59=Portal Registry User Homepages
60=Analytic Types
61=Archive Templates
62=XSLT
63=Portal Reg User Favorites
64=Mobile Page
65=Relationships
66=Component Interface Property PC
67=Optimization Model
68=File Reference
69=File Type Codes
70=Archive Object Definitions
71=Archive Templates
72=Diagnostic Plug-In
73=Analytic Models
74=Not Used
75=Java Portlet User Preferences
76=WSRP Remote Producer
77=WSRP Remote Portlet
78=WSRP Cloned Portlet Handle
79=Services
80=Service Operations
81=Service Operation Handlers
82=Service Operation Versions
83=Routing Defnitions
84=IB Queues
85=XMLP Template Defn
86=XMLP Report Defn
87=XMLP File Defn
88=XMLP Data Src Defn
OBJECTID1
OBJECTID1
OBJECTVALUE1
Object Value 1
OBJECTID2
OBJECTID2
OBJECTVALUE2
Object Value 2
OBJECTID3
OBJECTID3
OBJECTVALUE3
Object Value 3
OBJECTID4
OBJECTID4
OBJECTVALUE4
Object Value 4
NODETYPE
Node Type
SOURCESTATUS
0=Unknown 
1=Absent 
2=Changed 
3=Unchanged 
4=*Changed 
5=*Unchanged 
6=Same
TARGETSTATUS
0=Unknown 
1=Absent 
2=Changed 
3=Unchanged 
4=*Changed 
5=*Unchanged 
6=Same
UPGRADEACTION
0=Copy
1=Delete
2=None
3=Copy Properties
TAKEACTION
0=No
1=Yes
COPYDONE
0=No
1=Yes

Thursday, June 16, 2016

Weblogic Console Password Recovery - Linux

Procedure to know the console password - LINUX

Step1. Run setEnv.cmd/setEnv.sh from your Location@ E:\psft\PSHDEV\webserv\peoplesoft\bin directory to set necessary domain environment variables in command prompt.

Step2. Place\Create the below script “decrypt.py” file in E:\psft\PSHDEV\webserv\peoplesoft\security directory and paste the following code into it:

import os
import weblogic.security.internal.SerializedSystemIni
import weblogic.security.internal.encryption.ClearOrEncryptedService

def decrypt(domainHomeName, encryptedPwd):
    domainHomeAbsolutePath = os.path.abspath(domainHomeName)
    encryptionService = weblogic.security.internal.SerializedSystemIni.getEncryptionService(domainHomeAbsolutePath)
    ces = weblogic.security.internal.encryption.ClearOrEncryptedService(encryptionService)
    clear = ces.decrypt(encryptedPwd)
    print "Decrypted Password:" + clear


try:
    if len(sys.argv) == 3:
        decrypt(sys.argv[1], sys.argv[2])
    else:
        print "INVALID ARGUMENTS"
        print " Usage: java weblogic.WLST decryptPassword.py <DOMAIN_HOME> <ENCRYPTED_PASSWORD>"
        print " Example:"
        print "java weblogic.WLST decryptPassword.py <domain_path> <encrypted password>"

except:
    print "Unexpected error: ", sys.exc_info()[0]
    dumpStack()

    raise

Step3. Execute the command “java weblogic.WLST decrypt.py <DOMAIN_PATH> <ENCRYPTED PASSWORD> “from the location E:\psft\PSHDEV\webserv\peoplesoft\security 

Ex: java weblogic.WLST decrypt.py /data/PSOFT/HCMDEV/webserv/HCMDEV/ {AES}dokmw8rm1/eCBZ8QiOr3Q+vkNyqEVlYb+b+CV1mR75A=

Note: Take the encrypted password from “boot.properties” file and paste it when prompted for password in the above step.
Location @ E:\psft\PSHDEV\webserv\peoplesoft\servers\PIA\security\ boot.properties


Friday, June 3, 2016

Can You Use MS Office 365 with PeopleSoft?

One of our PeopleSoft Client - The business would like to switch from normal MS Office to Office 365 for some reason!!

Details from oracle support:
**********************************
June 6, 2014. Microsoft has released a new licensing option for their Office suite, Office 365.  There are a number of licensing options for businesses, with different billing options and numbers of users.  Some of the options include the desktop versions of various Office products, some do not.  
For quite some time PeopleSoft has enabled the use of several of the Office desktop products such as Excel with PeopleSoft nVision, and Word with several PeopleSoft applications.  PeopleSoft’s certification of these Office products depends on a local installation of the desktop application.  If PeopleSoft customers would like to subscribe to Office 365 instead of purchasing an Office desktop license, they may do so as long as they select a subscription which includes access to the desktop version of the applications.  A good comparison of business options for Office 365 can be found on Microsoft’s website.
Oracle plans to continue to certify new Office desktop products like Office 2013 with PeopleSoft applications on a timely basis.  As Microsoft releases updated versions, Oracle will promptly evaluate and certify these new versions.  For information on the latest Office 2013 certifications with PeopleTools 8.53, please refer to the following Tech Update:
First Certifications of Office 2013 Now Complete for PeopleSoft Note:1628388.1


Reference DocID:
**********************
Tech Update – Support of Microsoft Office 365 with PeopleSoft (Doc ID 1680324.1)