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

compared with
Version 4 by Olivier Fabre
on May 28, 2010 11:38.

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

Changes (20)

View Page History


!ViewSu-KPI.png|thumbnail,border=1,align=center!







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



!Studio-KPI.png|thumbnail,border=1,align=center!







{color:#333333}Watched Service(s): herein, we'll choose the endpoints that will be watched through notifications emissions. In our example, select the three available endpoints then click on Next.{color}


!SelectEndpoint.png|thumbnail,border=1,align=center!







{color:#333333}Watcher Configuratio : herein we'll fill in the states of our SU: In, Out, Status or Fault.{color}



!TypeSuKPI.png|thumbnail,border=1,align=center!







{color:#333333}Deployment Configuration: herein we'll give a human-readable name for our sa-kpi: e.g. Sa-KPI-tutorial.{color}



!ChooseSA-KPIName.png|thumbnail,border=1,align=center!







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



!su-EIP-In-jbi-xml.png|thumbnail,border=1,align=center!







{color:#333333}Here, important informations are enclosed in mark-up tags:{color}{color:#008080}<{color}{color:#3f7f7f}kpi:TopicExpressionContent{color}{color:#008080}>{color}{color:#1a1a1a}petals:component/cdk/producer/{color}{color:#800000}in{color}{color:#1a1a1a}\[@wstop:topic='true'\]{color}{color:#008080}</{color}{color:#3f7f7f}kpi:TopicExpressionContent{color}{color:#008080}>{color}

{color:#333333}In our example, we'll want informations from both su-KPI-FootballPoolEIPService-consume-In and su-KPI-copyResponse-consume-In.{color}

{color:#333333}{*}Stylesheet su-KPI-FootballPoolEIPService-consume-In.xsl{*}{color}{color:#333333}&nbsp;{color} !su-KPI-FileTransfert-In-Style.png|thumbnail,border=1,align=center!
One essential information to retrieve herein is processType. Its value must be the same for all stylesheets attached to a same process. This value allows linking between flows saved in database and related Petals View's referential. This value has to be unique for each process.

# One essential information to retrieve herein is processType. Its value must be the same for all stylesheets attached to a same process. This value allows linking between flows saved in database and related Petals View's referential. This value has to be unique for each process.

{color:#333333}Between&nbsp;{color}{color:#008080}<{color}{color:#3f7f7f}wsnebm:params{color}{color:#008080}>{color}{color:#333333}&nbsp;{color}{color:#008080}</{color}{color:#3f7f7f}wsnebm:params{color}{color:#008080}>{color}{color:#333333}&nbsp;{color}{color:#1a1a1a}tag we'll fill in the parameter we want to retrieve to display it in Petals View.{color}

{color:#333333}The value to fill in is:&nbsp;{color}{color:#008080}<{color}{color:#3f7f7f}xsl:value-of{color}{color:#333333}&nbsp;{color}{color:#7f007f}select{color}{color:#008080}={color}{color:#2a00ff}"//*\[local-name()='sCountryName'\]/text()"{color}{color:#008080}/>{color}{color:#333333}&nbsp;{color}


!su-KPI-EIP-In-Style-Full.png|thumbnail,border=1,align=center!


{color:#333333}{*}Stylesheet su-KPI-copyResponse-consume-In.xsl{*}{color}



!su-KPI-FileTransfert-In-Style-Full.png|thumbnail,border=1,align=center!







{color:#333333}Your su-kpi are ready. All that's left to do is export them so we can deploy them in Petals ESB.{color}



!export-su-kpi.png|thumbnail,border=1,align=center!







{color:#333333}Repeat for each su-kpi.{color}