Creation of related SA-KPI (sa-KPI-tutorial.zip)

compared with
Current by Olivier Fabre
on May 28, 2010 11:44.

Key
This line was removed.
This word was removed. This word was added.
This line was added.

Changes (8)

View Page History
{color:#333333}We'll first import in Petals Studio, the preconfigured services assemblies provided in PetalsView-SA directory. Thanks to this, we will easily retrieve informations we need to build our su-kpi.{color}

{color:#333333}{*}{_}4.1) Import sa from PetalsView-SA directory in Petals Studio{_}{*}{color}
h1. *Import sa from PetalsView-SA directory in Petals Studio*

{color:#333333}Launch Petals Studio and choose your workspace.{color}


{color:#333333}{*}{_}4.2) Create your su-kpi{_}{*}{color}
h1. *Create your su-kpi*

{color:#333333}In this step, we'll define all services units (SU) necessary for our scenario.{color}


{color:#333333}{*}{_}4.3) jbi.xml{_}{*}{color}
h1. *jbi.xml*

{color:#333333}Each SU has its own jbi.xml file. Let's examine what's needed to make this file KPI-specific. We'll take jbi.xml from su-KPI-FootballEIPService-consume-In as an example.{color}
{color:#333333}The value of this tag is the name of related stylesheet.{color}

{color:#333333}{*}{_}4.4) Stylesheet (.xsl) configuration{_}{*}{color}
h1. *Stylesheet (.xsl) configuration*

{color:#333333}For the time being, data collect can only be performed on "In" "type Service Units.{color}