1. What is a Coach?
Ans: Coach is a human activity in BPM Lombardi. When we build human service we usually include Coaches which provide the interface for the end-user interaction.
2. What is a Coach View?
Ans: Coach view provides the user interface elements and layout for the Coach.
Each Coach View can contain one or more other Coach Views, which creates a parent-child relationship between these Coach Views.
At run time, the parent Coach View is rendered as a "<div></div>" tag that contains a nested
"<div></div>" tag for each child Coach View.
Each Coach View can also have a binding to a business object, CSS code to control its visual layout and JavaScript to define its behavior.
3. What is the Architecture of IBM BPM?
Ans:
4. What are the key components of BPM?
Ans:
1. Process Server
2. Process Portal
3. Process Designer
4. Process Center
5. Process Center Console
6. Performance Data Warehouse
7. Process Admin Console
5. Explain about Error Handling capabilities in IBM BPM?
Ans: Error handling is of BPD level and Service level.
- Error end events in processes and services that throw errors. You can assign error codes and error data to errors that are thrown by the error end events.
- Error intermediate events in processes and services that catch errors.
- Error start events in processes event sub-processes that catch errors.
6. What is BPD?
Ans: To model a process, you must create a business process definition (BPD). A BPD is a reusable model of a process, defining what is common to all run time instances of that process model.
A BPD can include a lane for each system or group of users who participate in a process. A lane is the container for all the activities to be carried out by a specific group of users or by a system.
7. In how many ways BPD can be divided?
Ans: BPD can be divided into lanes and milestones. The horizontal lines are called Lanes and vertical ones are called Milestones.
Milestone is deprecated in V8.5. Now, It support phase instead of milestone.
8. Different types of exposing of a BPD?
Ans: Three diferent types, they are as follows
- Exposed to Start
- Expose Business Data
- Expose Performance Metrics
- From Process Portal.
- From Web Service.
- UCA( JMS ).
- Java API (startPeocessByName).
Ans: IBM Business Process Manager (IBPM) provides a platform on which Business Processes can be described, implemented, executed and monitored.
13. What is the difference between process app and toolkit?
Ans: Process App is deployable but toolkit is not deployable it should be integrate.
14. How will you maintain version in bpm?
Ans: By creating a snapshot. Snapshot is as simple as version management.
15. How will you access processes in BPM?
Ans: You can Start, Stop, Control and Monitor Processes using Process Portal.
16. What is the current version available in market for IBM BPM?
Ans: Version 8.6 (as of May'18).
17. What is UCA?
Ans: Under Cover Agents are used to send and receive message with in teamwork’s. The body of the message is defined by teamwork’s service that is attached to the UCA.
18. What are the different types of UCA's?
Ans: Message event and Timer event.
Message event is used to receive or send messages.
Timer event is mostly used as process scheduler's.
19. What is Durable Subscription?
Ans: When a message is sent to an user who is offline, the message waits in the queue and gets delivered when the user appears online again.
20. What is Event Listener?
Ans:
1. An event listener is a widget that is adds to our BPD. It basically tells our process to do something if an event occurs.
2. An event is anything that may happen outside our process or in our process that effects how our process runs.
3. Event listener cannot be added to service layer. Presently they are used in our business process layer.
21. What are the different types of Event Listener’s?
Ans: Two types of Event Listeners are available
1. Start message Event Listener.
2. Intermediate message Event Listener.
22. What is Start message Event Listener?
Ans: When the UCA reaches its end point. It will cause a new Business process to start.
The output of the UCA should be used to set the starting values of variables within the business process.
There is no concept of co-relation in start message event because it is creating a new BPD instance and such there is no data to compare it to.
23. What is Intermediate message Event Listener?
Ans: Intermediate message Event takes place in running Business process.
They tell the Business process to move a token forward in the process.
An Intermediate listener move forward only if event output data matches with the co-relation data in the business process.
24. What are the different types of Intermediate Event Listeners?
Ans:
- Message.
- Content.
- Timer.
- Tracking.
- Auto-tracking: Automatically captures data from tracking points at the entry and exit of each item in a BPD (for example, services, activities, and gateways).
- Tracking groups:Provide more control over tracked data. For example, use tracking groups track a selected group of process variables across multiple BPDs or process applications and to store tracking points for a timing interval.
- Both:You can take advantage of both tracking methods in a single BPD. If you use both autotracking and tracking groups, you can create a timing interval.
- Enable autotracking.
- Add tracking points to the business process definition.
- Create a tracking group to hold the timing interval data (make sure to add each tracking point to the tracking group you created).
29. Explain about Routing?
Ans: Routing is mainly used to assign task to Particular Participant or Particular group. Same participant performing one or more tasks.( Or) Assigning same participant to one or more activities.
30. What is serialization?
Ans: Serialization is mainly used to convert the XML to the Teamwork’s Object.
When we use web service integration service we will use serialization. The output of web service is XML So, we need to convert it to Team work’s Object.
31. Explain About SLA?
Ans: SLA full form is Service Level Agreement. It mainly used to do work timely manner fashion
Simply SLA is an Agreement Between Two People.
32. What are Variables(Business Objects) in IBM BPM?
Ans: Business objects are called variables in Teamworks represent the data that provides the data that provides the business context to a running process. There are two types of variables -Simple And Complex variables have different scopes- private Input and Output.
33. Different types of visibilities in IBM BPM?
Ans: Default, Readonly, None, Hidden, Required.
34. In production one instance has been failed due to some business object has bad data or null values, How will you inject data on runtime in production?
Ans: IBPM provide rest api which operation name is setData through that we can inject values.
35. What are different types of Human Tasks?
Ans:
- To-do task – a service schedules a piece of work for a person to perform.
- Invocation task – a person uses a service.
- Collaboration task – one person assigns work to another person.
- Administration task – a person is granted administrative powers over an activity or process.
- Timer
- Message
- Error
41. Explain about Web Services?
Ans: Web services are two types. Inbound and Outbound web services.
Inbound web services are used if external system wants to call into IBPM.
Outbound web services are used if IBPM want to use external system/Application.
In two ways it can be configurable
- Provide Inline Configuration.
- From Process App Settings.
- Not Exposed
- Administration service.
- Startable service.
- Dashboard.
- URL.
- Web File: Mostly we add image, .css files into this and these can be accessible in coach views.
- Server File: We add jar, js files into this category.
- Design File: We add .xsl files (text/xml, application/xml) to overide transform xsl in one or more heritage coaches.
Ans: event.propery == "varaible_name".
46. How will you identify a complex variable got changes in coach view?
Ans: Check below link for easier understanding.
https://www.ibm.com/support/knowledgecenter/en/SSFTBX_8.0.1/com.ibm.wbpm.wle.editor.doc/develop/topics/rbindingdata.html
1. Performance & Scalability Scenarios
Q1. A process is very slow when multiple users submit requests simultaneously. How do you analyze and fix it?
Answer (Structured):
-
Analyze
-
Check Performance Admin Console
-
Review long-running services
-
Enable tracking points for bottlenecks
-
Analyze DB locks and slow queries
-
-
Fix
-
Convert synchronous integrations to asynchronous
-
Split long services into smaller services
-
Reduce large Business Objects
-
Use parallel gateways where possible
-
Tune database indexes
-
π Real-world example: Converted a REST call to async + callback → reduced response time by ~40%.
2. Production Issue Handling
Q2. A production instance is stuck and not moving forward. What will you do?
Answer:
-
Identify stuck activity in Process Admin Console
-
Check:
-
Assigned user/team availability
-
Service failure logs
-
Timer or message events
-
-
Actions:
-
Retry the failed service
-
Skip activity (if business allows)
-
Move token to next activity
-
Fix issue and restart instance
-
π Mention: Never delete instances in production unless approved.
3. Snapshot & Deployment Scenarios
Q3. You deployed a snapshot, and users report a critical issue. How do you fix it?
Answer:
-
Snapshots are immutable
-
Options:
-
Roll back to previous stable snapshot
-
Fix issue → create new snapshot → deploy
-
-
For running instances:
-
Let old instances finish on old snapshot
-
New instances start on new snapshot
-
4. Data & Variable Handling
Q4. A process fails due to OutOfMemoryError. What could be the reason?
Answer:
Common causes:
-
Large lists stored in process variables
-
Storing documents/images in BOs
-
Too many tracking points
-
Infinite loops in scripts
Fix:
-
Use private variables
-
Store large data externally (DB/File system)
-
Limit tracking
-
Clean unused variables
5. Integration Scenarios
Q5. External REST service is slow/unreliable. How do you handle it?
Answer:
-
Use asynchronous Integration Service
-
Implement:
-
Timeout handling
-
Retry mechanism
-
Error boundary events
-
-
Log failure details
-
Use Message Events for callback
6. Human Service & UI Issues
Q6. Users complain that a coach screen takes too long to load. What do you do?
Answer:
-
Avoid heavy logic in Coach load
-
Move logic to pre-load service
-
Reduce large BO bindings
-
Use pagination for tables
-
Reuse Coach Views
7. Authorization & Security
Q7. Only certain users should see/perform an activity. How do you implement this?
Answer:
-
Create Team
-
Map team to:
-
User task
-
Service
-
-
Integrate with LDAP groups
-
Validate authorization at service level
8. Error Handling Scenario
Q8. How do you handle a failure in the middle of a long process?
Answer:
-
Use:
-
Boundary Error Events
-
Exception Subprocess
-
Try-Catch in Integration Services
-
-
Notify support team via email/log
-
Allow manual retry or correction
9. Migration Scenario (IBM BPM → BAW)
Q9. How did you approach BPM to BAW migration?
Answer:
-
Analyze existing snapshots
-
Resolve deprecated features
-
Update Java & REST integrations
-
Validate:
-
Coaches
-
Security
-
Integrations
-
-
Perform regression testing
-
Deploy on BAW runtime
π Mention challenges: UI differences, API changes, performance tuning.
10. Production Support Scenario
Q10. How do you handle high-priority (P1) production incidents?
Answer:
-
Immediate triage
-
Identify impacted instances
-
Apply temporary workaround
-
Communicate with stakeholders
-
Permanent fix via new snapshot
-
RCA documentation
11. Concurrency & Transaction Scenario
Q11. Two users update the same process data. How do you avoid conflicts?
Answer:
-
Use lock mechanisms
-
Minimize shared data
-
Use service-level transactions
-
Validate data before commit
12. Timer & SLA Scenario
Q12. Business requires SLA tracking and escalation. How do you implement it?
Answer:
-
Use Timer Intermediate Events
-
Escalation via:
-
Email service
-
Reassignment to higher role
-
-
Track SLA with milestones
13. Database Scenario
Q13. BPM DB size is growing rapidly. What action do you take?
Answer:
-
Archive completed instances
-
Clean tracking data
-
Purge old snapshots
-
Optimize DB cleanup scripts
14. Real Interview Closing Question
Q14. Describe a challenging BPM/BAW issue you solved.
Sample Answer:
“We faced performance degradation due to synchronous integrations and large BO usage. I redesigned the process to use async services, reduced variable size, optimized DB queries, and created a new snapshot. This improved throughput and stabilized production.”
How to Answer in Interviews (Important)
Always structure answers as:
Problem → Analysis → Action → Result

Excellent information for quick reference
ReplyDeleteThank You
Find a better way to enjoy a casino at the casino - Dr.MD
ReplyDeleteThe benefits of gambling are vast. The κ±°μ μΆμ₯μλ§ majority μν₯ μΆμ₯λ§μ¬μ§ of these advantages μμ μΆμ₯μλ§ come directly from the use μμ£Ό μΆμ₯μλ§ of a game of μ μ£Ό μΆμ₯λ§μ¬μ§ chance. The