PIA Installation on IBM WebSphere Hangs on 20%
Problem:
When installing new PIA on IBM WebSphere, the installation hangs for several minutes at 20%
Solution:
Installation takes a long time to complete. If the timeout is not long enough, the installation may fail. (Applying MP5 appears to have resolved this). Else, manually increase the timeout.
Here are the steps to clone the PeopleSoft instance:
1. Backup the database (FSDEV) and restore it to another name (FSTST)
2. Clear the GUID field in the PSOPTIONS table in FSTST
3. Set up ODBC connection for FSTST
4. Map PS_HOME network drive and run Configuration Manager to set up shortcuts, PS/nVision path names
5. Create new application server domain for FSTST
6. Create new batch server for FSTST
7. Stop web server and setup new PIA for FSTST
8. Start application server, batch server, web server and log on to FSTST.
[amazon asin=0071664939&template=iframe image&chan=default] [amazon asin=1430237074&template=iframe image&chan=default] [amazon asin=0071787925&template=iframe image&chan=default]
Problem:
How can PeopleSoft profiles (fsdmo) that use BEA WebLogic as the web server be installed as a Windows Service?
Solution:
Navigate to the WebLogic domain directory (E:PSOFTFS900webservfsdmobin) and run installNTservice.cmd .
To uninstall, use UninstallNTservice.cmd :
Cd /d E:PSOFTFS900webservfsdmobin UninstallNTservice.cmd PIA UninstallNTservice.cmd WebLogicAdmin E:PSOFTFS900webservfsdmobin>UninstallNTservice.cmd PIA fsdmo-PIA removed. Press any key to continue . . . E:PSOFTFS900webservfsdmobin> E:PSOFTFS900webservfsdmobin>UninstallNTservice.cmd WebLogicAdmin fsdmo-WebLogicAdmin removed. Press any key to continue . . . E:PSOFTFS900webservfsdmobin>
Problem:
If the user that starts the IBM WebSphere web server logs off the system, the web server is shut down. A Windows service must be created to ensure that the web service(s) remain running.
Solution:
At Command Prompt, issue the following commands:
E: cd E:IBMWebSphereAppServerbin WASService.exe -add fsdev -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservfsdev -logFile E:IBMWebSphereAppServerlogsstartNodefsdev.log -restart true -startType automatic WASService.exe -add fsdmo -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPIA_fsdmo -logFile E:IBMWebSphereAppServerlogsstartNodefsdmo.log -restart true -startType automatic E:IBMWebSphereAppServerbin>cd E:IBMWebSphereAppServerbin E:IBMWebSphereAppServerbin>WASService.exe -add fsdev -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservfsdev -logFile E:IBMWebSphereAppServerlogsstartNodefsdev.log -restart true –startType automatic Adding Service: fsdev Config Root: E:PSOFTFS900webservfsdevconfig Server Name: server1 Profile Path: E:PSOFTFS900webservfsdev Was Home: E:IBMWebSphereAppServer Start Args: Restart: 1 IBM WebSphere Application Server V6.1 - fsdev service successfully added. E:IBMWebSphereAppServerbin> The “IBM WebSphere Application Server V6.1 – fsdev” service is created. Note that the log file is E:IBMWebSphereAppServerlogsstartNodefsdev.log E:>E: E:>cd E:IBMWebSphereAppServerbin E:IBMWebSphereAppServerbin>WASService.exe -add tramdmo -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPIA_tramdmo -logFile E:IBMWebSphereAppServerlogsstartNodetramdmo.log -restart true -startType automatic Adding Service: tramdmo Config Root: E:PSOFTFS900webservPIA_tramdmoconfig Server Name: server1 Profile Path: E:PSOFTFS900webservPIA_tramdmo Was Home: E:IBMWebSphereAppServer Start Args: Restart: 1 IBM WebSphere Application Server V6.1 - tramdmo service successfully added. To remove the service: cd E:IBMWebSphereAppServerbin WASService.exe -remove tramdmo E:>E: E:>cd E:IBMWebSphereAppServerbin E:IBMWebSphereAppServerbin>WASService.exe -add peoplebooks -serverName server1 -wasHome E:IBMWebSphereAppServer -profilePath E:PSOFTFS900webservPSOL_fsdmo -logFile E:IBMWebSphereAppServerlogsstartNodepeoplebooks.log -restart true -startType automatic Adding Service: peoplebooks Config Root: E:PSOFTFS900webservPSOL_fsdmoconfig Server Name: server1 Profile Path: E:PSOFTFS900webservPSOL_fsdmo Was Home: E:IBMWebSphereAppServer Start Args: Restart: 1 IBM WebSphere Application Server V6.1 - peoplebooks service successfully added. E:IBMWebSphereAppServerbin> To remove the service: cd E:IBMWebSphereAppServerbin WASService.exe -remove peoplebooks
Reference:
http://handly.blogspot.com/2008/05/setting-up-websphere-61-cluster-to.html
Setting up the WebSphere Node Manager as a Windows service
First, you need to set up the Node Manager on each physical server to run as a service and restart after a reboot:
Open a Command Window and go to the ..IBMWebSphereAppServerbin directory
Type in the following command (adjusted for your install paths):
WASService -add “IBM WebSphere Node Agent” -servername nodeagent -profilePath D:IBMWebSphereAppServerprofilesAppSrv01 -wasHome D:IBMWebsphereAppserver -logFile D:IBMWebSphereAppServerprofilesAppSrv01logsnodeagentstartNode.log -logRoot D:IBMWebSphereAppServerprofilesAppSrv01logsnodeagent -restart true -startType automatic
Problem:
After running the SYSAUDIT report, the following errors appear under Integration Broker Audits:
Operation Version Routing --------- ------- ------- QAS_CRASH_MSG VERSION_1 ~GEN_UPG~18727 QAS_CRASH_MSG VERSION_1 ~GEN~UPG~19278 2 Total Rows
Solution:
In PIA, navigate to PeopleTools > Integration Broker > Service Utilities > Service Administration.
Click on the Routing tab.
Expand Delete Duplicate Routings.
Click Search
The duplicate Routing Definitions appear. The second item will be checked.
Click Delete Tem…
Then click Search again. Ensure that no rows appear.
Problem:
After running the SYSAUDIT report, the following errors appear under Integration Broker Audits:
(IBRK-10): IB Routing referencing invalid handlers: Routing On Send Handler On Receive Handler - ------ --------------- ------------------ ~GENERATED~17288 ACK 1 Total Rows
Solution:
Log on to SQL Server Management Studio and run the following queries against fsdev:
select * from PSIBRTNGDEFN where ROUTINGDEFNNAME = '~GENERATED~17288' select * from PSIBRTNGDEFN where ONRCVHDLRNAME = 'ACK' select ONRCVHDLRNAME, count(*) from PSIBRTNGDEFN group by ONRCVHDLRNAME select * from PSSRVHDLRRCV_VW
The outputs were:
ROUTINGDEFNNAME EFFDT VERSION EFF_STATUS SENDERNODENAME RECEIVERNODENAME RTNGTYPE IB_SYNCHNONBLOCK IB_OPERATIONNAME VERSIONNAME CONNOVERRIDE CONNGATEWAYID CONNID LOGMSGDTLFLG ONSNDHDLRNAME ONRCVHDLRNAME GENERATED IB_LOCALIDFLG LASTUPDDTTM LASTUPDOPRID OBJECTOWNERID DESCR DESCRLONG ------------------------------ ----------------------- ----------- ---------- --------------------------------------------------------- ~GENERATED~17288 2005-10-21 00:00:00.000 6 I ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-30 11:38:38.000 VP1 PPT GENERATED NULL (1 row(s) affected) ROUTINGDEFNNAME EFFDT VERSION EFF_STATUS SENDERNODENAME RECEIVERNODENAME RTNGTYPE IB_SYNCHNONBLOCK IB_OPERATIONNAME VERSIONNAME CONNOVERRIDE CONNGATEWAYID CONNID LOGMSGDTLFLG ONSNDHDLRNAME ONRCVHDLRNAME GENERATED IB_LOCALIDFLG LASTUPDDTTM LASTUPDOPRID OBJECTOWNERID DESCR DESCRLONG ------------------------------ ----------------------- ----------- ---------- --------------------------------------------------------- ~GENERATED~17288 2005-10-21 00:00:00.000 6 I ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-30 11:38:38.000 VP1 PPT GENERATED NULL (1 row(s) affected) ONRCVHDLRNAME COUNT(*) ------------------------------ ----------- 1500 ACK 1 (2 row(s) affected) IB_OPERATIONNAME ONRCVHDLRNAME DESCR ------------------------------ ------------------------------ --------------------------- CREATE_WORKLIST_ITEM OnAckForMarkedWorkedResp Create worklist entry (1 row(s) affected)
On fsdmo, ran the following queries:
select * from PSIBRTNGDEFN where ROUTINGDEFNNAME = '~GENERATED~17288' select * from PSIBRTNGDEFN where ONRCVHDLRNAME = 'ACK' select ONRCVHDLRNAME, count(*) from PSIBRTNGDEFN group by ONRCVHDLRNAME select * from PSSRVHDLRRCV_VW
The outputs were:
ROUTINGDEFNNAME EFFDT VERSION EFF_STATUS SENDERNODENAME RECEIVERNODENAME RTNGTYPE IB_SYNCHNONBLOCK IB_OPERATIONNAME VERSIONNAME CONNOVERRIDE CONNGATEWAYID CONNID LOGMSGDTLFLG ONSNDHDLRNAME ONRCVHDLRNAME GENERATED IB_LOCALIDFLG LASTUPDDTTM LASTUPDOPRID OBJECTOWNERID DESCR DESCRLONG ------------------------------ ----------------------- ----------- ---------- --------------------------------------------------------- ~GENERATED~17288 2005-10-21 00:00:00.000 1 A ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-18 16:04:16.000 PPLSOFT PPT GENERATED NULL (1 row(s) affected) ROUTINGDEFNNAME EFFDT VERSION EFF_STATUS SENDERNODENAME RECEIVERNODENAME RTNGTYPE IB_SYNCHNONBLOCK IB_OPERATIONNAME VERSIONNAME CONNOVERRIDE CONNGATEWAYID CONNID LOGMSGDTLFLG ONSNDHDLRNAME ONRCVHDLRNAME GENERATED IB_LOCALIDFLG LASTUPDDTTM LASTUPDOPRID OBJECTOWNERID DESCR DESCRLONG ------------------------------ ----------------------- ----------- ---------- --------------------------------------------------------- CREATE_WORKLIST_ITEM 2005-10-21 00:00:00.000 1 I ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-23 11:11:56.000 PPLSOFT Create worklist entry NULL ~GENERATED~17288 2005-10-21 00:00:00.000 1 A ~~ANY~~ PSFT_EP R N CREATE_WORKLIST_ITEM V1 N 2 ACK Y 2 2008-12-18 16:04:16.000 PPLSOFT PPT GENERATED NULL (2 row(s) affected) ONRCVHDLRNAME ------------------------------ ----------- 1513 ACK 2 (2 row(s) affected) IB_OPERATIONNAME ONRCVHDLRNAME DESCR ------------------------------ ------------------------------ --------------------------- CREATE_WORKLIST_ITEM ACK CREATE_WORKLIST_ITEM OnAckForMarkedWorkedResp Create worklist entry (2 row(s) affected)
Note that in PSSRVHDLRRCV_VW, there is a new row for ACK.
1. The simplest solution, however, is to delete the offending routing, ~GENERATED~17288.
2. In PIA, navigate to Integration Broker > Service Utilities > Service Administration. Select the Routings tab, and open the Delete section. Enter ~GENERATED~17288 into the Routing Name field and click Search. Check Select and then click Delete.
Under Results, the following message appears: Unable to delete. Routing belongs to a restricted service.
3. One way to resolve this is to change the restricted service to unrestricted. Navigate to Integration Broker > Configuration > Service Configuration. Click the Restricted Services tab, and search for PT_WORKLIST. Uncheck Restricted, and then Save.
4. Determine the field that is used as the lookup. Navigate to Integration Broker > Integration Setup > Routings. In the Find an Existing Value tab, in Routing Name, enter ~GENERATED~17288 and click Search.
5. Type Ctrl + J and note the Page name: IB_ROUTINGDEFN
6. On GL-WEB-APP, launch Application Designer and click Insert Definitions into Project. Choose Page and enter IB_ROUTINGDEFN. Choose IB_ROUTINGDEFN and click Close.
7. Double-click IB_ROUTINGDEFN. Right-click on the OnReceive Handler field and choose View Definition. On the ONRCVHDLRNAME field, right click and choose Record Field Properties. Click the Edits tab and note the Prompt Table: PSSRVHDLRRCV_VW.
8. In Management Studio, for the fsdev database, expand the Views navigator and locate PSSRVHDLRRCV_VW. Right click on PSSRVHDLRRCV_VW, choose Script View as, choose CREATE To, and click New Query. Note the command to create the view:
CREATE VIEW [dbo].[PSSRVHDLRRCV_VW] (IB_OPERATIONNAME, ONRCVHDLRNAME, DESCR) AS SELECT IB_OPERATIONNAME , HANDLERNAME , DESCR FROM PSOPRHDLR WHERE HANDLERID = 'RECV'
9. In PIA, navigate to Integration Broker > Integration Setup > Service Operations. In the Find Service Operation tab, in the Service Operation field, enter CREATE_WORKLIST_ITEM. Then click Search. Click CREATE_WORKLIST_ITEM to view it.
10. If the record is restricted, you will not be able to enter new Handlers. See step 3 above to resolve.
11. Click the Handler tab. Add a new Handler with the following information:
Name: ACK
Type: OnReceive
Implementation: Application Class
Status: Active
Click Details and add the following information:
Package Name: PT_WF_WORKLIST
Path: : [that is, only a colon must be entered]
Class ID: OnAckForMarkedWorkedResp
Method: OnAckReceive
12. Click Save.
Problem:
After running the SYSAUDIT report, the following errors appear under Integration Broker Audits:
(IBRK-08): IB Routing referencing invalid service operation:
Routing Operation Version
– —— ——— ——-
~GEN~UPG~24567 IB_INST_VER_ASYNC_MSG VERSION_1
~GEN~UPG~17626 IB_INST_VER_RESP_MSG VERSION_1
2 Total Rows
Solution:
Delete the above two routings:
1. Query records that appear in Integration Broker Audit section IBRK-08
select * from PSIBRTNGDEFN where ROUTINGDEFNNAME = ‘~GEN~UPG~24567’ or ROUTINGDEFNNAME = ‘~GEN~UPG~17626’
2. Launch PIA and search for the page that contains these values. Navigate to Integration Broker > Integration Setup > Routings. In the Find an Existing Value tab, in the Routing Name begins with field, enter ~GEN~UPG~24567. Click Search. It returns ‘No matching values were found.’ Then click the Add a New Value tab. The record appears.
3. Type Ctrl + J to get the page information. Note the Page (IB_ROUTINGDEFN).
4. On GL-WEB-APP, launch Application Designer. Insert Definitions into Project. Choose Definition Type Page and enter IB_ROUTINGDEFN in the Name field. Then press Enter. Insert the IB_ROUTINGDEFN page.
5. Right-click the Service Operation field, and choose Field Definition. In the Record Definition, choose Record Field Properties. Click the Edits tab and note the Prompt Table: PSOPERATION.
select * from PSOPERATION
select * from PSOPERATION where IB_OPERATIONNAME = ‘IB_INST_VER_RESP_MSG’ or IB_OPERATIONNAME = ‘IB_INST_VER_ASYNC_MSG’
6. Delete the two routings above (~GEN~UPG~24567 and ~GEN~UPG~17626). In PIA, navigate to PeopleTools > Integration Broker > Service Utilities > Service Administration. Select the Routings tab, and expand the Delete section. For each routing name (~GEN~UPG~24567 and ~GEN~UPG~17626), enter the Routing Name and click Search. The routing name appears. Check Select and then click Delete.
Reference:
E-IB: IBRK-xx SYSAUDIT exceptions after applying Maintenance Pack(s) (Doc ID 654766.1)
EFSCM: Orphan routing issue for FSCM9 customers after upgrading to 8.49 tools (Doc ID 661088.1)
[amazon asin=0071664939&template=iframe image&chan=default] [amazon asin=1430237074&template=iframe image&chan=default] [amazon asin=0071787925&template=iframe image&chan=default]
Problem:
After running the SYSAUDIT report, the following error appears under Integration Broker Audits:
(IBRK-05): Service Operation with missing service: Service Operation Service - ---------------- ------- PV_ORDER_XCBL3 PV_ORDER_XCBL3 1 Total Rows
Solution:
1. Check the “Data Management” PeopleBook, under the “Ensuring Data Integrity” section for information on resolving Integration Broker errors.
2. Check the Service Operations (PSOPERATION) and Service’s (PSSERVICE) tables in the fsdmo and fsdev databases.
select * from PSOPERATION where IB_SERVICENAME like 'PV_ORDER%' select * from PSSERVICE where IB_SERVICENAME like 'PV_ORDER%'
Note that PV_ORDER_XCBL3 appears in the PSOPERATION table in fsdev, but not in the PSSERVICE table. Note also that PV_ORDER_XCBL3 appears only in fsdev, but not in fsdmo.
Therefore, backup the row containing PV_ORDER_XCBL3 and then delete the row from the PSOPERATION table in the fsdev instance:
select * from PSOPERATION where IB_SERVICENAME = 'PV_ORDER_XCBL3' delete from PSOPERATION where IB_SERVICENAME = 'PV_ORDER_XCBL3'
3. Deleting the record introduced an IBRK-06 error on the SYSAUDIT report. To restore the data that was deleted:
insert into PSOPERATION
(IB_OPERATIONNAME, VERSION, DEFAULTVER, RTNGTYPE, IB_USERPWDREQ, IB_SERVICENAME, IB_ALIASNAME, LASTUPDDTTM,
LASTUPDOPRID, OBJECTOWNERID, DESCR, DESCRLONG)
values
('PV_ORDER_XCBL3', 1, 'VERSION_1', 'A', 'N', 'PV_ORDER_XCBL3', '', '2008-12-11 16:47:00.000', 'SVP1',
'DPV', 'xCBL Order', NULL)
4. In PIA, navigate to Integration Broker > Service Utilities > Service Administration. Click the Service Operations tab. Expand Delete and in the Service Operation field, enter PV_ORDER_XCBL3. Check Select, and then click Delete.
Under Results, ‘Successful delete’ appears.
After rerunning SYSAUDIT, the exception no longer appears.
Problem:
When running the ZFSCM900_DROP5_PRE_DMS step to drop unneeded views, many steps complete in error:
SQL Error. Error Position: 0 Return: 601 - [Microsoft][SQL Native Client][SQL Server] Cannot drop the view 'PS_XXXX_XX_XXXX_VW', because it does not exist or you do not have permission.
The end of the log file states ‘Successful Completion’.
Solution:
This is expected behaviour. The MP5 documentation states:
Dropping Views
In this step, if you encounter an error, due to some tables and views previously dropped or already do not exist in the database, please ignore the error, mark this step as Complete and continue with the Maintenance Pack installation. Note that the script log would still mark as Successful completion.
Problem:
When installing BEA WebLogic from the command line, the following error appears:
Step 1 – Installation preparation.
WebLogic was unexpected at this time.
Solution:
Remove spaces from folder name:
Rename E:stagingCDImagesBEA WebLogic to E:stagingCDImagescd849-WebLogic.
Recent Comments