Continuous Assessment Test 3

CAP470-Cloud Computing
Topic Name-
Enterprise Integration with the workday integration
cloud

Submitted by:- Submitted To:-

Name- Sarvesh kumar Dr. manmohan sharma
Reg no- 12103110
Roll n0- A39

Simplifying Enterprise Integration with the Workday Integrat

Simplifying Enterprise Integration
with the Workday Integration Cloud

The Burden of Enterprise System Integration Let’s be clear; integration of enterprise applications is
For an enterprise to thrive in today’s hyper-connected business complex, time-consuming, and hard. For many IT
and social environment, it needs to have access to necessary and departments, just keeping up with different types of
relevant data that enable, employees, partners, and customers to platforms and architecture scenarios requires a
have an engaging and useful experience. substantial investment of time and often happens at the expense
of other IT necessities.
The challenge of identifying, connecting, and using the
appropriate data and functionality becomes harder as enterprises Integration is a concern for both business and IT managers.
adopt more software and data repositories. There’s simply more Those involved with any part of implementing business
stuff to connect and manage. requirements into IT capabilities will deal with the issues of
integration regularly. This is especially
Contained within its internal applications and repositories,
true when an enterprise begins using cloud applications since
an enterprise probably has every piece of data that could be
they offer a more flexible model for accessing and sharing real-
to customers, partners, and their own employees. But if this
time data. The work will be strenuous, but the result will be
data isn’t delivered to the right people in a meaningful way,
hugely advantageous.
then an organization simply isn’t making the most of its
data and missing opportunities in the process. Yet for IT
The Problem with Traditional ERP
departments, integration usually appears seems both
daunting and never-ending. Few, however, would disagree Traditional ERP applications were built primarily on a client-

that server model that did not consider the need for sharing and

integrating enterprise IT assets is one of the most critical communicating with other applications.

elements of a company’s business and IT strategies. To remedy this disconnect, application programming interfaces
(APIs) were added later to accommodate system-to-system
At Workday, integration is not just a task in the overall integration. This approach increased the options available for
software development process. Workday applications are integrations, but unfortunately also greatly increased the cost
built with integration as a primary element to serve and complexity of building and supporting them. In addition,
customers’ needs effectively, our applications first need much of the integration to traditional ERP was completed at a
to connect existing systems to new ones, in order to drive data level
future growth and change. using SQL. Typically, achieving a more comprehensive integration
from the ERP system to necessary bolt-on systems required
Integration is not about ripping out your core systems and re-
significant programming, which only added to the cost,
learning a new way of conducting business. When done
complexity, and rigidity of these integrations.
correctly, integration delivers a vastly improved version of the
way you do things, and prepares your organization for the
future.

1
The Workday Approach: Integration in the Cloud 1. Open, Standards-Based Web Services APIs. At the
Human capital, payroll, and financial management systems foundation of our approach, Workday provides
must interact in a variety of ways with other internal and comprehensive standards-based web services APIs to
external systems and data sources. Unlike legacy enterprise support all integrations to and from Workday.
application providers, Workday understands the importance of Workday APIs are not only organized by functional

integration to core systems-of-record because integration has areas, but they also automatically inherit the security

been a fundamental architectural and application design permissions of the user executing the calls.

criteria from the company’s inception. 2. Integration Cloud Platform. The Workday
Integration Cloud Platform is a proven, enterprise-
Workday thinks that connectivity to other applications and class Integration-Platform-as-a-Service (iPaaS) that
resources should be simpler to build, deploy, manage, and enables Workday, customers, and partners to
evolve over time. This is a significant and long- awaited change build, deploy, and manage integrations to and from Workday in
from the way integration is currently done for most enterprise the Workday Cloud.
systems. By offering a variety of packaged solutions and
3. Integration Cloud Connect. Workday offers a
integration tools as well as
growing ecosystem of packaged integrations and
the ability to deploy integrations to the Workday Cloud,
connectors. These offerings are 100 percent built,
Workday helps relieve the burden of systems integration.
supported, and maintained by Workday as well as run
and managed in the Workday Cloud. This vendor-
To simplify systems integration, Workday provides the
supported approach significantly shifts
following solutions and tools:
the cost, risk, and burden of integrations from the
customer to Workday and significantly accelerates
implementation times.

Workday Integration Cloud

Workday Cloud

Workday Applications
Public Web Service APIs Custom APIs

Workday Integration Cloud

Integration Cloud Platform

Connectors and CC Packages Management and Monitoring

Cloud Applications On-Premise Applications Benefits Providers Payroll Providers

LDAP/AD

2
Why Use Workday for Integration? Workday Embraces Open, Standards-Based
Clearly, you can build any integration you need to the Workday Web Services APIs
API using your own middleware technology; MuleSoft, Boomi, At the core of Workday are open standards-based APIs that give
TIBCO, or Oracle Fusion Middleware are just a few of the complete programmatic access to business operations and
middleware tools used by Workday customers. However, there processes. These web services-based APIs provide an
are several major advantages to using the Workday Integration integration format (SOAP or REST) that is interoperable with
Cloud: all the leading client-side languages and integration
middleware platforms. In addition,
• Integrations surface naturally inside the Workday user
the Workday APIs are fully versioned, which means customers that
interface. You can view the integrations, launch them,
build an integration against any particular release of Workday are
schedule them, secure them, include them in Workday
guaranteed those integrations will continue to work across future
business processes, configure notifications around them,
Workday updates.
and audit and log them— all from within the Workday
user experience.
The Workday APIs contains the following service
• Both packaged and custom integrations run on categories:
Workday software and hardware infrastructure in our
data centers. You do not need to license or use any on- • Business Services are the primary way to

premise integration middleware platform, which can programmatically interact with Workday and directly

greatly simplify the deployment and management of correspond with the major functional areas of Workday

integrations especially when the majority of the (e.g., Staffing, Benefits, or Financial Management). The

integrations are connecting to Workday operations within these services correspond with
business events and business objects within Workday
• Finally Workday’s integration tools are also highly
(such as “Hire Employee” within Staffing or “Get
optimized for efficiently building integrations
Journal” within Financial Management). Operations
to and from Workday. Purpose-built packaged
return extensive data sets but can also be configured via
components handle much of the plumbing aspects of
“Response Groups” to return a subset of possible data
integration-building, freeing you to focus on the critical
(e.g., contact information, position information, etc.).
business logic.
• Reporting Services, also known as Reports-as-a-
Overall, Workday’s packaged integrations and tools are widely
Service (RaaS), provide a flexible, user-defined means to
proven in a variety of demanding situations and offer a lower-
get data out of Workday. All of the reports created
cost, lower-risk path to delivering needed integrations in
using Workday’s built-in report writer can be set up to
support of your deployment.
deliver data via RSS, REST (JSON), or traditional SOAP-
based messages with the simple click of a checkbox. This
includes customer-defined calculated fields. Reporting
Services effectively provide a mechanism within
Workday for customers to define and create their own
custom APIs. If only a subset of fields within Workday
Human Capital Management services are needed for a
specific integration, then a custom API

3
 that contains only those needed fields can be built.
type of transparency gives business users greater
Workday or any third-party integration tool can then
visibility into inter-system processing than ever before.
consume this API.

• Outbound Messaging Services are used to provide

Workday Integration Cloud Platform
real-time notifications to external applications
Workday’s Integration Cloud Platform is a proven, enterprise-
when business events occur within Workday. For
class Integration-Platform-as-a-Service (iPaaS) for building,
example, the workflow behind the “Hire” event in
deploying, and managing integrations to
Workday could be configured to publish an outbound
and from Workday. All integrations are deployed to and run in
message to a subscribing third-party
the Workday Cloud without the need for any on- premise
system. Upon receipt of the real-time notification, the
footprint or middleware. Workday also provides management
subscribing system could then query Workday (using
and monitoring services embedded in the Workday user
the public API) to get details about the “Hire” (e.g.,
interface.
employee information, job-related information, etc.)
and then take appropriate action. Powering all of Workday’s integration capabilities is a best-of-
breed Enterprise Service Bus (ESB) architecture that enables
• Monitoring Services expose Workday integration
Workday’s integrations to scale, interconnect, and support the
infrastructure status to external applications
latest industry standards, protocols,
so integrations can be enriched with additional
and formats. Workday’s ESB is a core component of the
functionality. For example, external applications can
Workday Integration Cloud and provides universal and open
monitor the execution of integration events that are
standards-based connectivity for virtually all types of business
happening within Workday. With this level of
applications, information, and processes.
information, external applications can see not only the
status of their current integrations but also gain insight
into when and how data will come from Workday prior
to the events occurring. This

Integration Cloud Platform

Workday Integration Tools (EIB & Studio) Design, Build, Test, & Deploy

Enterprise Class ESB Grid

Transport Mediate Route

Transform Orchestrate Secure

Workday UI
Manage & Monitor

4
Powerful Integration Tools To create an outbound EIB, users need to only go through
Powerful integration tools simplify custom integrations for three main steps:
both business managers and IT. Workday offers tooling for
common and simple integration scenarios as well as the 1. Get Data: In the “Get Data” phase, a data source is
complex ones that customers face today. specified. In 95 percent of the cases, this is a
These two offerings include Enterprise Interface Builder and custom report (RaaS). If you are specifying a Report
Workday Studio. Data Source, you can choose the format
in which the report results are delivered: normal
XML, simplified XML, CSV, JSON, GData, or RSS. Do
Enterprise Interface Builder (EIB)
not worry if these sound confusing—they just mean
The Workday Enterprise Interface Builder (EIB) tool provides an
you can get data straight out of the system in a variety
easy-to-use graphical and guided interface to define Workday-
of formats which may minimize or
based inbound and outbound integrations without requiring any
remove the need for subsequent transformation. It is
programming. Both business and IT users can use EIB to
also possible to specify a Workday Web Service
address a variety of integration needs.
endpoint as the data source for an EIB.

Outbound EIBs 2. Transform: At this point, you can either choose to

use your own XSLT transformation or use
the “Custom Report” transformation which is a UI-
based editor for transformations (you don’t need to
know any XSLT). The “Custom Report”
transformation is usually selected when the source is a
Outbound EIBs are used to extract information from report. Custom XSLT transformations must be uploaded.
Workday. The results can be stored in the customer’s tenant This step is optional if there is no need to alter the
for future use or sent out to any target system for further output of the source data.
processing. Over three-quarters of outbound EIBs currently
3. Deliver: The output can either be attached back to
in production send a file to an external destination via FTP your tenant, or alternatively delivered to an
automating the delivery of data to external systems. external endpoint. Supported transports are FTP, SFTP,
FTPS, HTTPS, email, and AS/2. You can optionally
compress or encrypt documents with a PGP key. You can
also control the created filename, any sequence numbers,
and document retention policies where appropriate. Once
an EIB is defined, any authorized user can run it. When it
runs to completion, its status (and any associated output
files) can be viewed by searching for the EIB run (and its
associated integration event record).

5
Inbound EIBs Workday Studio
Workday Studio is a powerful development tool that enables
customers and partners to build sophisticated integrations to and
from Workday applications. These integrations are deployed and
run on integration servers in Workday’s data center. Aimed at
skilled developers and offered as a set of plug-ins to the Eclipse
Inbound EIBs are a mirror image of the outbound EIB use IDE, Workday Studio offers a rich, graphical development
case. For a number of use cases, it is convenient to upload environment in which a user can drag and drop a variety of
information directly to the Workday system. In reusable components.
this case, an inbound file is provided and associated with a
transformation. This transformation will convert the data into
a format suitable for sending to a particular Workday web
service. In order to simplify this process, Workday can
generate a default spreadsheet for any inbound (add or update)
operation.

Some of these operations include mass payroll, time off, benefit

adjustments, and other standard HR and financial operations. All
you need to do is take the generated spreadsheet, add data to it,
and then use EIB to import
it to the customer tenant and insert or update all the records.
The Workday Integration Cloud will proactively notify any
errors in the load process and highlight the cells in the input
spreadsheet causing the problem. These delivered spreadsheets
can also be customized so you can specifically identify the
columns you need, add comments to help guide other users
who will be inputting the data, hide irrelevant fields, etc.

6
When to Use Workday Studio • Need to develop related integrations for other
Workday Studio provides a comprehensive set of capabilities services which also offer an Eclipse-based
for the identification, development, and management of development environment
integration tasks. Enterprises that use Workday Studio typically
have one or more of the following requirements:

Workday Integration Cloud Connect

• Multiple data sources and/or delivery requirements
Workday Integration Cloud Connect consists of a growing
• Scalable and efficient processing of large data sets (up number of pre-built integrations packaged as connectors and
to tens of gigabytes) Cloud Connect packages to complementary solutions that are
• Complex looping or branching logic based on 100% built, supported, and maintained by Workday. The
dynamic data or external variables benefits of this approach to the customer are many, including
access to a set of integrations that are:
• Sophisticated change detection requirements

• Complex error handling scenarios and • Lower cost, lower risk, and faster to deploy without
corresponding need to react differently to error requiring any coding
conditions
• Fully supported by Workday and certified and
• Need for rigorous source code control, unit testing, tested across updates and patches
debugging, logging, and other formal development
• Treated like any other part of the product, with a
disciplines
published product roadmap
• Need to extend with custom capabilities
implemented in Java, Spring, or a third-party
service

7
What Are Connectors? What Is a Cloud Connect Package?
Connectors are pre-built integrations that are designed, Workday provides a collection of connectors for speeding integration
implemented, and supported by Workday. They drastically implementation with third-party systems.
reduce the implementation time required to complete an end- Each Cloud Connect package contains a collection of
to-end integration by providing the processing logic, data connectors for orchestrating an end-to-end integration with
transformation, and error handling details required to integrate the processing logic and error handling required on the
third-party party systems such as Kronos, ADP, Ceridian, Workday side of the integration. In addition, connectors
Salesforce, Cybersource, Cornerstone, and others. All provide change detection, rule-based data mapping, field
connectors are configurable to accommodate differences in validation, and formatting. These Cloud Connect packages
customer situations (such as customizations of your third-party include connectors to known and
system) and run unknown third-party systems or standards. For the cases where
in the Workday Cloud, releasing you from the burden of the integrated third-party system is unknown, customers are
having to maintain a separate integration infrastructure. responsible for completing the integration by implementing
the necessary logic (it may require formatting and possibly
Connectors are managed just like any other Workday application
transformations) to tie it to
and are kept up to date with the same overall Workday update
the third-party system they are looking to integrate with
schedule. Updates include reacting to Workday core applications
Workday. Customers also have the flexibility to customize
—for compliance and additional application features—as well as
the orchestration of services within the Cloud Connect
updates to the latest tooling and infrastructure. In addition,
package to match their specific requirements for the
Workday works with third-party partners to manage a joint
integration. Integrations completed using Cloud Connect
roadmap to ensure the integration is kept up-to-date as the
packages run inside the Workday Cloud, and all
third- party application evolves.

8
Cloud Connect packages are managed, maintained and
1. Use a packaged connector to define the behavior of the
supported by Workday.
base one-time-payments integration.

Integration Cloud Connect offers the following Cloud Connect 2. Call this integration on a scheduled basis from
packages across Workday’s breath of business applications: within a business process.

3. Once the integration completes, forward a reference to

• Cloud Connect for Benefits - Extends Workday
the generated document to a second (Workday Studio-
Human Capital Management (HCM) by providing
built) integration, which further processes this output
integration to a growing catalog of benefits providers
by transforming it into a new file format.
including health insurance, health and flexible spending
accounts, retirement savings plans, life insurance, 4. Initiate an approval and delivery sequence from within

AD&D insurance, and COBRA administrators. the business process framework whereby the final file
proposed for delivery to the payroll vendor can be
• Cloud Connect for Third-Party Payroll - Extends
reviewed and approved in a normal workflow.
Workday HCM by providing integrations to third-
5. Once approvals are complete, deliver the file to the
party payroll providers and aggregators.
configured third-party endpoint, again powered by the
business process framework.
Putting It All Together: A Payments EXample
As an example, consider a customer who is using Workday All of the above is fully logged and audited, and any issues or

Studio to create a one-time payments integration to a third- errors that arise along the way can readily be corrected and the

party payroll vendor. This sample combines a number of process restarted.

aspects of the integration approach that has been described in

this document:

Business Process

Step 1: Launch Step 2: Launch Step 3: Launch

picof.Xml .csv file
PICOF PayData EXtract Integration Workday Studio PayData Integration Delivery Service

Completion Integration Event

9
The Workday Developer Network Workday’s Vision: Simplifying Integration
The Workday Developer Network is an online community for in the Cloud
developers to collaborate around Workday applications and Until now, the best option offered by traditional ERP
integrations. This developer network provides a variety of vendors to support integration to their solutions was a
resources and training material low-level API. With the emergence of Software-as- a-
on Workday’s integration solutions as well as the opportunity to Service (SaaS) as a delivery model for enterprise solutions,
interact with the Workday ecosystem. The community is the innovative vendors such as Workday are providing new
place to get all latest news relating to Workday’s integration approaches that simplify the creation, deployment, and
offerings, view the latest Workday Web Service API maintenance of integrations. Just as
documentation, take part in forum discussions, contribute an Workday simplifies the deployment, management, and upgrades
article, or share useful code. associated with enterprise applications through a SaaS-based
Workday is also committed to providing a rich ongoing supply delivery model, Workday also simplifies application integration
of real-world sample integrations that you can be used as a by moving the development, deployment, and management of
basis for your development efforts. integrations to the Workday Integration Cloud.

Visit our Workday Developer Network for more information

about Workday’s cloud-based approach to integration.