Monday 30 January 2017

Using a PUM Instance in the Cloud to Apply Maintenance to On-Premise targets


To use a PUM instance in the Oracle Compute Cloud to apply maintenance to an on-premise target, execute the following steps:

1) Initiate deployment in Oracle Cloud Marketplace.
2) Configure the instance for the Microsoft Windows server.
3) Permit access for the Samba shared drives in Oracle Compute Cloud service instances .
4) Permit access for Oracle database ports in Oracle Compute Cloud Service instances.
5) Access the Samba share drive from Microsoft Windows VM for PeopleTools client deployment.
6) Configure your instance for Remote Desktop Protocol (RDP) access .
7) Log in to your instance using RDP.
8) Deploy the PeopleTools client for PeopleSoft Update Manager on a Microsoft Windows host or VM.
9) Upload the on-premise environment to PUM in Oracle Compute Cloud Service.
10) Create a change package.
11) Run the Change Assistant job for the source steps only.
12) Copy the change package from Oracle Compute Cloud Service to on-premise.
13) Run the Change Assistant job for the target steps only.

Tuesday 24 January 2017

Error "java.lang.NegativeArraySizeException" while starting HTTPS 12c server

Error "java.lang.NegativeArraySizeException" while starting HTTPS 12c server


I got below error 
./startComponent.sh ohs1
Starting system Component ohs1 ...

Initializing WebLogic Scripting Tool (WLST) ...

Welcome to WebLogic Server Administration Scripting Shell

Type help() for help on available commands

Reading domain from /oracle/webserver/user_projects/domains/base_domain


Error: java.lang.NegativeArraySizeException

Exiting WebLogic Scripting Tool.

To fix it we need to go to 
cd $HOME
 there will be a hidden folder .wlst
Inside it file  nm-key-base_domain.props got corrupted, so delete it and re-run

Worked after that.

Tuesday 10 January 2017

Peoplesoft Health Center

Peoplesoft Health Center

Understanding PeopleSoft Health Center

The PeopleSoft Health Center enables you to monitor the health of your PeopleSoft application by providing real-time analysis of performance and load. The PeopleSoft Health Center can be used for self-monitoring of an application or for multiple systems in a single monitoring system. Additionally, PeopleSoft Health Center provides alerts that enable you to attend to immediate performance issues.
In PeopleTools 8.55, both the PPM (PeopleSoft Performance Monitor) agent and the JMX (Java Management Extensions) agents are enabled by default. While the PPM agent is required for component registration, the JMX agent is required for real-time monitoring in PeopleSoft Health Center.
On initial access of PeopleSoft Health Center, Health Center completes the following tasks:
1.       Registers a component or domain with the PPM agent.
2.       Authenticates the registered component or domain using JMX agents.
PeopleSoft Health Center presents monitoring data in the form of a dashboard (Application dashboard), which includes the following information:
  General self-monitoring health information.
  Alerts of potential performance issues.
  Health status of participating components or domains.



  Log files.
The health status, performance and load details of each component or domain are presented in separate dashboards that can be accessed from the Application dashboard.
Note: You cannot configure the content and layout of dashboards.
PeopleSoft Health Center allows you to choose which component or domain you want to be monitored. You make this selection on the initial access of Health Center.
All log files created and updated by Tuxedo domains and web server are available on PeopleSoft Health Center. Each domain or server level dashboard lists log files associated with the domain or server.
Each log file is represented as a tile with the following information:
File name.
File size.
Last modified date
------------------------------------------------------------------------------------------------------------------------------------------

Configuration of Peoplesoft Health Center 

-          Configure Integration Broker.
-          Set the Performance Collator property.
-          Enable the PPM agents.
-          Enable and configure the JMX agents.
-          (Optional) Set the Mobile Application Platform session time-out.

Configure Integration Broker.

1 . Make sure IB is working fine, Local node is pinging and in service configuration REST service is having correct URL.

Set the Performance Collator property.

To set the Performance Collator property:
1.       Run PSADMIN and choose the domain that you want to configure.
2.       Select 4) Configure this domain.
3.       To configure the domain, the domain needs to be shut down.
4.       Enter y to the question: Do you want to continue (y/n).
5.       Toggle 10) Perf Collator to set it to Yes.
6.       Select 14) Load config as shown.
7.       Restart the domain.

Enable the PPM agents

To enable the PPM agents:
1.       Run PSADMIN and choose the domain that you want to configure.
2.       Select 6) Edit configuration/log files menu.
3.       Select 1) Edit domain configuration file.
4.       In the configuration file, in the PSTOOLS section, locate the EnablePPM Agent parameter and set the value to 1.
5.       If you set the value to 0, the PPM agents are disabled.
6.       Save the changes you made in the configuration file.
7.       Restart the domain.

Enable and configure the JMX agents

To enable JMX agents:
1.       Run PSADMIN and choose the domain that you want to configure.
2.       Select 6) Edit configuration/log files menu.
3.       Select 1) Edit domain configuration file.
4.       In the configuration file, in the PSTOOLS section, locate the following parameters and set the values:
5.       Enable Remote Administration - Set the value to 1.
6.       Remote Administration Port - Set the value to 10100.
7.       Remote Administration Userid - Enter a user ID, for example, admin.
8.       Remote Administration Password - Enter an encrypted password. To encrypt the password, use the PSCipher utility.
9.       For more information on encrypting passwords, see Encrypting Passwords Using the PSCipher Java Utility.
10.   Save the changes you made in the configuration file.
11.   Restart the domain.

(Optional) Set the Mobile Application Platform session time-out.

To modify the session time-out on the MAP Security page:
1.       Navigate to select PeopleTools, then select Mobile Application Platform, then select MAP Administration, then select MAP Security.
2.       In the Session Timeout field, replace the default 5 minutes with an appropriate number, such as 60 minutes.
3.       Click Save.

Issues


Issue I was facing that whenever I was navigating to Health center and clicking the link it was giving broken signon page and issue as below :-
Your PeopleSoft connection has expired. For increased security on this site, connections are expired after 0 minutes of inactivity. Your PeopleSoft session has expired. Close all browser windows before logging in again. If this is your only active PeopleSoft session, click the Sign In link to sign in again.
Sign in to PeopleSoft

Later When I was navigating to Mobile application platform there was Layout designer click that
You will find PT_MAPFLUID click that and click later on View Initialization URL and I was not getting URL with domain name. I changed domain name in Gateway URL,Service configuration URL.
Later go to map security increase time to 30 min
Then Map File synchronization and do cleanup and synchronization. Later URL will start working.
Weserver password will be same as weblogic console.
System – Passw0rd
Appserver and psunx password we need to change in Main menu>Peopletools>Performance Monitor>administration>JMX users
Make changes in cfg files too using psadmin utility.
User id and password kept is admin – Passw0rd
----------------------------------The END---------------------------------------------
Userid and password is not correct and one java related issue while clicking webserver domain in health center side.

Solution wa sto update the encrypted password in backed for system and admin.

select * from PS_PTPMJMXUSER;

Update PS_PTPMJMXUSER set PTPMJMXPSWD='{V1.1}7m4OtVxxxxxxx' where PM_AGENTID=19;



The purge process did not run because the Oprid configured to start the Process Scheduler did not have the required permissions to run the purge process.

  Purge process - Required permissions The PeopleSoft Oprid used to start the Process Scheduler, as defined in the Scheduler's psprcs.cf...