Application Deployment

“In any collection of data, the figure most obviously correct, beyond all need of checking, is the error...”

Check, Double-Check, Recheck is the mantra while depolying on production in order to avoid any goofups. Despite any technique being used for deployment including ADM or EIM a thorough sanity should be done after deploying the artifacts on the production envirnoment. This becomes quintessential in multi-project environments where roll out is in phases. Every body has its own strategy based on the environment to perform a sanity check. However the one i have been using is to perform a count of records across the environment along with ADM to deploy artifacts. While ADM ensures that artifacts have been deployed successfully the count helps in confirming that nothing is missed from the source environment.

Here is sample query which can be customized based on the specific artifacts which gives us the count of records from multiple tables such as Personalization rules, runtime events, Views, Views/Responsibility, LOV's :

SELECT

(SELECT COUNT(*) FROM SIEBEL.S_RESP) S_RESP_COUNT, -- Count of Responsibilties

(SELECT COUNT(*) FROM SIEBEL.S_APP_VIEW) S_APP_VIEW_COUNT, -- Count of Views

(SELECT COUNT(*) FROM SIEBEL.S_APP_VIEW_RESP) S_APP_VIEW_RESP_COUNT, -- Count of Resp-View association

(SELECT COUNT(*) FROM SIEBEL.S_LST_OF_VAL) S_LST_OF_VAL_COUNT, -- Count of LOVs

(SELECT COUNT(*) FROM SIEBEL.S_CT_ACTION_SET) S_CT_ACTION_SET_COUNT, -- Count of Runtime Action sets

(SELECT COUNT(*) FROM SIEBEL.S_CT_RULE_SET) S_CT_RULE_SET_COUNT, -- Count of Personalization Action sets

(SELECT COUNT(*) FROM SIEBEL.S_SYS_PREF) S_SYS_PREF_COUNT, -- Count of System Preferences

(SELECT COUNT(*) FROM SIEBEL.S_VALDN_RL_SET) S_VALDN_RL_SET_COUNT -- Count of Validation Rules

FROM DUAL

This query should be run against source and destination databases and results should be compared. The output of this query looks like:

Happy crunching!!