This document discusses steps for designing an application architecture from a starting point of "HelloWorld" to production-ready. It covers: 1) starting with a basic UI, 2) factors to consider like the UI, directory server, documents, etc, 3) implementing business intelligence from the start, 4) preparing for higher volumes, and 5) using Scrum methodologies. The overall goal is providing a structured approach to application architecture design.

1. From HelloWorld to Production
Luc Gorissen
Designing ACM solutions

2. Luc Gorissen
Previous employers:
- KPN Research
- CMG Wireless Data Solutions
- OraVision
- Oracle
Focus:
- BPM and SOA Suite
luc.gorissen@amis.nl
+31 6 3622 4226
@LucGorissen
No, no, no
LinkedIn

3. 3
What to expect?
• Step-by-step
• Real-life experience
Application Architecture

4. 4
Topics
Higher volumes
Scrum
Starting point:
<HelloWorld/>
Always consider:
• UI
• Directory Server
• DMS / RM
• ‘Real’ functionality
Switch on the Light:
1 2 3
4 5
Closing
Final
ACM Solution
Architecture
6
BI
BAM
Designing an ACM solution Application Architecture in steps

5. 5
HelloWorld
Application Architecture
browsercase
1. starting point

6. 6
User Interface
ACM/BPM Platform
-
Case Control
SOAP API
Custom API
REST API
2. Always consider
ADF JET companyACM/BPM WorkSpace
Custom API
Service Bus
More powerful API on
ACM/BPM platform
Pick right technology combination
–
for different user groups

7. 7
User Interface
2. Always consider
ACM/BPM Platform
-
Case Control
SOAP API
Custom API
REST API
ADF JET companyACM/BPM WorkSpace
Custom API
Service Bus
Application Architecture

8. 8
User Interface
ACM/BPM Platform
-
Case Control
SOAP API
Custom API
REST API
2. Always consider
ADF JET companyACM/BPM WorkSpace
Custom API
Service Bus
Cache API session context when using the API
Enduser
Cache
Enduser

9. 9
User Interface
ACM/BPM Platform
-
Case Control
SOAP API
Custom API
REST API
2. Always consider
ADF JET companyACM/BPM WorkSpace
Custom API
Service Bus
System user &
Cache API session context when using the API
Enduser
SSL
Systemuser
Cache

10. 10
User Interface
2. Always consider
Application Architecture

11. 11
Directory Server
Application Architecture
2. Always consider
Dedicated directory server?
Tune for performance
WebLogic configuration of
3 directory servers

12. 12
Documents
Application Architecture
2. Always consider
Pre-integrated or not?
Authorization when opening
up the DMS
A-synchronous…

13. 13
Object Registries
2. Always consider
ACM/BPM Platform
-
Case Control
Regulations Customers Licenses
‘Back-end’ system data?
Stand-alone application?
Referential integrity
Management screens
Only steering data in
case/process

14. 14
Object Registries
Application Architecture
2. Always consider

15. 15
And …
Document Generation / Digital Document Signing
SOA Services
Select and integrate
On same platform?
Make that Service Architecture Layering model
On same platform?
Delete the ‘default’ partition
2. Always consider

16. 16
Application Architecture
2. Always consider

17. 17
Business Intelligence
Business Activity Monitoring
So, our Scrum development team worked to get a 'minimum viable set‘
It's not complete, but let's start using it.
BI
BAM
But … what’s happening?
3. Switch on the Light

18. 18
Business Intelligence
Business Activity Monitoring
3. Switch on the Light
Install BAM from the start into your domain
No BI on dehydration store
Business will request all-or-nothing: don’t wait for that!

19. 19
3. Switch on the light
Application Architecture
3. Switch on the Light

20. 20
4. Higher volumes
Improve Exception Handling
Clean consoles
Move non-steering case data into Case Registry
Save Case History (in Case Registry?)
Search function for Case (History)
4. Higher volumes

21. 4.Highervolumes
21
4. Higher volumes
Application Architecture

22. 22
Scrum
Scrum team with 2 weekly delivery cycles…
5. Scrum
Highly automated tests
Nightly builds & regression tests
Highly automated deployments

23. 23
Scrum
Scrum team with 2 weekly delivery cycles…
5. Scrum
CustomerComplaint 15.08
CustomerComplaint 15.12
CustomerComplaint 16.18
CustomerComplaint 15.20
CustomerComplaint 15.10
Case Versions Case Instances

24. 24
Scrum
Scrum teams with 2 weekly delivery cycles…
5. Scrum
High # version – slow start-up time
High # versions – confused end users
High # versions – confused application management
High # versions – confused developers

25. 25
Re-startable cases
Case
ACM Case
Activity
Case
Activity
Case
Activity
External Case Activities
Already solves problems…
Case
ACM
Case
Activity
Case
Activity
Case
Activity
5. Scrum

26. 26
Re-startable cases
Case
ACM Case
Activity
Case
Activity
Case
Activity
Re-startable cases
Case
ACM
Case
Activity
Case
Activity
Case
Activity
5. Scrum

27. 27
Scrum
With re-start…
5. Scrum
CustomerComplaint 15.08
CustomerComplaint 15.12
CustomerComplaint 16.18
CustomerComplaint 15.20
CustomerComplaint 15.10
Case Versions
Case Instances

28. 28
Re-start case
New Case
Old Case
abortCase
transformCaseInfo
Re-startcase getCaseInfo
initializeCase
updateStatusCase
Re-start of cases is not easy
5. Scrum

29. 29
Case re-starts
Application Architecture
5. Scrum

30. 30
6. Final Architecture:
the shopping list
Questions?
6. Closing

31. 31
6. Final Architecture:
the shopping list
Easier?
6. Closing

32. 32