If you are a Cloud client, there are no installation requirements.

If you are an On-Premise client, this section describes what you must do to install the product.

Pre-Installation Instructions

1. Overview

This document summarizes the steps that are required prior to installation of the Smart Onboarding product. These steps must be completed by all Smart Onboarding cloud customers that will run the Smart Onboarding application on their premises.

2. Initial Steps

a) Create Web Profiles

Create Web Profiles with names “SMINT” and “SMONB”, with all properties similar to PSHRDEV. Assure that the Timeout Warning is set as shown below.

b) Create Additional PeopleSoft Sites

Create an additional PeopleSoft Site “internal” on your primary PeopleSoft domain.

Create an additional PeopleSoft Site “external” on your primary PeopleSoft domain.

c) Copy Files to the new PeopleSoft Sites

Copy <<WEBSERVER>>\ <<DOMAIN>>\applications\peoplesoft\PORTAL.war\smart to Target Domain.

Copy <<WEBSERVER>>\ DEVHCM\applications\peoplesoft\ \PORTAL.war\WEB-INF\psftdocs\smarterp to Target Internal Domain

Copy <<WEBSERVER>>\ DEVEREC\applications\peoplesoft\ \PORTAL.war\WEB-INF\psftdocs\smarterp to Target eRecruit Domain

Copy <<WEBSERVER>>\ <<DOMAIN>>\applications\peoplesoft\ \PORTAL.war\WEB-INF\lib\SmartFilterNew.jar to Target Internal Domain and Target eRecruit Domain

Copy <<WEBSERVER>>\ DEVHCM\applications\peoplesoft\ \PORTAL.war\WEB-INF\smarterp.config to Target Internal Domain

Copy <<WEBSERVER>>\ DEVEREC\applications\peoplesoft\ \PORTAL.war\WEB-INF\smarterp.config to Target eRecruit Domain

d) Enable SmartFilter

Copy <<WEBSERVER>>\ <<DOMAIN>>\applications\peoplesoft\ \PORTAL.war\WEB-INF\web.xml to web.original.xml

Edit <<WEBSERVER>>\ <<DOMAIN>>\applications\peoplesoft\ \PORTAL.war\WEB-INF\web.xml and add the following entry after “”

<filter-name>SmartFilter</filter-name>

<filter-class>com.smarterp.ui.ResponsiveUIFilter</filter-class>

<init-param>

<param-name>configFile</param-name>

<param-value>smarterp.config</param-value>

</init-param>

</filter>

<filter-mapping>

<filter-name>SmartFilter</filter-name>

<url-pattern>/psp/*</url-pattern>

<url-pattern>/psc/*</url-pattern>

</filter-mapping>

e) Production Only Configuration

Edit <<WEBSERVER>>\ <<DOMAIN>>\applications\peoplesoft\ \PORTAL.war\WEB-INF\smarterp.config

Change:

TO

And change:

TO

f) Appserver Files Migration

Copy 1itext-2.1.7.jar from <<PS_APP_HOME>>\class to Target PS_APP_HOME\class folder.

g) Configure Authentication for Candidates

Navigate to PeopleTools > Security > SecurityObjects > Signon PeopleCode.

1) Set Invoke as user to an active PeopleSoft User ID.

2) Ensure that FUNCLIB_SM_AUTH is sequentially first as shown in the screenshot below.

Record: FUNCLIB_SM_AUTH

Field Name: LDAPAUTH

Event Name: FieldDefault

Function Name: SMSSO_AUTHENTICATION

Check the Enabled and Exec Auth Fail check boxes.

h) Add ONBRD Node to Single Signon

Navigate to PeopleTools > Security > SecurityObjects > Single Signon. Add the ONBRD Node.

i) Set Authentication Option and Password

The Default local node and the ONBRD node should have Authentication Option as password and should have same password.

The ONBRD node can use any standard PeopleSoft integration user.

j) Set the Login URL

Navigate to Peopletools > Utilities > Administrator > URLs and open SM_AUTH_SSI_LOGIN_URL.

Update the URL ID to point to the Primary PeopleSoft login URL as shown in example below.

http://<<hostname>>:<<portnumber>>/psp/<<sitename>>/?cmd=login&languageCd=ENG&

k) Webserver HostName DNS Entry

On each of the webserver hosts make sure that hostname.<<authentication token domain>> resolves to the local webserver host. If this is not handled on the dns server make sure to add it on thehosts file (On Linux/Unix at /etc/hosts and On Windows at C:\Windows\System32\drivers\etc)

For example: if the webserver hostname is "smtest01" and the authentication token domain used while creating webserver domain is ".smarterp.org" then smtest01.smarterp.org should resolve to the same host.

3. Installation Prerequisites

a) Create a PeopleSoft User and Two Webprofiles

1) Create a PeopleSoft user with User ID as “INVITEE”. Roles will be assigned in Post Installation.

2) Create two webprofiles in the PeopleSoft system with the following information:

a. Profile Name “SMONB” with Public access having user Id “INVITEE”.

b. Profile Name “SMINT” used for Internal/HR users. Public access is NOT required for this Site.

c. Create two WebDomains or Websites corresponding to the two web profiles for external and internal access.

4. Pre-Installation Steps

a) Create EDITTABLE Fields in the DERIVED Table in the HRSYS/HRMS Databases

This is needed because if this is not done before projects are copied, then the page won't recognize the fields added later and you will end up copying the Invitation pages two times. To prevent that, you must do this prior to the PeopleSoft Project copy.

b) Application Server/Process Scheduler Configuration Steps

Smart Onboarding uses the GetNextNumberWithGapsCommit PeopleCode function. Because of this we recommend that the Application server and process scheduler domains set DBFlags value to 8 under the PSTOOLS section. Please refer to My Oracle Support portal KB Article 1485558.1 for additional details on DBFlags.

c) Validate the Environment for Integration Broker Configuration

The environment must be validated for Integration Broker configuration, making sure the default local node is set up correctly, and that the active IB domain and keystore password are encrypted on the gateway configuration.

5. Installation Steps

a) Download and extract the windows executable from the zip file.

b) Run the executable and follow the instructions.

Choose the Copy option if you want to copy and build PeopleSoft projects manually. Choose manual build if you want projects to be copied, but built manually. Auto build will copy and build PeopleSoft projects during installation.

6. Import Certificate and Keystore Configuration Steps

The following describes the steps to be done to configure PeopleSoft keystores for secure integration between Smart E-Verify and the USCIS E-Verify Webservices.

a) Access the USCIS E-VERIFY URL

Access the USCIS E-Verify URL in any browser and open the certificate.

URL for Production Environment:

https://e-verify.uscis.gov/WcfWebService/EmployerWebServiceV29.svc?wsdl

URL for non-Production Environment:

https://stage.e-verify.uscis.gov/WcfWebService/EmployerWebServiceV29.svc?WSDL

b) View the Certificate

Go to the Certification Path tab and highlight the intermediate certificate, Symantec Class 3 Secure Server CA – G4 (intermediate certificate) in this case, and click the View Certificate button.

c) Certificate Details

On the intermediate certificate, go to the Details tab and click the Copy to fFle button to export the certificate.

d) Export Certificate

Choose the Base-64 Encoded X.509 (.CER) format and export the certificate into a file.

e) Copy and Import Certificate

Copy this file to the web server that is hosting the Integration Broker gateway and import the certificate file using pskeymanager (at <PS_CFG_HOME>\webserv\<domainname>\piabin) or any other key manager utility, and bounce the webserver.

.Installation Notes for On-Premise Clients v1.6