OTM Workflow

8/12/2019 OTM Workflow

1/38

QUALITY MATTERS

OTM WorkflowBest Practices

By

Lakshmi PadiletiDATE: 14 TH AUGUST 2012

www.srujantechnologies.com


2/38

j g

Agenda

Workflow Dependencies & Components

Workflow Preparation & Design

Workflow Setup Tips

Business Scenarios Best Practices

Documentation


3/38

Agenda



Workflow Setup Tips


Documentation


4/38

Workflow Dependencies


5/38

Workflow Facts

Workflow is NOT just agents

What to use is the KEY for bestworkflow design

One small mistake can cause the bigger

performance issues

Lot of new agent actions introduced, before writing

traditional way, look for new actions


6/38

Major Workflow Components

Automation Agents

Schedule Jobs

(Integration) Saved QueriesMilestone Monitors

VPD Profiles

Action Checks and

Many more


7/38

Integration Design

Does it impact workflow design? How?

Integration Components:

Interface DesignExternal System Setup

Out XML Profiles

Error Handling


8/38

Performance Tuning

Again, does it impact workflow design? How?

Major Performance Tuning Components

Tuning ThreadsTuning Connection Pools

Server Level Tuning (JVM, Memory, etc)

Minimizing Logs


9/38

Agenda



Workflow Setup Tips


Documentation


10/38

Workflow Time Allocation

Following chart gives high level time allocation forcomplex workflow setupThis may vary depends on the complexity

0%

10%

20%

30%

40%

Design Build Test

Time Allocation by Phase

Time Allocation


11/38

Workflow Preparation

Collect Requirement

Discussions

Analyze Understand &

identifyaffectedobjects

Prepare Document high

level workflowsetup


12/38


13/38

Workflow Preparation Design

Design:Avoid multiple agents triggering for same agent event

Initiate the DB package with frequently used queries &complex business logic

Introduce flags at object level for easy workflow &reports separation in multi phased/business processimplementations

Optimize the server resources by distributing schedule jobtimings

Identification of interfaces & integration process


14/38

Workflow Preparation Design contd

Process identification iskey in workflow design Agents

Saved Queries / Packages

Schedule Jobs

Milestones

Action ChecksUser Security (VPD, etc)

Anything else?


15/38

Agents:Identification of exact triggering conditionsIdentify similar requirements can go together

Agents high level flow for each business scenarioIdentify key agent actions/lookup/queries

Integrations:List of interfaces and data dependencyCommunication Method & List of Ext. SystemsOut XML Profiles



16/38

Error Handling:Initiate process for proper technical error handlingIdentify the possible solutions for business exceptions

Team:Allocate one dedicated team for workflow preparation toavoid redundancyReview the finalized process with different team beforebuild phase starts



17/38

Workflow Preparation Sample

Requirement: Copy the shipment quantities to shipmentactuals received via shipment events

Analyze: Identify when to copy actuals, for everyshipment event or only Pickup or Delivery? Check anyother requirements can marry with this one

Prepare: Document the requirement & write the highlevel pseudo agent related to this requirement


18/38

Workflow Preparation Sample contd

Prepare:Sample documentfor AgentsSpecification

What might bepoor design here?


19/38

Agenda



Workflow Setup Tips


Documentation


20/38

Avoid triggering multiple agents for given agentevent. This can cause serious problems if we mis-use.

Avoid using WAIT action

Careful while writing DSU Action:Default behavior refreshes entire Business Object Tree (I.e.Shipment, Stop, Ship Unit, etc.)

Enable Parse SQL option to increase performance byonly refreshing objects updated by SQL

Use Do Not Refresh when performing multiple updates tothe same object within one Agent

Workflow Setup Agents


21/38

Similar actions should not trigger in parallel on sameobject.

For ex, Recalc on date change & Rerate on locations

change. There are chances we can expect these twochanges at once

Every agent must pass through the test cases

Split the agents by business process

Enforce the version controllin in the a ents

Workflow Setup Agents contd


22/38

Avoid writing all actions into one big agent

Error Handler section should minimum notify users

Before going to production, NO AGENT TECHNICALFAILURES for any reason.

The acceptable failures will be business exceptions butnot technical exceptions

Workflow Setup Agents contd


23/38

Workflow Setup Saved Queries

Every SQL query must optimized by running explainplan

When query is expected for heavy usage, validatethe query with DBA for better performance

Move the commonly used queries into DB package

Avoid using OTM shipped views more than once in thesame query

When query is running longer time, negotiate with

business team to compromise the requirements


24/38

Workflow Setup Ext. Systems

Ext. systems configuration is simple and key

Identify the BEST communication method to use, for ex,HTTP, Web Service, FTP, etc by analyzing the currentenvironment

MUST have an habit to use Out XML Profile withtemplate option to reduce the xml size in ext. systems

Try to create a separate ext. system for eachinterface even though they are referring to same URL

Avoid using GLOG_* out xml profiles in notifications


25/38

Workflow Setup Schedule Jobs

Query must be tuned to the greater extend

Timing must be adjusted properly

Avoid running different long running jobs at the sametime


26/38

Workflow Setup Tuning

Threads:A backlog of queued events and/or a long average waittime may indicate a need to increase threads

Moving longer processing events to a dedicated threadgroup will increase throughput and reduce backlogs

Workflow processing is monitored with the Event

Diagnostics screen

Increase the connection pool sizes to desired levelbased on the load test results


27/38

Logs

Too much logging will impact on performance

Avoid using Ad -Hoc logs (which are written for all

users)

Do not turn on too many logs for User logs as well,

still impacts performance


28/38

Agenda



Workflow Setup Tips


Documentation


29/38

Best Design Approaches

Restrict the user access to see the orders & shipmentsrelated to their work location

Create separate screen sets, manager layouts & menus?

Create separate VPD profile and User Role?

Create one VPD profile with different User Roles link viaVPD context variables?


30/38


Send planned shipment to legacy when shipmenttendered or accepted

Send planned shipment when tendered & accepted

Revise the requirement and try to send planned shipmentat tender accepted time and introduce out xml profile toreduce the size of XML as low as possible

With this approach, half of the transmissions for sending

the planned shipments will be decreased


31/38


Recalc Shipment when shipment dates are changed,Rerate shipment when locations are changed

Write one agent for Recalc when dates changed andanother agent for Rerate when locations are changed

One agent with conditional check for dates vs locationchanges. Introduce Rerate status to identify rating failures

This will the avoid duplicate planning process when both

dates and locations are changed at the same time


32/38


Send vouchers to payment system

OTM will send voucher to middleware, business validation

checks perform in the middleware before sending topayment system

Perform as max as possible business validations beforeapproving the invoice and then send to middleware forfurther processing

Provides the better exception handling mechanism


33/38

Agenda



Workflow Setup Tips


Documentation


34/38

Documentation

List of workflow requirements (agents or etc)spreadsheet

Agents Specification Document

End to End technical document for complex processes

Saved Queries details & usage


35/38

Documentation

Agents Flow Diagram


36/38

Documentation

Schedule Jobs Flow Diagram

j t h l gi


37/38



38/38


Lakshmi Padileti

[email protected]

OTM Workflow

Documents

Transcript of OTM Workflow