Friday 23 August 2019

General Linux commands to get Hardware info

Task display : CPU Information
$ cat /proc/cpuinfo
Task: Display Free and used Memory Information
$ free -m
Task: Display partition information
# fdisk -l
Task: Display file system disk space usage
# df -H
OR
# df -h
Task: Estimate file space usage
# du
Task: List PCI devices
# lspci
Task: List USB devices
# lsusb
Task display : More Information
$ lsdev

APP-VERSION ENGINE

PROPER PROCEDURE for APP-VERSION ENGINE


The proper steps to follow when running VERSION AE are:

1. Shutdown all Application Servers, Process Schedulers, and
other PeopleTools clients.

2. *critical step* Ensure that all Application Designer session
are logged out and shut down. If necessary, shutdown and restart
the database and its communication software.

3. Establish the proper shell environment. Normally this
includes loging in as your PeopleSoft id, and
changing to the PSFT bin directory (i.e. cd $PS_HOME/bin)
setting the PS_SERVER_CFG environment variable (export
PS_SERVER_CFG=$PS_HOME/appserv/prcs/<dbna me>/psprcs.cfg)


4. Execute the command from a command line:
psae -CD <dbname> -CT <dbtype> -CO <oprid> -CP <pswd> -R
INSTALL [where INSTALL is a valid run control] -AI VERSION
(Note: INSTALL must be a valid run control for <oprid>)

5. Issue the following SQL and archive the output to ensure that
the program ran (all the versions should be 1).
SELECT * FROM PSVERSION ORDER BY VERSION DESC;

6. Clear the cache files from the Application Server, Web
Servers, Process Schedulers, and Client machines.

7. Restart the system per normal operational procedures. There
will be expected performance impact as the system rebuilds its cache
files.

8. Over the course of the following days, every 4 hours or so,
rerun the SQL from Step #5. You should observe a gradual growth of
the versions, typically in the order of dozens per day. The version
associated with SYS should always be equal to or greater than all
other values in the table.

Tuesday 13 August 2019

PSFT_CUSTOMIZATIONS.YAML file for SMTP

---
appserver_domain_list:
  "%{hiera('appserver_domain_name')}":
    os_user:         "%{hiera('domain_user')}"
    ps_cfg_home_dir: "%{hiera('ps_config_home')}"
    template_type:   "%{hiera('appserver_template')}"

    db_settings:
      db_name:        "%{hiera('db_name')}"
      db_type:        "%{hiera('db_platform')}"
      db_opr_id:      "%{hiera('db_user')}"
      db_opr_pwd:     "%{hiera('db_user_pwd')}"
      db_connect_id:  "%{hiera('db_connect_id')}"
      db_connect_pwd: "%{hiera('db_connect_pwd')}"

    config_settings:
      Domain Settings/Domain ID:    "%{hiera('appserver_domain_name')}"
      PSAPPSRV/Min Instances:       2
      PSAPPSRV/Max Instances:       2
      PSAPPSRV/Max Fetch Size:      15000
      Security/DomainConnectionPwd: "%{hiera('domain_conn_pwd')}"
      JOLT Listener/Port:           "%{hiera('jolt_port')}"
      JOLT Listener/Address:        0.0.0.0
      Workstation Listener/Port:    "%{hiera('wsl_port')}"
      SMTP Settings/SMTPServer=dfdfd
      SMTP Settings/SMTPPort=25
      SMTP Settings/SMTPServer1=abc
      SMTP Settings/SMTPPort1=0
      SMTP Settings/SMTPSender=PeopleSoft@peoplesoft.com
      SMTP Settings/SMTPBlackberryReplyTo=
      SMTP Settings/SMTPSourceMachine=aaa
      SMTP Settings/SMTPCharacterSet=UTF-8
      SMTP Settings/SMTPEncodingDLL=dfdfd
      SMTP Settings/SMTPGuaranteed=0
      SMTP Settings/SMTPTrace=0
      SMTP Settings/SMTPSendTime=0
      SMTP Settings/SMTPUseSSL=N
      SMTP Settings/SMTPSSLPort=465
      SMTP Settings/SMTPClientCertAlias=dfdfd
      SMTP Settings/SMTPUseSSL1=N
      SMTP Settings/SMTPSSLPort1=465
      SMTP Settings/SMTPClientCertAlias1=dfdfd 

    feature_settings:
      PUBSUB:        "Yes"
      QUICKSRV:      "No"
      QUERYSRV:      "No"
      JOLT:          "Yes"
      JRAD:          "No"
      WSL:           "Yes"
      DBGSRV:        "No"
      RENSRV:        "No"
      MCF:           "No"
      PPM:           "Yes"
      PSPPMSRV:      "Yes"
      ANALYTICSRV:   "No"
      SERVER_EVENTS: "Yes"
      DOMAIN_GW:     "No"

Error: Evaluation Error: Error while evaluating a Function Call, bad decrypt at /etc/puppet/modules/pt_profile/manifests/pt_pia.pp:49:22 on node

If you get this error while running psft_customizations.yaml file all you have to do is go tp $Base/dpk/puppet/production/data folder open the psft_configuration.yaml file and copy the encrypted password from there for webserver_admin_user_pwd and profile_user password and paste in your psft_customizations.yaml file and then re-run it.

psft_customizations.yaml file for DPK installation but I want same folder structure what I had in past

---

ps_home_location:       "/oracle/peopletools/8.57.05"
ps_home:
  db_type:    "%{hiera('db_platform')}"
  unicode_db: "%{hiera('unicode_db')}"
  location:   "/oracle/peopletools/8.57.05"
  remove:  false

inventory_location:     "/oracle/oraInventory"
inventory:
  location: "/oracle/oraInventory"
  remove:  false

oracle_client_location: "/oracle1/app/oracle/product/12.1.0.2.0/fullclienthome1"
oracle_client:
  location: "/oracle1/app/oracle/product/12.1.0.2.0/fullclienthome1"
  remove:  false

jdk_location:           "/oracle/jdk/default"
jdk:
  location: "/oracle/jdk/default"
  remove:  false

weblogic_location:      "/oracle/middleware_12c"
weblogic:
  location: "/oracle/middleware_12c"
  remove:  false

tuxedo_location:        "/oracle/tuxedo"
tuxedo:
  location: "/oracle/tuxedo"
  remove:  false

ohs_location:           "/oracle/webserver"
ohs:
  location: "/oracle/webserver"
  remove:  false

Just note that You can do the customization however you want from your $/BASE/dpk/puppet/production/data

here you will have default files as 

defaults.yaml
psft_cm.yaml
psft_configuration.yaml
psft_deployment.yaml
psft_opa.yaml
psft_unix_system.yaml
psft_unix_system.yaml_20190806151800

after creating your customizations file you need to place here. Basically for location customizations you need to refer psft_deployment.yaml and for configurations related changes say you want 2 domains sites you need to refer psft_configuration.yaml and create psft_customizations file.


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...