When using BAW Case, you should always use the external CPE setup. The embedded CPE, as Mikhail mentions, is really just for transient doc storage for process attachments vs how case uses its CPE object store as a system of record (long lived and lots of objects).
Most customers upgrading from IBM Case Manager to BAW Case just point the BAW install at their existing case object stores. That way, after the install, everything is just as they left it. All of your existing case solution projects are sitting in the unpromoted case project landing page and can be edited and deployed just like before with the new BAW code. All your deployed case solutions and their data will also still be in your Navigator desktop just like before. Only difference is that the case code is now begin run off the BAW server instead of off the Nav server where it was probably installed in ICM 53x.
Once you promote a case project, it is updated from being just the previous SDF package to a TWX package that still includes the original SDF but now also has a place to store any of the process and UI related artifacts that we gain from the BAW Process side. Again, after promoting, your case project moves to the main Workflow Center project page and can be opened and edited and deployed again exactly as before. The main difference now is that some new features will show up in Case Builder relating to those native BAW processes under case activities and building case UIs using the client-side human services framework (inherited from the BAW process side as well).
------------------------------
DAVE PERMAN
------------------------------
Original Message:
Sent: Wed August 17, 2022 07:11 AM
From: Sameera Wijayarathne
Subject: Content management capabilities in BAW
Hi @YOLANDA YATES,
Yes, I wanted to know about an existing BAW environment as explained by Mikhail.
Thanks for your feedback.
------------------------------
Sameera Wijayarathne
Sri Lanka
Original Message:
Sent: Tue August 16, 2022 10:16 PM
From: YOLANDA YATES
Subject: Content management capabilities in BAW
Hi,
from your request I am trying to understand if you have an existing BAW install and you either want to create a workflow using case and content artefacts or you want to import an existing case solution. Can you please clarify?
Additionally, for you existing BAW environment, as per Mikhail's comments, what was the installation type - was it a BAW install with a separate FileNet and Navigator instance, and did the install include the case components?
Regards,
Yo
------------------------------
YOLANDA YATES
Original Message:
Sent: Tue August 16, 2022 07:10 AM
From: Sameera Wijayarathne
Subject: Content management capabilities in BAW
Hi,
We are clear that existing Filenet, Case Manager customers can migrate to BAW after upgrading existing components to the latest versions.
*Can existing BAW customers get deployed case manager and FileNet content management capabilities in their environments?
Appreciate your feedback
TIA
------------------------------
Sameera Wijayarathne
Sri Lanka
------------------------------