Jämförda versioner

Nyckel

  • Dessa rader lades till.
  • Denna rad togs bort.
  • Formateringen ändrades.

Innehållsförteckning
maxLevel3

UNDER UPPBYGGNAD!

Loggning

Logfiler

Engagemangsindex applikationsloggar lagras i foldern <MULE-HOME>/logs. EI's frontend- och backend-applikation har vars en log-fil:

  • mule-app-skltp-ei-application-mule-frontend-app-1.0.0.log
  • mule-app-skltp-ei-application-mule-backend-app-1.0.0.log

För mer information om EI's uppdelning i frontend- och backend-applikation se avsnittet deployment-vy i EI's SAD.

Förväntade sekvenser av log-händelser

I denna sektion beskrivs förväntade sekvenser av log-händelser för de användningsfall som beskrivs i EI's SAD.

...

För att beskriva de förväntade sekvenserna används skltp's "realtids log viewer".

Användningsfallen "uppdatering", "bearbetning" och "notifiering" i skltp's "realtids log viewer".

Här beskrivs förväntade sekvenser av log-händelser för användningsfallen:

...

  1. Ett källsystem med HSA-ID "client" skickar in en uppdatering via EI's update tjänst.
  2. EI's update-tjänst lägger uppdateringen på JMS-kön med namnet "skltp.ei.process" och returnerar ett svar till källsystem
  3. EI's process-tjänst uppdaterar databasen och lägger en notifiering om uppdateringen på JMS-topicen med namnet "skltp.ei.notify"
  4. EI's notifierings-tjänst notifierar en prenumerant med HSA-ID "demo-ei-notify-publisher"

Användningsfallen "uppdatering", "bearbetning" och "notifiering", så ser det ut i logfilerna.

Uppdatering

  1. Ett anrop kommer in via virtuell tjänst för Update i VP (https://localhost:20000/vp/Update/1/rivtabp21) och routas vidare till EI's frontend-applikation och dess Update-tjänst på http://localhost:8081/skltp-ei/update-service/v1 
  2. Ett meddelande läggs på kön (jms://skltp.ei.process) för bearbetning.
Kodblock
titlemule-app-skltp-ei-application-mule-frontend-app.log
2013-11-05 09:30:54,968 INFO  se.skltp.ei.intsvc.log.EiOverrideDefaultEventLogger - soi-toolkit.log
** logEvent-info.start ***********************************************************
IntegrationScenarioId=
ContractId=
LogMessage=req-in
ServiceImpl=update-service
Host=MacBook-Pro.local (33.33.33.33)
ComponentId=94261f80-45f4-11e3-8a98-cd2487e2763a
Endpoint=http://localhost:8081/skltp-ei/update-service/v1 (POST on /skltp-ei/update-service/v1)
MessageId=966f2547-45f4-11e3-8a98-cd2487e2763a
BusinessCorrelationId=
BusinessContextId=
ExtraInfo=
Payload=org.apache.commons.httpclient.ContentLengthInputStream@5b9a1072
** logEvent-info.end *************************************************************
2013-11-05 09:30:55,054 INFO  se.skltp.ei.intsvc.log.EiOverrideDefaultEventLogger - soi-toolkit.log
** logEvent-info.start ***********************************************************
IntegrationScenarioId=
ContractId=
LogMessage=msg-out
ServiceImpl=update-service
Host=MacBook-Pro.local (33.33.33.33)
ComponentId=94261f80-45f4-11e3-8a98-cd2487e2763a
Endpoint=jms://skltp.ei.process
MessageId=966f2547-45f4-11e3-8a98-cd2487e2763a
BusinessCorrelationId=
BusinessContextId=
ExtraInfo=
Payload=<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:Update xmlns:ns2="urn:riv:itintegration:engagementindex:UpdateResponder:1" xmlns="urn:riv:itintegration:engagementindex:1"><ns2:engagementTransaction><deleteFlag>false</deleteFlag><engagement><registeredResidentIdentification>191212121212</registeredResidentIdentification><serviceDomain>urn:riv:scheduling:timebooking</serviceDomain><categorization>booking</categorization><logicalAddress>1212121212</logicalAddress><businessObjectInstanceIdentifier>SE100200400-600</businessObjectInstanceIdentifier><clinicalProcessInterestId>NA</clinicalProcessInterestId><sourceSystem>XXX100200400-600</sourceSystem><dataController>dataController</dataController><owner>Inera</owner></engagement></ns2:engagementTransaction></ns2:Update>
** logEvent-info.end *************************************************************



 

I ActiveMQ konsol ser att meddelande lagts på kö (om man är snabb)

 

Image Added

Bearbetning

  1. EI's backend-applikation läser meddelandet på kön (jms://skltp.ei.process)
  2. EI's backend-applikation skickar ett meddelande till kön (jms://topic:skltp.ei.notify) för att notifiera producenter om att det kommit en uppdatering. 

 

Kodblock
titlemule-app-skltp-ei-application-mule-backend-app.log
** logEvent-info.start ***********************************************************
IntegrationScenarioId=
ContractId=
LogMessage=msg-in
ServiceImpl=process-service
Host=MacBook-Pro.local (33.33.33.33)
ComponentId=f5986a4c-45f4-11e3-b6fd-4f78c0f8a129
Endpoint=jms://skltp.ei.process?connector=soitoolkit-jms-connector
MessageId=f8257cfa-45f4-11e3-b6fd-4f78c0f8a129
BusinessCorrelationId=
BusinessContextId=
ExtraInfo=
Payload=<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:Update xmlns:ns2="urn:riv:itintegration:engagementindex:UpdateResponder:1" xmlns="urn:riv:itintegration:engagementindex:1" xmlns:ns3="urn:riv:itintegration:engagementindex:ProcessNotificationResponder:1"><ns2:engagementTransaction><deleteFlag>false</deleteFlag><engagement><registeredResidentIdentification>191212121212</registeredResidentIdentification><serviceDomain>urn:riv:scheduling:timebooking</serviceDomain><categorization>booking</categorization><logicalAddress>1212121212</logicalAddress><businessObjectInstanceIdentifier>SE100200400-600</businessObjectInstanceIdentifier><clinicalProcessInterestId>NA</clinicalProcessInterestId><sourceSystem>XXX100200400-600</sourceSystem><dataController>dataController</dataController><owner>Inera</owner></engagement></ns2:engagementTransaction></ns2:Update>
** logEvent-info.end *************************************************************
2013-11-05 09:33:38,951 INFO  se.skltp.ei.intsvc.log.EiOverrideDefaultEventLogger - soi-toolkit.log
** logEvent-info.start ***********************************************************
IntegrationScenarioId=
ContractId=
LogMessage=msg-out
ServiceImpl=process-service
Host=MacBook-Pro.local (33.33.33.33)
ComponentId=f5986a4c-45f4-11e3-b6fd-4f78c0f8a129
Endpoint=jms://topic:skltp.ei.notify
MessageId=f8257cfa-45f4-11e3-b6fd-4f78c0f8a129
BusinessCorrelationId=
BusinessContextId=
ExtraInfo=
Payload=<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:Update xmlns:ns2="urn:riv:itintegration:engagementindex:UpdateResponder:1" xmlns="urn:riv:itintegration:engagementindex:1" xmlns:ns3="urn:riv:itintegration:engagementindex:ProcessNotificationResponder:1"><ns2:engagementTransaction><deleteFlag>false</deleteFlag><engagement><registeredResidentIdentification>191212121212</registeredResidentIdentification><serviceDomain>urn:riv:scheduling:timebooking</serviceDomain><categorization>booking</categorization><logicalAddress>1212121212</logicalAddress><businessObjectInstanceIdentifier>SE100200400-600</businessObjectInstanceIdentifier><clinicalProcessInterestId>NA</clinicalProcessInterestId><sourceSystem>XXX100200400-600</sourceSystem><dataController>dataController</dataController><owner>Inera</owner></engagement></ns2:engagementTransaction></ns2:Update>
** logEvent-info.end ************************************************************* 

 

I ActiveMQ konsol ser att meddelande lagts på kö (om man är snabb)

Image Added

Notifiering

  1. EI's backend-applikation har en registrerad intressent för notifieringar och läser av kön (jms://topic:skltp.ei.notify)
  2. EI's backend-applikation skickar ett anrop ProcessNotification (i detta fallet till en teststubbe på http://localhost:8083/skltp-ei/process-notification-teststub-service/v1) till den registrerade intressenten 
  3. EI's backend-applikation får ett ack på att anropet gått bra

 

Kodblock
titlemule-app-skltp-ei-application-mule-backend-app.log
2013-11-05 09:35:46,966 INFO  se.skltp.ei.intsvc.log.EiOverrideDefaultEventLogger - soi-toolkit.log
** logEvent-info.start ***********************************************************
IntegrationScenarioId=
ContractId=
LogMessage=msg-in
ServiceImpl=notify-service-HSA_ID_A
Host=MacBook-Pro.local (33.33.33.33)
ComponentId=4062fd70-45f5-11e3-8341-2193df8d79ad
Endpoint=jms://topic:skltp.ei.notify?connector=soitoolkit-jms-connector
MessageId=447d410c-45f5-11e3-8341-2193df8d79ad
BusinessCorrelationId=
BusinessContextId=
ExtraInfo=
Payload=<?xml version="1.0" encoding="UTF-8" standalone="yes"?><ns2:Update xmlns:ns2="urn:riv:itintegration:engagementindex:UpdateResponder:1" xmlns="urn:riv:itintegration:engagementindex:1"><ns2:engagementTransaction><deleteFlag>false</deleteFlag><engagement><registeredResidentIdentification>191212121212</registeredResidentIdentification><serviceDomain>urn:riv:scheduling:timebooking</serviceDomain><categorization>booking</categorization><logicalAddress>1212121212</logicalAddress><businessObjectInstanceIdentifier>SE100200400-600</businessObjectInstanceIdentifier><clinicalProcessInterestId>NA</clinicalProcessInterestId><sourceSystem>XXX100200400-600</sourceSystem><dataController>dataController</dataController><owner>Inera</owner></engagement></ns2:engagementTransaction></ns2:Update>
** logEvent-info.end *************************************************************
-
-
-
2013-11-05 09:35:46,979 INFO  se.skltp.ei.intsvc.log.EiOverrideDefaultEventLogger - soi-toolkit.log
** logEvent-info.start ***********************************************************
IntegrationScenarioId=
ContractId=
LogMessage=req-out
ServiceImpl=notify-service-HSA_ID_A
Host=MacBook-Pro.local (33.33.33.33)
ComponentId=4062fd70-45f5-11e3-8341-2193df8d79ad
Endpoint=http://localhost:8083/skltp-ei/process-notification-teststub-service/v1 (POST)
MessageId=447d410c-45f5-11e3-8341-2193df8d79ad
BusinessCorrelationId=
BusinessContextId=
ExtraInfo=
Payload=org.mule.module.cxf.transport.MuleUniversalConduit$1@24206bb5
** logEvent-info.end *************************************************************
-
-
-
** logEvent-info.start ***********************************************************
IntegrationScenarioId=
ContractId=
LogMessage=resp-in
ServiceImpl=notify-service-HSA_ID_A
Host=MacBook-Pro.local (33.33.33.33)
ComponentId=4062fd70-45f5-11e3-8341-2193df8d79ad
Endpoint=jms://topic:skltp.ei.notify
MessageId=44824943-45f5-11e3-8341-2193df8d79ad
BusinessCorrelationId=
BusinessContextId=
ExtraInfo=
Payload=Missing jaxbContext or deprecated jaxb2xml injection, can't marshal JAXB object of type: riv.itintegration.engagementindex.processnotificationresponder._1.ProcessNotificationResponseType
** logEvent-info.end *************************************************************

 

Användningsfallet "sök innehåll"

Här beskrivs förväntade sekvenser av log-händelser för användningsfallen:

6. Tjänstekonsument begär information från ett engagemangsindex

TBS

Användningsfall som saknar förväntade sekvenser av log-händelser

2. Engagemangsindex hämtar uppdateringar från ett källsystem
3. Federerat engagemangsindex uppdaterar engagemangsindex

Användningsfall "notifiering ", logghändelser vid registrering av lyssnare på notifieringar, uppstart av EI backend

  1. Vid uppstart av EI backend gör ett anrop till VP's http://localhost:8080/vp/GetLogicalAddresseesByServiceContract/1/rivtabp20 för att hämta producenter av tjänstekontraktet processnotification (registrerade i TAK) 
  2. För varje producent av tjänstekontraktet processnotification startas ett flöde

 

Kodblock
titlemule-app-skltp-ei-application-mule-backend-app.log
** logEvent-info.start ***********************************************************
IntegrationScenarioId=
ContractId=
LogMessage=msg-in
ServiceImpl=get-logical-addressees-service
Host=MacBook-Pro.local (33.33.33.33)
ComponentId=4062fd70-45f5-11e3-8341-2193df8d79ad
Endpoint=vm://get-logical-addressees
MessageId=435ae0d7-45f5-11e3-8341-2193df8d79ad
BusinessCorrelationId=
BusinessContextId=
ExtraInfo=
Payload=
** logEvent-info.end *************************************************************
2013-11-05 09:35:45,178 INFO  se.skltp.ei.intsvc.log.EiOverrideDefaultEventLogger - soi-toolkit.log
** logEvent-info.start ***********************************************************
IntegrationScenarioId=
ContractId=
LogMessage=req-out
ServiceImpl=get-logical-addressees-service
Host=MacBook-Pro.local (33.33.33.33)
ComponentId=4062fd70-45f5-11e3-8341-2193df8d79ad
Endpoint=http://localhost:8080/vp/GetLogicalAddresseesByServiceContract/1/rivtabp20 (POST)
MessageId=435ae0d7-45f5-11e3-8341-2193df8d79ad
BusinessCorrelationId=
BusinessContextId=
ExtraInfo=
Payload=org.mule.module.cxf.transport.MuleUniversalConduit$1@57148683
** logEvent-info.end *************************************************************
2013-11-05 09:35:45,241 INFO  se.skltp.ei.intsvc.integrationtests.getlogicaladdressees.GetLogicalAddresseesByServiceContractTestProducerLogger - Test producer called with x-rivta-original-serviceconsumer-hsaid: ei-hsa-id
2013-11-05 09:35:45,275 INFO  se.skltp.ei.intsvc.integrationtests.getlogicaladdressees.GetLogicalAddresseesByServiceContractTestProducer - GetLogicalAddresseesByServiceContractTestProducer received a GetLogicalAddresseesByServiceContract request for hsa-id vp-hsa-id and service contract urn:riv:itintegration:engagementindex:ProcessNotificationResponder:1
2013-11-05 09:35:45,289 INFO  se.skltp.ei.intsvc.log.EiOverrideDefaultEventLogger - soi-toolkit.log

 
 
 
** logEvent-info.start ***********************************************************
IntegrationScenarioId=
ContractId=
LogMessage=resp-in
ServiceImpl=get-logical-addressees-service
Host=MacBook-Pro.local (33.33.33.33)
ComponentId=4062fd70-45f5-11e3-8341-2193df8d79ad
Endpoint=vm://get-logical-addressees
MessageId=437d5d07-45f5-11e3-8341-2193df8d79ad
BusinessCorrelationId=
BusinessContextId=
ExtraInfo=
Payload=Missing jaxbContext or deprecated jaxb2xml injection, can't marshal JAXB object of type: riv.itintegration.registry.getlogicaladdresseesbyservicecontractresponder._1.GetLogicalAddresseesByServiceContractResponseType
** logEvent-info.end *************************************************************
2013-11-05 09:35:45,291 INFO  se.skltp.ei.intsvc.log.EiOverrideDefaultEventLogger - soi-toolkit.log
** logEvent-info.start ***********************************************************
IntegrationScenarioId=
ContractId=
LogMessage=resp-out
ServiceImpl=get-logical-addressees-service
Host=MacBook-Pro.local (33.33.33.33)
ComponentId=4062fd70-45f5-11e3-8341-2193df8d79ad
Endpoint=vm://get-logical-addressees
MessageId=437d5d07-45f5-11e3-8341-2193df8d79ad
BusinessCorrelationId=
BusinessContextId=
ExtraInfo=
Payload=Missing jaxbContext or deprecated jaxb2xml injection, can't marshal JAXB object of type: riv.itintegration.registry.getlogicaladdresseesbyservicecontractresponder._1.GetLogicalAddresseesByServiceContractResponseType
** logEvent-info.end *************************************************************
2013-11-05 09:35:45,295 INFO  se.skltp.ei.intsvc.dynamicFlows.Initializer - Found 1 logical addresses for dynamic notify flows
2013-11-05 09:35:45,299 WARN  org.soitoolkit.commons.mule.util.RecursiveResourceBundle - Failed to laod properties from ResourceBundle: ei-config-override, continue with the next bundle
2013-11-05 09:35:45,300 INFO  se.skltp.ei.intsvc.dynamicFlows.CreateDynamicFlows - Loading static flows...
2013-11-05 09:35:45,300 INFO  se.skltp.ei.intsvc.dynamicFlows.CreateDynamicFlows - Stop loading static configurations, loaded 0 config files
2013-11-05 09:35:45,300 INFO  se.skltp.ei.intsvc.dynamicFlows.CreateDynamicFlows - Loading dynamic flows...
2013-11-05 09:35:45,300 INFO  se.skltp.ei.intsvc.dynamicFlows.CreateDynamicFlows - Generate dynamic flow #1 from template file dynamicFlows/notify-service.xml.gt
2013-11-05 09:35:45,724 INFO  se.skltp.ei.intsvc.dynamicFlows.CreateDynamicFlows - Stop loading template files for dynamic flows, loaded 1 config files
2013-11-05 09:35:45,724 INFO  se.skltp.ei.intsvc.dynamicFlows.Initializer - Starting 1 flows...