Setting Up Employee Self Service V2 Part 7 - Testing ICS Integrations

So now we have configured all our ICS integrations and activated them.

We must now test them. Since they are REST services we can interrogate them.

In order to interrogate REST Web services we need two things.

1) A tool that can easily do the interrogation
2) The URL to be interrogated.

For 1) , download Postman ( a Chrome web app ) - this makes it very easy.

For 2)

Each Integration exposes a URL to invoke the ICS Integration.   In order to activate it, each URL is protected via Basic Authentication, so we need an ICS user and password.  ( you should have got this set up when provisioning ICS).

Getting the Integration URLs :



Within each integration, to the right of the green tick box is an (i) containing information. Click it : and copy the endpoint URL that appears.

Copy this into Postman, enter the userid and password into the Basic Authentication

If you have done everything right you should get the service Metadata in return :



Repeat this test for all the integration urls.


Once you have completed all the test, we have now checked that all the ICS integrations are end-to-ending OK, so we can now move on in the next blog post to configuring MCS.

See you soon !

Chris.

Setting Up Employee Self Service V2 Part 6 - Configuring ICS Internals.

Hiya again

Now we're showing how to configure up ICS to deal with the connectivity to EBS.

Construct the JDBC URL

• From the EBS connection information, construct the JDBC URL to insert into the integrations.The URL should look something like jdbc:oracle:thin:rws60039rems.oracle.com:1541:ebs11ic2

Obtain the PAR File

• From the solution distribution, get the selfservice-backend/ICS/EBS_SelfService.par file.

Upload the ICS Integrations Package

Go to ICS homepage and select Designer > Packages > Import Package. Select the PAR file in the file browser and click OK and Import.






This will create nine integrations:

• EBS_DeleteTimecard
• EBS_GetEmployeeProfile
• EBS_GetTimecardCategories
• EBS_GetTimecards
• EBS_CreateTimecard
• EBS_DoTimecardApproval
• EBS_GetTimecardApprovalList
• EBS_GetTimecardDetails
• EBS_GetVacations

It will also create three skeleton ICS Connections that you need to configure before you can activate the integrations:

• ICS Local REST
• 11iEbizDB
• EBS_SelfServiceSOAP

Correct the ICS Local REST Connection

1. Go to Connections and click to open ICS LOCAL REST.
2. Click Configure Connectivity and set the URL based on what is shown in your browser's address bar.For example, if you see https://icsapps-icaspps.integration.dc1.c9dev2.oraclecorp.com/ics/faces/global, the Connection URL should be https://icsapps-icaspps.integration.dc1.c9dev2.oraclecorp.com.
   The username and password should be set to an ICS system user credentials.

Not providing much info here as it is very  install specific. 

1. Click Test and then Exit Connection and Save. Click Yes to confirm that the integrations you just imported will be affected.
2. 
3. If you see the following message, repeat the above steps and test again.
   We cannot save your connection. [Cause: ICS-10954]:
- Unable to marshall the AppInstance into an xmlString.

( this error was not seen ) 

Correct the SOAP Connection

( These steps seem not to be  needed !!!! ) start going again at the Database Connectionsd. 

1. Go to connections and click to open EBS_SelfServiceSOAP.
2. You may need to upload the WSDL again. This WSDL should be in your project zip file (ebsselfservice-backend/ICS/EBS_SelfServiceActions.wsdl).
3. The username and password should be set to an ICS system user credentials.
4. Click Test and then Exit Connection and Save. Click Yes to confirm that 3 of the integrations you just imported will be affected.

Correct the Database Connection Information

1. Edit the DB Connection and configure the hostname, port, SID or service name, and the username and password.
2. Choose the agent group which you earlier created and validated and click Test to get it to 100% configured.

Saving this pops up the same warning box that you are affecting all the integrations; this is fine because you need to connect to EBS ! Click OK. 

Activate All Integrations

Go through all the  integrations and drag across the start button 

Do all the rest and it should look like : 

That's all for now.  In our next blog entry we'll move on to testing the integrations and finally moving towards MCS 

Setting Up Employee Self Service V2 Part 5 - Configuring ICS

Moving on we are now configuring ICS :

After you have prepared EBS to work with ICS, create the ICS users and roles for communicating with EBS. To do so, you need to have the ICS Identity Administrator role.
Within the My Services Users page in Oracle Cloud, create the following types of users:

• A single user with the ICS Runtime role.
  This user should be an administrator who does not do development and the credentials should be kept secret as much as possible. (While still in development, developers will need access to this user's credentials, but they need to be protected carefully once in production.)
• Users with the ICS Users role for anybody who will be using ICS to create and configure ICS integrations.

If you would like more detail on how roles work in ICS, see About Oracle Integration Cloud Service Roles and User Accounts in Using Oracle Integration Cloud Service

Since we are using a trial GSE account I will use the specified account with the system; I will not post the credentials here. 

Now lets grab the ICS Agent 

1. Log in to ICS.
2. In the ICS toolbar, click Designer.
3. On the Designer Portal, click Agents.
4. Click Create New Agent Group and complete the wizard to create the new agent group.
5. Click the the Download Agent Installer button, select Connectivity Agent, and save file to the Linux machine where the agent will be installed/running. This Linux machine needs to be able to establish a non-proxied TCP/IP connection to the EBS instance it will be communicating with.

[ Please do NOT leave this till the last minute.  The download is just under 2GB in size and if you are downloading it to the desktop and then uploading to your EBS server it will take quite some time.   !!! You have been warned.  Currently waiting 3-4 hours for download and upload ... ] 

Now that's done [ we are extracting to our demo EBS app tier ] 

Create a directory /u01/ICS [ keeping things simple ]  and chown everything to  oracle. [ again keeping it simple  but I'd presume there's no issue separating them ]  

1. Click the the Download Agent Installer button, select Connectivity Agent, and save file to the Linux machine where the agent will be installed/running. This Linux machine needs to be able to establish a non-proxied TCP/IP connection to the EBS instance it will be communicating with.
2. Extract the contents of the zip file and navigate to the cloud-connectivity-agent-installer.bsx file. This .bsx (a self-extracting Linux bash script) is the installation script that will be executed in the EBS machine.
3. Make sure the cloud-connectivity-agent-installer.bsx file is executable (e.g., run chmod +x cloud-connectivity-agent-installer.bsx)
4. Construct a command to execute the shell script with the following elements:

   ./cloud-connectivity-agent-installer.bsx —h=https://[ICS_HOST]:443 —u=[ICS_USERNAME] —p=[ICS_PASSWORD] —ad=[AGENT_GROUP_IDENTIFIER] -au=[AGENT_USERNAME] -ap=[AGENT_PASSWORD] -aport=[OPTIONAL_AGENT_PORT] -ph=PROXY_HOST -pp=PROXY_PORT

   where:
• [ICS_HOST] = the host name of your ICS service. (The port appended to the host name must be 443.)
• [ICS_USERNAME] =
• [ICS_PASSWORD] =
• [AGENT_GROUP_IDENTIFIER] = the agent group identifier that was generated in the Identifier field when you created the agent group.
• [AGENT_USERNAME] = the agent username. This is the username with which you log in to the on-premises agent’s Oracle WebLogic Server Administration Console, if required.
• [AGENT_PASSWORD] = the agent password.
• [OPTIONAL_AGENT_PORT] = the port to use for the agent if you don't want to use the default (7001)
• [PROXY_HOST] = the outbound proxy hostname.
• [PROXY_PORT] = the outbound proxy password.

For our purposes. 

ICS_HOST=  xxx.us2.oraclecloud.com

1. Execute the script. For example:

   ./cloud-connectivity-agent-installer.bsx -h=https://icsapps-icaspps.integration.dc1.c9dev2.oracle.com:443 -u=joe.green@example.com -p=We1come1 -ad=MOBILEPACKAGEDSOLUTIONSAGENTGROU -au=weblogic -ap=welcome -ph=www-proxy.mycompany.com -pp=80
   

2. Return to the ICS console and the Agent Groups page and verify that the agent count is 1 (or has increased by one).

Problems we had : 

1.  installer thinks Derby is running ( solution shut EBS down , install agent, start EBS back up again 

2. Installer complains about other files in directory ( solution : create cca subdirectory move BSX file into that directory, run from there, all OK ) 

3. Installer complains Java Home not set ( solution : install a JDK ( we used 1..8.102, set JAVA_HOME envar, all OK ). 

The agent server is a single-server WebLogic Server configuration where everything is targeted to the Admin server and (by default) listens on port 7001. Simply use the scripts in the ${agent_domain}/bin directory to start and stop the server

rgument -- -h=h:443
Argument -- -u=roland.dubois
Argument -- -p=******
Argument -- -ad=MobDemo_EBSICS_OCT16
Argument -- -au=weblogic
Argument -- -ap=******
Argument -- -aport=9001
minimum free space available requirement is 5 GB
Enough Space Available
Linux Operating System.....Proceeding with installation
Java Home Check Verified OK
Oracle Java is Present,Verified OK
JAVA 64-Bit is Present,Verified OK
Derby Check Verified OK
HOSTURL  = https://i:443
USENAME     =
PASSWORD    = ******
PROXYHOST   =
PROXYPORT   =
AGENTDEFINITION = MobDemo_EBSICS_OCT16
DATABASEPASSWORD =
AGENTUSER   = weblogic
AGENTPORT   = 9001
AGENTPROFILE =
NOPROXYHOSTS =
https protocol
Valid hostURL provided
integration-g.oraclecloud.com is alive
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
No conflicting Process Running, Verified OK
Checking the installation directory for unwanted files or directories.
Finished checking the installation directory for unwanted files or directories.

Self Extracting Installer

./agentInstaller/
./agentInstaller/config/
./agentInstaller/config/oraInst.loc
./agentInstaller/config/details.properties
./agentInstaller/config/agent_response.properties
./agentInstaller/config/rcu_pwd.txt
./agentInstaller/config/revisionHistory.txt
./agentInstaller/config/response.properties
./agentInstaller/lib/
./agentInstaller/lib/oracle.cloud.agent.jar
./agentInstaller/lib/ics_connectivity_agent_generic.jar
./agentInstaller/agent/
./agentInstaller/agent/config/
./agentInstaller/agent/config/CpiAgent.properties
./agentInstaller/agent/cert/
./agentInstaller/agent/cert/AgentRestClient.jar
./agentInstaller/agent/cert/DecryptUtil.jar
./agentInstaller/agent/cert/keystore.jks
./agentInstaller/agent/app/
./agentInstaller/scripts/
./agentInstaller/scripts/launch-server.sh
./agentInstaller/scripts/create-shiphome-Domain.py
./agentInstaller/scripts/compact-shiphome-Domain.py
./agentInstaller/scripts/createDomain.py
./agentInstaller/scripts/compactDomain.py
./agentInstaller/scripts/onpremis-agent-install.sh
./agentInstaller/scripts/launch-shiphome-server.sh
./agentInstaller/scripts/import_cert_kss.py
./agentInstaller/scripts/on-premise-agent-shiphome-install.sh
./agentInstaller/install-agent.sh
./agentInstaller/install-shiphome-agent.sh
./agentInstaller/wls/
./agentInstaller/wls/wls_jrf_generic.jar


bla bla bla bla ( 30 mins )

Location changed to serverRuntime tree. This is a read-only tree with ServerRuntimeMBean as the root.
For more help, use help('serverRuntime')

Location changed to domainRuntime tree. This is a read-only tree with DomainMBean as the root.
For more help, use help('domainRuntime')

Keystore imported. Check the logs if any entry was skipped.

- end importCert for verisign
Already in Domain Runtime Tree

Keystore imported. Check the logs if any entry was skipped.

- end importCert for verisign
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
Agent is Running
Agent Instance Creation at ICS is Successful
The Agent has been Successfully Installed. And it is ready to process requests from ICS as well as on premises end points. You can always look at the Agent Status by logging into ICS
[oracle@bd8bc7 cca]$

ICS is showing 1 agent :

IN the next blog we'll show how to upload the ICS Integrations ... 

Install Node.js and NPM on Oracle Linux

Hi Folks

Stepping out from the Mobile Blog to do a short tech  blog.  We need node.js so in order to get it up and running while we blog the rest of the mobile set up on ICS we can be installing node.js in the background.

Node is not part of the standard YUM repos so we need another repo added ( there are lots of other ways  too ! ) .

Here's mine.

We need to get the EPEL Repo ( this has node in it ).
As root:

Need wget to get the first rpm
( we are using a very basic Oracle Install )
[root@mobdev1 ~]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.8 (Santiago)
[root@mobdev1 ~]#

[root@mobdev1 ~]# yum -y install wget
Loaded plugins: security, ulninfo
Setting up Install Process
Resolving Dependencies
--> Running transaction check
---> Package wget.x86_64 0:1.12-8.el6 will be installed
--> Finished Dependency Resolution

Dependencies Resolved

================================================================================
 Package       Arch            Version                Repository           Size
================================================================================
Installing:
 wget          x86_64          1.12-8.el6             ol6_latest          483 k

Transaction Summary
================================================================================
Install       1 Package(s)

Total download size: 483 k
Installed size: 1.8 M
Downloading Packages:
wget-1.12-8.el6.x86_64.rpm                               | 483 kB     00:00
Running rpm_check_debug
Running Transaction Test
Transaction Test Succeeded
Running Transaction
  Installing : wget-1.12-8.el6.x86_64                                       1/1
  Verifying  : wget-1.12-8.el6.x86_64                                       1/1

Installed:
  wget.x86_64 0:1.12-8.el6

Complete!
[root@mobdev1 ~]#

Now to get the EPEL RPM

[root@mobdev1 ~]# wget https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm

--2016-10-14 07:09:55--  https://dl.fedoraproject.org/pub/epel/epel-release-latest-6.noarch.rpm

Resolving dl.fedoraproject.org... 209.132.181.26, 209.132.181.24, 209.132.181.25, ...

Connecting to dl.fedoraproject.org|209.132.181.26|:443... connected.

HTTP request sent, awaiting response... 200 OK

Length: 14540 (14K) [application/x-rpm]

Saving to: âepel-release-latest-6.noarch.rpmâ

100%[======================================>] 14,540      --.-K/s   in 0.1s

2016-10-14 07:09:56 (103 KB/s) - âepel-release-latest-6.noarch.rpmâ

[root@mobdev1 ~]#

Now to install it. 

[root@mobdev1 ~]# yum -y install epel-release-latest-6.noarch.rpm

Loaded plugins: security, ulninfo

Setting up Install Process

Examining epel-release-latest-6.noarch.rpm: epel-release-6-8.noarch

Marking epel-release-latest-6.noarch.rpm to be installed

Resolving Dependencies

--> Running transaction check

---> Package epel-release.noarch 0:6-8 will be installed

--> Finished Dependency Resolution

Dependencies Resolved

================================================================================

 Package          Arch       Version    Repository                         Size

================================================================================

Installing:

 epel-release     noarch     6-8        /epel-release-latest-6.noarch      22 k

Transaction Summary

================================================================================

Install       1 Package(s)

Total size: 22 k

Installed size: 22 k

Downloading Packages:

Running rpm_check_debug

Running Transaction Test

Transaction Test Succeeded

Running Transaction

  Installing : epel-release-6-8.noarch                                      1/1

  Verifying  : epel-release-6-8.noarch                                      1/1

Installed:

  epel-release.noarch 0:6-8

Complete!

[root@mobdev1 ~]#

Now to get node.js and npm

yum -y install nodejs npm 

( Lots and lots of getting files remotely and  installing .. 

here's a sample

---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

Total                                                                                                                                                         12 MB/s |  57 MB     00:04

warning: rpmts_HdrFromFdno: Header V3 RSA/SHA256 Signature, key ID 0608b895: NOKEY

Retrieving key from file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6

Importing GPG key 0x0608B895:

 Userid : EPEL (6)

 Package: epel-release-6-8.noarch (@/epel-release-latest-6.noarch)

 From   : /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-6

Running rpm_check_debug

Running Transaction Test

Transaction Test Succeeded

Running Transaction

  Installing : 1:libuv-0.10.34-1.el6.x86_64                                                                                                                                            1/110

  Updating   : openssl-1.0.1e-48.el6_8.3.x86_64                                                                                                                                        2/110

  Installing : nodejs-0.10.46-1.el6.x86_64                                                                                                                                             3/110

  Installing : nodejs-inherits-2.0.0-4.el6.noarch                                                                                                                                      4/110

  Installing : nodejs-semver-2.1.0-1.el6.noarch                                                                                                                                        5/110

  Installing : nodejs-mkdirp-0.3.5-3.el6.noarch                                                                                                                                        6/110

  Installing : nodejs-graceful-fs-2.0.0-2.el6.noarch                                                                                                                                   7/110

  Installing : nodejs-rimraf-2.2.2-1.el6.noarch                                                                                                                                        8/110

  Installing : nodejs-fstream-0.1.24-1.el6.noarch                             

after about 3 or 4 mins 

 redhat-rpm-config.noarch 0:9.0.3-51.0.1.el6                  v8.x86_64 1:3.14.5.10-25.el6                                v8-devel.x86_64 1:3.14.5.10-25.el6

  zlib-devel.x86_64 0:1.2.3-29.el6

Dependency Updated:

  openssl.x86_64 0:1.0.1e-48.el6_8.3

Complete!

[root@mobdev1 ~]#

[root@mobdev1 ~]# node -v

v0.10.46

[root@mobdev1 ~]#

Finally you should update node and NPM to the latest versions :

sudo npm cache clean -f
sudo npm install -g n
sudo n stable

npm install npm@latest -g

                                                                             

Setting Up Employee Self Service V2 Part 4 - Configuring EBS for ICS

Continuing our series on looking into the newest version of Oracle's EBS Mobile Applications,  we now move on to Part III - in which we amend EBS Vision Payroll Configuration so it makes for a reasonable demo.

Create a New EBS User

1. Create a new schema user in EBS and call it XXMC.
2. Grant the user the necessary privileges:

   GRANT CREATE SESSION TO XXMC;
   GRANT CREATE PROCEDURE TO XXMC;
   GRANT CREATE TYPE to XXMC;
   

QL> create user XXMC identified by r1234567;

User created.

SQL> GRANT CREATE SESSION TO XXMC;

GRANT CREATE PROCEDURE TO XXMC;

GRANT CREATE TYPE to XXMC;

Grant succeeded.

SQL>

Grant succeeded.

SQL>

Grant succeeded.

SQL>

This user will be a system user than can access and update employee timecard records in EBS. We'll later give this user the least privileged credentials that are needed for the solution to work (the ability to call the package XXMC_Utilities on Apps.

Create Custom Views and Packages

As the APPS user, run the provided SQL scripts in the following order to create the necessary views and packages:

1. EBS/init/01_create_XXMC_HXC_WORKED_HOURS_V.sql
2. EBS/init/02_create_XXMC_HXC_TC_WORKED_HOURS_V.sql

[oracle@bd8bc7 init]$ sqlplus apps @01_create_XXMC_HXC_WORKED_HOURS_V.sql

SQL*Plus: Release 12.1.0.2.0 Production on Wed Oct 12 11:34:19 2016

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Last Successful login time: Wed Oct 12 2016 11:30:52 -04:00

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

View created.

Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

[oracle@bd8bc7 init]$ sqlplus apps @02_create_XXMC_HXC_TC_WORKED_HOURS_V.sql

SQL*Plus: Release 12.1.0.2.0 Production on Wed Oct 12 11:34:28 2016

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Last Successful login time: Wed Oct 12 2016 11:34:20 -04:00

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

View created.

Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

[oracle@bd8bc7 init]$

1. EBS/plsql/XXMC_Utilities.pks
2. EBS/plsql/XXMC_Utilities.pkb

[oracle@bd8bc7 plsql]$ sqlplus apps @XXMC_Utilities.pks

SQL*Plus: Release 12.1.0.2.0 Production on Wed Oct 12 11:35:09 2016

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Last Successful login time: Wed Oct 12 2016 11:34:28 -04:00

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

Package created.

No errors.

Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

[oracle@bd8bc7 plsql]$ sqlplus apps @XXMC_Utilities.pkb

SQL*Plus: Release 12.1.0.2.0 Production on Wed Oct 12 11:35:15 2016

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Last Successful login time: Wed Oct 12 2016 11:35:10 -04:00

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

Package body created.

No errors.

Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

[oracle@bd8bc7 plsql]$

[oracle@bd8bc7 plsql]$

Note: The XXMC_Utilities package is set up with definer's rights.

Grant the XXMC User Permission to Execute the Newly Created Package

• As the APPS user, run the following command to grant the XXMC user permission to invoke the package you created on Apps:

  GRANT EXECUTE ON APPS.XXMC_Utilities TO XXMC;

SQL> GRANT EXECUTE ON APPS.XXMC_Utilities TO XXMC;

Grant succeeded.

SQL>

Make a note of these least privileged user credentials. These are the database credentials you will be using later on in ICS. These packages give the Integration Cloud Service a standard way to interact with the data in EBS.

Create the Wrapper Types and Package That Can Be Called from ICS

• As the XXMC user, run the EBS/integration/XXMC_ICS_TIMECARD_create.sql script.

Errors for PACKAGE XXMC_ICS_TIMECARD:

LINE/COL ERROR

-------- -----------------------------------------------------------------

3/9      PL/SQL: Declaration ignored

4/25     PLS-00754: illegal reference to editioned object

         APPS.XXMC_UTILITIES

SQL> alter user XXMC enabled editions;

alter user XXMC enabled editions

                *

ERROR at line 1:

ORA-00922: missing or invalid option

SQL> alter user XXMC enable editions;

User altered.

SQL>  select editions_enabled from dba_users where username in ('APPS','XXMC');

E

-

Y

Y

SQL>

drop it and run again

[oracle@bd8bc7 integration]$ sqlplus xxmc/r1234567 @XXMC_ICS_TIMECARD_create.sql

SQL*Plus: Release 12.1.0.2.0 Production on Wed Oct 12 11:45:54 2016

Copyright (c) 1982, 2014, Oracle.  All rights reserved.

Last Successful login time: Wed Oct 12 2016 11:45:45 -04:00

Connected to:

Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

Type created.

No errors.

Type created.

No errors.

Type created.

No errors.

Type created.

No errors.

Type created.

No errors.

Type created.

No errors.

Type created.

No errors.

Type created.

No errors.

Type created.

No errors.

Type created.

No errors.

Package created.

No errors.

Package body created.

No errors.

Disconnected from Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production

With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options

[oracle@bd8bc7 integration]$

Note the Database Host, Port, SID (or service name), and Restricted User Credentials

These will be needed for ICS setup.

10.196.134.222
bd8bc7.compute-a423042.oraclecloud.internal
EBSDB
XXMC/R11234567

OK next step is to configure ICS !

Setting Up Employee Self Service Mobile V2 - Part 3b EBS Screen Configurations.

Continuing our series we now move on to Part 3b, which is more E-Business Configuration

From the linked Tutorial Here Are the Steps :

1. Enable the HR Absences Integration with OTL profile option.
1. Navigate to System Administrator > Profile > System.
2. Search for the profile HR: Absences Integration with OTL.
3. Modify the site-level value to Yes.
4. Save the change.

1. Disable obsolete absence elements and absence types. The absence elements and absence types that are pre-seeded in OTM Vision Weekly payroll do not work well when Absences and OTL are integrated. So we need to disable these absence elements and absence types.
1. Navigate to US OTL Application Developer, Vision Corporation > Alternate Names > Alternate Name Definition.
2. Search for the Alternate Name Definition: Vision OTL Elements - Enabled.
3. For Alternate Names: Paid Vacation and Sick Hours Taken, uncheck the Enabled checkbox.
2. 
1. Save the changes.
2. Navigate to US Super HRMS Manager, Vision Corporation > Total Compensation > Basic > Absence Types.
3. Search for the following Absence Types - Sick Time and Vacation.
4. End date both the absence types by entering the current date in the Effective Dates To field.
5. Save the changes.
6. 
7. 
8. 
   
3. Create absence elements
1. Navigate to US Super HRMS Manager, Vision Corporation -> Total Compensation -> Basic -> Element Description.
2. Create an element with the following information:
   • Name: Absence Sick Hours Taken
   • Reporting Name: Absence Sick Hours Taken
   • Primary Classification: Information
3. Save the changes.
4. 
1. Click Input Values.
2. Add a row with the following values:
   • Name: Hours
   • Units: Hours in Decimal format (2 places)
3. Save the changes and close the dialog.
5. 
1. Click Further Information.
2. In the dialog that opens up, for Category, enter Absence Hours and click OK.
3. Click OK.
4. 
     If are asked to choose between correcting existing information versus preserving history, choose to correct existing information.
5. Save the changes.
6. Add another absence element with the following information:
   • Name: Absence Paid Vacation
   • Reporting Name: Absence Paid Vacation
   • Primary Classification: Information
   • Input Values::
     • Name: Hours
     • Units: Hours in Decimal format (2 places)
   • Further Information:
     • Category: Absence Hours
7. Save changes.
6. 
7. Link absence element to payroll.
1. Navigate to US Super HRMS Manager, Vision Corporation > Total Compensation > Basic > Link.
2. For Element Name select one of the absence elements added above (for example, Absence Sick Hours Taken).
3. Check Link To All Payrolls.
4. Save the changes.
5. Repeat these sub-steps for all the absence elements added earlier.
8. 
9. 
10. Create absence types.
1. Navigate to US Super HRMS Manager, Vision Corporation > Total Compensation > Basic > Absence Types.
2. Add an absence type with the following information:
• Name: Absence Sick Time
• Category: Sickness
• Associated Element::
• Name: Absence Sick Hours Taken Click OK for the question This element may be processed by the Payroll Run - continue?
• Units: Hours
• Balance: Decreasing
• Reasons: Compassionate Leave, Dental Appointment, Doctors Appointment, Illness, Sick
11. 
1. Save the changes.
2. Add another absence type with the following information:
   • Name: Absence Vacation
   • Category: Vacation
   • Associated Element::
   • Name: Absence Paid Vacation Click OK for the question This element may be processed by the Payroll Run - continue?
   • Units: Hours
   • Balance: Decreasing
   • Reasons: Vacation
   • 
3. Save the changes.
12. Create element set.
1. Navigate to US Super HRMS Manager, Vision Corporation > Payroll > Element Set.
2. Add an element set with the following information:
   • Name: PackagedApps Absence Elements
   • Type: Run Set
3. Save the changes.
4. Click Include Elements.
5. Add the two elements: Absence Sick Hours Taken and Absence Paid Vacation.
13. 
14. Generate flexfield mapping.
1. Navigate to US OTL Application Developer, Vision Corporation > Process and Reports > Submit Process and Reports ( bug in original text ) 
2. For the question What type of request do you want to run?, select Single Request and click OK.
3. Fill in the following values:
• Name: Generate Flexfield and Mapping Information
• Parameters::
• Delete Definitions?: No
• Element Set: PackagedApps Absence Elements
• Effective Date: today's date in the format 30-Sept-2016
• Include Absence Information?: Yes

1. Click OK and then Submit. For the question Submit another request? choose No.
2. Navigate to US OTL Application Developer, Vision Corporation > Process and Reports > View Requests.
3. Select All My Requests and click Find. The Generate Flexfield Mapping request should be shown. The Phase should be Completed and the Status should be Normal.
1. 
   
2. 
3. Configure absence types.
   1. Navigate to US OTL Application Developer, Vision Corporation > Absence Integration Setup > Configure Absence Types.
   2. In the Element Set text field enter PackagedApps Absence Elements and click Go. The Absence Types associated with the element set should be displayed.
   3. For all the absence types listed, change the value in the Timecard Action Allowed column to View and Edit.
   
   1. Click Save.
   Note: After submitting the Generate Flexfield Mapping request for an element set, there might be a short delay before the element set is searchable on the Absence Integration Setup page.

1. Set alternate name definitions.
1. Navigate to US OTL Application Developer, Vision Corporation > Alternate Names > Alternate Name Definition.
2. Search for Alternate Name Definition: Vision OTL Elements - Enabled.
3. Add an alternate name with the following information:
   • Alternate Name: Sick
   • From: leave the current date as is
   • Values: Absence Sick Hours Taken
   • Enabled: Checked
4. Add an another alternate name with the following information:
   • Alternate Name: Vacation
   • From: leave the current date as is
   • Values: Absence Paid Vacation
   • Enabled: Checked
5. Save the changes.
2. 

Finally we need to 

Customize the Review Layout

To show the Comment and Location fields on the Review page of the app, we need to upload a customized definition for the review layout:

1. From the terminal of the EBS instance, with the correct TNS connection identifier, execute the following command to load the LDT file Payroll_review_comments3.ldt (located in the selfservice-backend/EBS/seeded directory of the solution) into the system:
   

   FNDLOAD apps/apps@ 0 Y UPLOAD $HXC_TOP/patch/115/import/hxclaytlayoutsld.lct Payroll_review_comments3.ldt

[oracle@bd8bc7 ~]$ FNDLOAD apps/apps@EBSDB 0 Y UPLOAD $HXC_TOP/patch/115/import/hxclaytlayoutsld.lct ./Payroll_review_comments3.ldt

Log filename : L7535553.log

Report filename : O7535553.out

[oracle@bd8bc7 ~]$

+---------------------------------------------------------------------------+

Concurrent request completed successfully

Current system time is 12-OCT-2016 11:17:34

+---------------------------------------------------------------------------+

                                                                                         

1. Attach the new layout to the employee through OTL preferences:
1. Navigate to US OTL Application Developer, Vision Corporation > Preferences > PackagedApps-Payroll > Timecard Layout > Preference Values.
2. Modify Review Layout to Payroll Review Layout WC3 with Detail level comments and save.

That was a long and tedious process !  [[ PS where are the simple SQL for all this !!! ]]  Anyway its done now so let's move onto the next step, configuring EBS for ICS. 

Setting Up Employee Self Service Mobile V2 - Part 3a EBS Screen Configurations.

Continuing our series on looking into the newest version of Oracle's EBS Mobile Applications,  we now move on to Part III - in which we amend EBS Vision Payroll Configuration so it makes for a reasonable demo.

First thing to do is set the payroll for 30 years :

1. Navigate to HRMS Management, Vision Corporation > HRMS Manager &g; Payroll > Description.
2. Once in the Payroll dialog, press the F11 key, enter OTM Vision Weekly in the Name field, and press Ctrl+F11.
3. Change the value of the Number of Years field to 30.
4. Select File > Save.
5. 
6. On the next box press Update.

File/Exit Oracle Applications.  

Now for the Preferences 

1. Navigate to the US OTL Application Developer, Vision Corporation > Preferences page.
2. From the main menu, double-click the Preferences function, type PackagedApps-Payroll as the name of the node, and save the change.
3. Right-click the new PackagedApps-Payroll node, select New, enter Alternate Name as the name of the node, and save.
4. Select the new node.
5. In the Preferences field, enter Self-Service Timecard Alternate Name Set Defined for a User.
6. In the Preference Values field, enter Vision OTL Elements - Enabled and click OK.

Note that steps 4,5,6 are all selecting from a list; there is no  direct entry . Once you have it all correct it should look like 

Now do file/save and repeat the entries 3-6 above for all ove the other entries required. 

This  will take about 15 mins per the instructions 

Now : 

1.     On the Preferences form, click the Eligibility Criteria tab on the Preferences form and enter a blank query (Ctrl+F11).
2.     Click in the first empty row and create a new record with the following values:
3.         Name of rule: Payroll Rule
4.         Name of Branch: PackagedApps-Payroll
5.         Link By: Payroll
6.         Linked to: OTN Vision Weekly
7.         Precedence: Use any unique number that has not been entered on the form. You should enter a high number, such as 10000, because the precedence is calculated in descending order.
8.     Save and close the form.

If tis done right it should look like 

Assign the Accrual Plan to the Test Users

1. For every accrual plan there is a recurring element created with the same name as the accrual plan. This element needs to be attached to the assignment from the element entry screen.
2. 
   
3.     Navigate to HRMS Management, Vision Corporation > HRMS Manager > People > Enter and Maintain.
4.     Find the test user using the first and last names. (See the 01_seed_test_users.sql script for their full names)
5.     Navigate to Assignment > Entries (or) Fastpath > Element Entries.
6.     Add elements by clicking in the first empty row and creating a new record with the following values:
7.         Element Name - Sick Time Accrual, Processing Type - Recurring
8.         Element Name - Vacation Accrual, Processing Type - Recurring
9.         Element Name - Family Medical Leave, Processing Type - Recurring
10.     Select File > Save

Repeat until all test employees are done ( why they could not just do this with a bunch of PL/SQL APIs I do not know 

That is enough for one blog.  Tomorrow I will blog about fixing OTL .  A basic step and hopefully should go according to the manual.  

So far we have been OK, just minor fixings.