| Excerpt |
|---|
Notes from the morning of day 1. |
| Children Display | ||
|---|---|---|
|
...
| Attachments |
|---|
...
Kalan presented an overview of Workday Integrations
...
- Industry best practice
- Simplifies maintenance
- Promotes code reuse
- Stability
- Manageability of complex applications
Touch Points - all integrations are made of 2 or more touch points
Standardized Internal File Format
Benefits:
- allows maximum reuse of programs
- simplifies addition of future programs
Integration Types
Not long ago, the text book anser was that the only valid SOA communication is SOAP based web services.
In practice this is not realistic
Not all systems support web service...
In practice there are a number of communication systes that are commonly used
Oracle SOA will support all of these
- Web Services (SOAP or REST)
- Queues
- File Drop
Recommendations:
- Use SOAP web services for all communication outside of the Enterprise
- Standardize on either REST or SOAP fo web services within the Enterprise
- Most communications will be quick with reasonable sized docs Use Web services fr these
- for very large docs use files
- for batch processing use ques
- more to add
Oracle SOA is an Integration Suite.
See Dustin's slide deck for diagrams and detailed notes.
Workday Tenants
CU is using 5 tenants currently
How do we manage CU environments to match Workday tenant upgrades? We need a test environment synced up with Workday.
Dustin - what is the backward compatibility plan - Kalan - current - 3 is the current policy
Phil - how does load test get handled
Workday has a 2GB limit on flle extracts and integrations can only run for less than an hr
In bound Workday can only receive 5MB file size
COPY in Steve's Google doc notes here.
One customer out of 200+ wants a user acceptance test environment in place
We will need to plan for testing CU systems when a system (including Workday) is upgraded