<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by P8 Hub🍁 on Medium]]></title>
        <description><![CDATA[Stories by P8 Hub🍁 on Medium]]></description>
        <link>https://medium.com/@gihanshamikeliyanage?source=rss-f465db041132------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*VUcjgD6r_HQl8etEQ-22BA.png</url>
            <title>Stories by P8 Hub🍁 on Medium</title>
            <link>https://medium.com/@gihanshamikeliyanage?source=rss-f465db041132------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 19:35:26 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gihanshamikeliyanage/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Capturing Documents/Images Through a Webcam in IBM BAW]]></title>
            <link>https://medium.com/@gihanshamikeliyanage/capturing-documents-images-through-a-webcam-in-ibm-baw-c72ddd74a936?source=rss-f465db041132------2</link>
            <guid isPermaLink="false">https://medium.com/p/c72ddd74a936</guid>
            <category><![CDATA[document-scanning]]></category>
            <category><![CDATA[webcam]]></category>
            <category><![CDATA[ibm-baw]]></category>
            <category><![CDATA[camscanner]]></category>
            <category><![CDATA[image-capture]]></category>
            <dc:creator><![CDATA[P8 Hub]]></dc:creator>
            <pubDate>Wed, 03 Dec 2025 22:27:01 GMT</pubDate>
            <atom:updated>2025-12-03T22:27:01.091Z</atom:updated>
            <content:encoded><![CDATA[<p>One of my banking clients required a solution to capture customer images and supporting documents using a webcam. Their goal was to attach documents and images without relying on a physical scanner.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oDDkD6bkaxeGjn6JPdyvJQ.png" /><figcaption>Default view</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IOhq4YhnirsE00BXjafwhA.png" /><figcaption>Previewing captured image</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1nE_6_XYwWlgO-hgqLj3wg.png" /><figcaption>When camera not available</figcaption></figure><p>To meet this requirement, I developed a reusable webcam widget view in IBM BAW. The output of this view was bound to an <strong>ECMContentStream</strong>, type variable which was then passed to the Document Creation service. The Document Creation service was used to attach the captured items to the corresponding folder in the object store (in this case, the work item’s case folder).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/912/1*-m6OQRprIv36NAxgd4dNMA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/903/1*b2LlAdf5JcKY1r5fR24N7Q.png" /></figure><p>As a further enhancement, I am planning to implement automatic edge detection and edge cropping features, similar to what mobile cam scanners offer.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c72ddd74a936" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to Create Custom Time and Holiday Schedules in IBM BAW]]></title>
            <link>https://medium.com/@gihanshamikeliyanage/how-to-create-custom-time-and-holiday-schedules-in-ibm-baw-ac1d96f8f214?source=rss-f465db041132------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac1d96f8f214</guid>
            <category><![CDATA[baw]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[custom-holiday-schedules]]></category>
            <category><![CDATA[custom-time-schedules]]></category>
            <category><![CDATA[create-and-remove]]></category>
            <dc:creator><![CDATA[P8 Hub]]></dc:creator>
            <pubDate>Wed, 25 Jun 2025 01:00:47 GMT</pubDate>
            <atom:updated>2025-06-25T01:00:47.409Z</atom:updated>
            <content:encoded><![CDATA[<p>To implement custom time and holiday schedules in IBM BAW, you can create a <strong>Service Flow</strong> and run a server script like this once to add custom schedules to the TWHolidaySchedule and TWTimeSchedule variables.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/935/1*_dIqBSMZ0kOW0HDoEksGJQ.png" /></figure><p>This script creates and registers a custom <strong>holiday schedule </strong>named &quot;myHolidaySchedule&quot; with two holidays (June 25 and 26, 2025) and a <strong>time schedule</strong> named &quot;myTimeSchedule&quot; that defines working hours from 9:00 AM to 5:00 PM on Monday to Thursday and Sunday, excluding holidays.</p><p>These schedules are added to the system using tw.system.addHolidaySchedule() and tw.system.addTimeSchedule() to support custom business time calculations in IBM BAW.</p><pre>var holidaySchedule = new tw.object.TWHolidaySchedule();<br>      holidaySchedule.name = &quot;myHolidaySchedule&quot;;<br>      holidaySchedule.dates = new tw.object.listOf.Date();<br>      holidaySchedule.dates[0] = new tw.object.Date();<br>      holidaySchedule.dates[0].parse(&quot;20250625&quot;, &quot;yyyyMMdd&quot;);<br>      holidaySchedule.dates[1] = new tw.object.Date();<br>      holidaySchedule.dates[1].parse(&quot;20250626&quot;, &quot;yyyyMMdd&quot;);<br>tw.system.addHolidaySchedule(holidaySchedule);<br><br>var timeSchedule = new tw.object.TWTimeSchedule();<br>      timeSchedule.name = &quot;myTimeSchedule&quot;;<br>      timeSchedule.excludeHolidays = true;<br>      timeSchedule.periods = new tw.object.listOf.TWTimePeriod();<br>var timePeriod = new tw.object.TWTimePeriod();<br>      timePeriod.startTime = new tw.object.Time();<br>      timePeriod.startTime.parse(&quot;09:00&quot;, &quot;HH:mm&quot;);<br>      timePeriod.endTime = new tw.object.Time();<br>      timePeriod.endTime.parse(&quot;17:00&quot;, &quot;HH:mm&quot;);<br>      timePeriod.monday = true;<br>      timePeriod.tuesday = true;<br>      timePeriod.wednesday = true;<br>      timePeriod.thursday = true;<br>      timePeriod.friday = false;<br>      timePeriod.saturday = false;<br>      timePeriod.sunday = true;<br>      timeSchedule.periods[0] = timePeriod;<br>tw.system.addTimeSchedule(timeSchedule);  </pre><h3>How Due Dates Are Calculated in IBM Business Automation Workflow</h3><p>IBM Business Automation Workflow calculates due dates at runtime. The calculation is based on:</p><ul><li>The <strong>start date</strong> of the process instance or the runtime task</li><li>The <strong>“Due In”</strong> time value configured in <strong>Process Designer</strong></li><li>The <strong>work schedule properties</strong>, which include defined working hours and holidays</li></ul><h3>How “Due-In” Time Works differently for Processes and Activities</h3><p>The <strong>“Due-In”</strong> time is handled differently for <strong>processes</strong> and <strong>activities</strong>, and it directly impacts how due dates are calculated at runtime.</p><h4>Processes</h4><ul><li>The <strong>default due-in time</strong> for a process instance is <strong>8 hours</strong>.</li><li>You can customize this duration using <strong>days</strong>, <strong>hours</strong>, and <strong>minutes</strong>.</li><li><strong>Example</strong>: If you set a due-in time of <strong>2 days, 4 hours, and 30 minutes</strong>, the process is expected to complete within that time after it starts.</li></ul><h4>Activities</h4><ul><li>The <strong>default due-in time</strong> for an activity is <strong>1 hour</strong>.</li><li>You can configure the time using <strong>days</strong>, <strong>hours</strong>, or <strong>minutes</strong>.</li><li>If you set the due-in time in <strong>days</strong>, an additional field allows you to specify the <strong>exact time of day</strong> the task is due.</li><li><strong>Example</strong>: If you specify <strong>1 day</strong> and set the time to <strong>11:00 AM</strong>, the task will be due at <strong>11:00 AM</strong> the day after it starts.</li></ul><p>These elements are combined to determine an accurate due date that reflects actual business time rather than just elapsed time.</p><p>After that, you can use the newly created <strong>Time schedules</strong> and <strong>Holiday schedules</strong> in any process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UBcd7m54rXy4xBMPooXE5w.jpeg" /><figcaption>Setting custom schedules for entire process</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1gQ5XxwrKh0Q9kl0SSi0dQ.jpeg" /><figcaption>Setting custom schedules for steps</figcaption></figure><h3>PS: How to Remove Time and Holiday Schedules from IBM BAW</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/894/1*wIP2Ep4YMISeBrPGIN22rg.png" /></figure><pre>// variable1 (TWTimeSchedule List) will return the existing TimeSchedules.<br>// variable2 (TWHolidaySchedule List) will return the existing HolidaySchedules.<br>// Run this in debug mode and get the existing TimeSchedules &amp; HolidaySchedules lists.<br>tw.local.variable1 = tw.system.timeSchedules;<br>tw.local.variable2 = tw.system.holidaySchedules;<br><br>// paste TimeSchedule id here, which you want to be removed. ex -2098.1056<br>tw.system.removeTimeSchedule(&quot;2098.1056&quot;);<br>// paste HolidaySchedule id here, which you want to be removed. ex -2099.1057<br>tw.system.removeHolidaySchedule(&quot;2099.1057&quot;);<br></pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac1d96f8f214" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Displaying User-Defined Variables as Columns in the Process Portal Task List]]></title>
            <link>https://medium.com/@gihanshamikeliyanage/displaying-user-defined-variables-as-columns-in-the-process-portal-task-list-de2dbc488426?source=rss-f465db041132------2</link>
            <guid isPermaLink="false">https://medium.com/p/de2dbc488426</guid>
            <category><![CDATA[filenet]]></category>
            <category><![CDATA[baw]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[process-portal]]></category>
            <category><![CDATA[task-list]]></category>
            <dc:creator><![CDATA[P8 Hub]]></dc:creator>
            <pubDate>Tue, 24 Jun 2025 17:52:29 GMT</pubDate>
            <atom:updated>2025-06-24T17:52:29.466Z</atom:updated>
            <content:encoded><![CDATA[<p>I had a requirement to change the value displayed in the <strong>“Task received from”</strong> column in Process Portal. However, this column always shows the value <strong>“deadmin”</strong> (or whatever the admin username is).</p><p>Since <strong>“Task received from”</strong> is a system-defined variable, and modifying its value directly is not recommended. So I decided to implement an alternative solution. I created a separate variable to track the last owner and exposed that particular variable to the Process Portal instead.</p><h3>Approach:</h3><p><strong>Step 1:</strong><br>Expose the custom variable to the Process Portal by selecting “Visible in Process Portal”. If needed, we can rename the<strong> Alias</strong> of the exposed variable</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Wyd-D3WdPma5o9-kpLYytA.jpeg" /><figcaption>Expose variable to Process Portal</figcaption></figure><p><strong>Step 2:</strong><br> Create a new Saved Search and configure the columns as needed.<br> Rename the column headings as desired.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wbyOwXoogTtNKO06YIml8Q.jpeg" /><figcaption>Edit columns of saved search</figcaption></figure><p>This approach avoids modifying “Task received from” system variable.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HCE6RGGEVMeyp2Hef9SJig.jpeg" /><figcaption>Saved search</figcaption></figure><p>This way we can display <strong>user-defined variables</strong> (business data) as columns in the Process Portal Task List.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=de2dbc488426" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[WebSphere Best Practices After FileNet Installation]]></title>
            <link>https://medium.com/@gihanshamikeliyanage/websphere-best-practices-after-filenet-installation-8070a8aacf98?source=rss-f465db041132------2</link>
            <guid isPermaLink="false">https://medium.com/p/8070a8aacf98</guid>
            <category><![CDATA[filenet]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[wa]]></category>
            <category><![CDATA[websphere]]></category>
            <category><![CDATA[best-practices]]></category>
            <dc:creator><![CDATA[P8 Hub]]></dc:creator>
            <pubDate>Tue, 29 Apr 2025 02:34:55 GMT</pubDate>
            <atom:updated>2025-04-29T02:34:55.949Z</atom:updated>
            <content:encoded><![CDATA[<p>After installing FileNet on IBM WebSphere Application Server (WAS), following 10 best practices are crucial for ensuring system stability, performance, and security.</p><h4>❇️ 1. JVM &amp; Heap Tuning</h4><ul><li><strong>Initial/Max Heap Size</strong>: Set appropriate JVM heap sizes based on system memory. Common:<br> -Xms2048m -Xmx4096m (adjust as needed).</li><li><strong>GC Policy</strong>: Use -Xgcpolicy:gencon for balanced throughput and response time.</li><li><strong>Monitor GC</strong>: Enable verbose GC logging (-verbose:gc) and analyze regularly.</li></ul><p>🔧<strong><em> How to set Heap Size and GC policy:</em></strong></p><ol><li>Go to:<br> Servers &gt; Server Types &gt; WebSphere application servers &gt; server1</li><li>Click <strong>Java and Process Management &gt; Process Definition &gt; Java Virtual Machine</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FHvrJkmgY1pDYBVKUfENuA.jpeg" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I9HWyLMWncrCJ15xqQoBWw.jpeg" /></figure><p>3. Set:</p><ul><li><strong>Initial heap size (Xms)</strong>: 2048</li><li><strong>Maximum heap size (Xmx)</strong>: 4096</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TbvZDgXDobIoTnF0UtOoPw.png" /></figure><p>4. Add JVM arguments:</p><pre>-Xgcpolicy:gencon<br>-verbose:gc<br>-Xloggc:/opt/IBM/WebSphere/logs/gc.log</pre><p>5. Save and restart the server.</p><h4>❇️ 2. JDBC &amp; Connection Pool Tuning</h4><ul><li><strong>Set Minimum &amp; Maximum Pool Sizes</strong>: Avoid defaults. Tune based on load (e.g., Min: 5, Max: 50).</li><li><strong>Connection Timeout</strong>: Configure idle timeout and aged timeout to recycle stale connections.</li><li><strong>Test Connections</strong>: Enable “Test connection on reserve” to prevent bad connections.</li></ul><p>🔧 <strong><em>How to configure:</em></strong></p><ol><li>Go to:<br> Resources &gt; JDBC &gt; Data sources &gt; (your datasource)</li><li>Click <strong>Connection pool properties</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wmSBqfdAtHjzrLs0qlmA9Q.jpeg" /></figure><p>3. Set:</p><ul><li><strong>Minimum connections</strong>: 5</li><li><strong>Maximum connections</strong>: 50 (adjust based on load)</li><li><strong>Connection timeout</strong>: 180</li><li><strong>Aged timeout</strong>: 600</li></ul><p>4. Check <strong>“Test connection on reserve”</strong></p><h4>❇️ 3. Thread Pool Configuration</h4><ul><li>Tune the WebContainer thread pool based on concurrent user load.<br> Default: 50; Custom: 100–200 if load demands.</li><li>Monitor using <strong>Performance Monitoring Infrastructure (PMI)</strong>.</li></ul><p>🔧<strong><em> How to tune thread pools:</em></strong></p><ol><li>Go to:<br> Servers &gt; Server Types &gt; WebSphere application servers &gt; server1</li><li>Click <strong>Thread Pools &gt; WebContainer</strong></li><li>Adjust:</li></ol><ul><li><strong>Minimum size</strong>: 50</li><li><strong>Maximum size</strong>: 200 (based on load testing)</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EzRbe2cNCi7NKq7btZe_Mw.png" /></figure><h4>❇️ 4. Security Hardening</h4><ul><li><strong>Global Security</strong>: Enable and configure properly.</li><li><strong>Application Security</strong>: Use JAAS roles for FileNet components.</li><li><strong>SSL</strong>: Use secure communication (HTTPS, LDAPS). Update default certificates.</li><li><strong>Audit</strong>: Enable WebSphere and FileNet auditing features.</li></ul><p>🔧 <strong><em>How to enable Global Security:</em></strong></p><ol><li>Go to:<br> Security &gt; Global Security</li><li>Enable <strong>Administrative Security</strong></li><li>Set <strong>Federated Repositories</strong> or <strong>LDAP</strong> for user registry</li><li>Configure <strong>SSL</strong>:</li></ol><ul><li>Security &gt; SSL certificate and key management</li><li>Update certificates</li><li>Set secure protocols (disable TLS 1.0/1.1)</li></ul><h4>❇️ 5. Session &amp; Cache Management</h4><ul><li>Use <strong>Distributed or Persistent HTTP Sessions</strong> if clustered.</li><li>Configure <strong>Dynacache</strong> for performance.</li><li>Tune <strong>Cache sizes</strong> and expiration settings.</li></ul><p><strong><em>🔧 How to set session persistence:</em></strong></p><ol><li>Go to:<br> Applications &gt; Application Types &gt; WebSphere enterprise applications</li><li>Click on the FileNet application (e.g., wsi, navigator)</li><li>Click <strong>Session management</strong></li><li>Choose:</li></ol><ul><li><strong>Persistent to database</strong> (for HA/Clustered)</li><li>Enable <strong>Cookies</strong> only (for session tracking)</li></ul><h4>❇️ 6. FileNet-Specific Settings</h4><ul><li><strong>Thread Dump Configuration</strong>: Enable thread dumps on critical errors.</li><li><strong>PE &amp; CE Connection Pools</strong>: Monitor and tune based on FileNet traffic.</li><li><strong>Health Monitoring</strong>: Set up FileNet heartbeat URL checks for cluster/load balancers.</li></ul><p><strong><em>🔧 Content Engine/Process Engine tuning:</em></strong></p><ol><li><strong>Use Process Administrator and FEM console</strong> to:</li></ol><p>➥ Configure Dispatcher thread count</p><p>➥ Monitor CE/PE Health</p><p>2. Monitor <strong>Error logs</strong> at:</p><p>➥ /opt/IBM/FileNet/logs or SystemOut.log</p><h4>❇️ 7. Logging &amp; Monitoring</h4><ul><li>Configure <strong>log rotation</strong> to avoid disk issues.</li><li>Use <strong>HPEL (High Performance Extensible Logging)</strong> for efficient diagnostics.</li><li>Integrate with monitoring tools (e.g., IBM Tivoli, Splunk, or AppDynamics).</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/626/1*LXazPqkW5cOzBVOybF43Wg.jpeg" /></figure><p>🔧 <strong><em>How to enable HPEL and rotate logs:</em></strong></p><ol><li>Go to:<br> Troubleshooting &gt; Logs and trace &gt; server1 &gt; Diagnostic Trace</li><li>Enable <strong>HPEL</strong> or configure classic log rotation</li></ol><ul><li>Log size: 10MB</li><li>Max files: 50</li></ul><h4>❇️ 8. Deployment &amp; Classloader Isolation</h4><ul><li>Use <strong>Parent Last</strong> class loader for FileNet applications to avoid conflicts.</li><li>Use <strong>Application scoped resources</strong> where possible.</li></ul><p><strong><em>🔧 How to set to “Parent Last”:</em></strong></p><ol><li>Go to:<br> Applications &gt; Enterprise Applications &gt; (your FileNet app)</li><li>Click <strong>Class loader &gt; Class loader order</strong></li><li>Select <strong>Parent Last</strong></li></ol><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_AtjVnUg7liDuHeHgI13Jw.jpeg" /></figure><p>4. Save and restart app.</p><h4>❇️ 9. Backup &amp; Disaster Recovery</h4><ul><li>Regularly back up:</li></ul><p>➔ WAS profiles</p><p>➔ FileNet GCD, object stores</p><p>➔ CE/PE configuration files</p><ul><li>Test restore procedures periodically.</li></ul><p>🔧 <strong><em>What to back up:</em></strong></p><ol><li><strong>WAS Profiles</strong>:<br> /opt/IBM/WebSphere/AppServer/profiles/AppSrv01</li></ol><p>2. <strong>GCD, Object Store DBs</strong>: via database backup</p><p>3. <strong>CE/PE configuration</strong>:</p><p>➔ FileNetConfig.properties</p><p>➔ XML exports of workflows</p><h4>❇️ 10. High Availability (if clustered only)</h4><ul><li><strong>Configure Node Synchronization</strong> properly.</li><li><strong>Enable Automatic Restart of Servers</strong> (Node Agents and Application Servers).</li><li><strong>Tune DRS (Dynamic Replication Services)</strong> if used.</li></ul><p>🔧 <strong>How</strong>:<br> Servers &gt; Core Groups &gt; Policies.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VuhiyqkI9qF_JIb6Z1H6UA.png" /></figure><p>Properly tuning and securing WebSphere Application Server after installing FileNet is very important to keep FileNet system running smoothly and securely.<br>By adjusting settings like JVM memory, database connections, thread pools, security options, and FileNet-specific settings, you can build a strong and stable FileNet environment for your production system.</p><p>Apart from that consistent monitoring, documentation, and backup strategies will further protect the system against downtime and make scaling and troubleshooting easier in the future.</p><p>PS: ⚠️ Always test changes in a staging environment before applying them to production environment…!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8070a8aacf98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Steps to Deploy a Simple Web Application in WebSphere]]></title>
            <link>https://medium.com/@gihanshamikeliyanage/steps-to-deploy-a-simple-web-application-in-websphere-0af1affc5433?source=rss-f465db041132------2</link>
            <guid isPermaLink="false">https://medium.com/p/0af1affc5433</guid>
            <category><![CDATA[web-applications]]></category>
            <category><![CDATA[java]]></category>
            <category><![CDATA[filenet]]></category>
            <category><![CDATA[websphere]]></category>
            <category><![CDATA[deployment]]></category>
            <dc:creator><![CDATA[P8 Hub]]></dc:creator>
            <pubDate>Tue, 18 Feb 2025 18:56:53 GMT</pubDate>
            <atom:updated>2025-02-18T18:56:53.541Z</atom:updated>
            <content:encoded><![CDATA[<p>To deploy an application in IBM WebSphere, follow these steps:</p><h4>1. Prepare Your Application</h4><ul><li>Ensure your application is packaged correctly. For a Java web application, it should be packaged as a .war (Web Archive) file.</li><li>If it’s an Enterprise Application, it should be packaged as a .ear (Enterprise Archive) file.</li></ul><h4>2. Log into the WebSphere Admin Console</h4><ul><li>Open your browser and go to the WebSphere Admin Console URL, typically http://&lt;your_server&gt;:&lt;port&gt;/ibm/console.</li><li>Log in with your WebSphere administrator credentials.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ALWVm2jGkGqRGriVZ95cpA.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yzBR525294Uu2rjQWkUV6w.jpeg" /><figcaption>Click on <strong>Applications</strong> &gt; <strong>New Application</strong> in the left-hand menu</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wqogHu2RPmUNvhvxqY_ryQ.png" /><figcaption>Click <strong>Browse</strong> to locate the .war or .ear file on your local system.</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kuQTNXBJ-OOWavi_SOBeMA.png" /><figcaption>Select <strong>Fast Path</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_GEd_-4VpD31Y4zTTTCRsw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OeVEjTnZGnmniydK0Z-Hjg.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*B6jqFWW0EyrzheIh2c9t-g.png" /></figure><h4>3. Configure the Application</h4><ul><li>Specify the context root for the application (e.g., /p8hub-webapp), which determines the URL path to access the application.</li><li>Configure other deployment settings such as <strong>security settings</strong>, <strong>data sources</strong>, and <strong>JMS settings</strong>, if required by your application.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g8MKDCWYDv_vQqPZgfeL2Q.jpeg" /></figure><h4>4. Review the Deployment Configuration</h4><ul><li>Review all your settings, including the application file, server settings, and other configurations.</li><li>Click <strong>Finish</strong> to deploy the application.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UaXG01foSj4SqDRTdbYJVw.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fBpgHjr33tfdT2dRGmNl0Q.jpeg" /></figure><h4>5. Start the Application</h4><ul><li>If you chose not to start the application automatically, navigate back to <strong>Applications</strong> in the Admin Console.</li><li>Locate your application and click the <strong>Start</strong> button to launch it.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*JIAcMkMwp1-VyDcC1JbEXQ.jpeg" /></figure><h4>6. Verify Deployment</h4><ul><li>Once the application is started, access it via the configured context root URL (e.g., http://&lt;your_server&gt;:&lt;port&gt;/p8hub-webapp).</li><li>You can monitor the logs and WebSphere Admin Console for any errors or issues during the deployment.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rTuAF3gfRMapStFeMfIQkg.png" /></figure><p>These steps only cover a very basic webapp deployment. Depending on your web application’s complexity, you may need to adjust additional configurations like data sources, JMS, or security settings.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0af1affc5433" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[IBM Case Manager vs IBM Business Automation Workflow (BAW)]]></title>
            <link>https://medium.com/@gihanshamikeliyanage/ibm-case-manager-vs-ibm-business-automation-workflow-baw-70b4a5ca698e?source=rss-f465db041132------2</link>
            <guid isPermaLink="false">https://medium.com/p/70b4a5ca698e</guid>
            <category><![CDATA[baw]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[filenet]]></category>
            <category><![CDATA[comparison]]></category>
            <category><![CDATA[case-manager]]></category>
            <dc:creator><![CDATA[P8 Hub]]></dc:creator>
            <pubDate>Sun, 16 Feb 2025 23:01:42 GMT</pubDate>
            <atom:updated>2025-02-16T23:01:42.499Z</atom:updated>
            <content:encoded><![CDATA[<p>IBM Case Manager and IBM Business Automation Workflow (BAW) are both products in IBM’s automation suite, but they serve different purposes and cater to different types of business processes. Here’s a breakdown of their differences and key features:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*H01CtHu7iw0nNJjyLmWn_w.jpeg" /></figure><h3>IBM Case Manager (ICM)</h3><p>IBM Case Manager is a solution for managing <strong>case-based processes</strong>. It focuses on knowledge work and unstructured processes that often require human judgment.</p><h4>Key Features:</h4><ol><li><strong>Case-Centric</strong>: Designed to handle cases like incident management, claims processing, or customer complaints where data, tasks, and workflows revolve around the case.</li><li><strong>Content Integration</strong>: Integrates deeply with IBM FileNet Content Manager for storing and managing documents related to cases.</li><li><strong>Dynamic and Adaptive</strong>: Allows knowledge workers to dynamically add tasks or collaborate to resolve cases as they evolve.</li><li><strong>Collaboration Tools</strong>: Includes built-in collaboration tools, such as comments and activity streams, to enhance teamwork.</li><li><strong>Ad Hoc Workflows</strong>: Supports ad hoc workflows that aren’t strictly predefined, enabling flexibility for knowledge workers.</li><li><strong>Case Analytics</strong>: Provides insights into case performance with dashboards and analytics.</li></ol><h4>Best For:</h4><ul><li>Handling unstructured, content-heavy, and knowledge-driven processes.</li><li>Use cases like insurance claims, legal case management, HR grievance handling, or healthcare case tracking.</li></ul><h3>IBM Business Automation Workflow (BAW)</h3><p>IBM BAW is a platform that combines <strong>business process management (BPM)</strong> and <strong>case management</strong> into one comprehensive solution. It focuses on <strong>structured workflows</strong>, automation, and orchestration of tasks.</p><h4>Key Features:</h4><ol><li><strong>Workflow Automation</strong>: Automates end-to-end structured processes with defined workflows and rules.</li><li><strong>Integration of BPM and Case Management</strong>: Combines structured process workflows with case management capabilities for hybrid scenarios.</li><li><strong>Business Rules</strong>: Supports complex decision-making with robust business rule engines.</li><li><strong>Workflow Orchestration</strong>: Manages tasks across multiple systems and users for seamless execution.</li><li><strong>Low-Code Development</strong>: Provides a low-code environment for developing workflows and processes.</li><li><strong>AI and Insights</strong>: Leverages AI capabilities (e.g., IBM Watson) for predictive insights and workflow optimizations.</li><li><strong>Cloud and Hybrid Support</strong>: Available on IBM Cloud and supports hybrid deployment.</li></ol><h4>Best For:</h4><ul><li>Managing structured, repeatable processes like loan approvals, order processing, or employee onboarding.</li><li>Use cases where orchestration between systems and tasks is critical.</li></ul><h3>Comparison Table</h3><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/8a616c9a8d8fb5fb54e3a1fa43beed65/href">https://medium.com/media/8a616c9a8d8fb5fb54e3a1fa43beed65/href</a></iframe><h3>Choosing Between Them</h3><ul><li>Use <strong>IBM Case Manager</strong> if your processes are primarily <strong>case-driven</strong>, unstructured, and require high collaboration with knowledge workers.</li><li>Use <strong>IBM Business Automation Workflow</strong> if you need to automate <strong>structured workflows</strong>, integrate systems, and combine BPM with case management capabilities for end-to-end process optimization.</li></ul><p>If you’re working in scenarios that involve a mix of structured and unstructured tasks, IBM BAW (which includes case management features) may offer more comprehensive capabilities.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=70b4a5ca698e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a Case Using the FileNet P8 Java API]]></title>
            <link>https://medium.com/@gihanshamikeliyanage/creating-a-case-using-the-filenet-p8-java-api-44323c4c84c5?source=rss-f465db041132------2</link>
            <guid isPermaLink="false">https://medium.com/p/44323c4c84c5</guid>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[java-apis]]></category>
            <category><![CDATA[case-manager]]></category>
            <category><![CDATA[create-case]]></category>
            <category><![CDATA[filenet]]></category>
            <dc:creator><![CDATA[P8 Hub]]></dc:creator>
            <pubDate>Sat, 15 Feb 2025 09:55:26 GMT</pubDate>
            <atom:updated>2025-02-15T09:55:26.707Z</atom:updated>
            <content:encoded><![CDATA[<p>In this code, I am passing case property values, case type, and solution name as method parameters. The case properties are being passed as a JSON object.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/804/1*D3aZWUitXa7HhsGLwCzzSQ.png" /></figure><pre>package temp.temp;<br><br>import java.util.Locale;<br>import java.util.Map;<br>import java.util.Set;<br>import java.util.Map.Entry;<br><br>import javax.security.auth.Subject;<br><br>import org.apache.log4j.Logger;<br><br>import com.google.gson.JsonElement;<br>import com.google.gson.JsonObject;<br><br>import com.filenet.api.constants.RefreshMode;<br>import com.filenet.api.core.Connection;<br>import com.filenet.api.core.Domain;<br>import com.filenet.api.core.Factory;<br>import com.filenet.api.core.ObjectStore;<br>import com.filenet.api.util.UserContext;<br><br>import com.ibm.casemgmt.api.Case;<br>import com.ibm.casemgmt.api.CaseType;<br>import com.ibm.casemgmt.api.DeployedSolution;<br>import com.ibm.casemgmt.api.constants.ModificationIntent;<br>import com.ibm.casemgmt.api.context.CaseMgmtContext;<br>import com.ibm.casemgmt.api.context.P8ConnectionCache;<br>import com.ibm.casemgmt.api.context.SimpleP8ConnectionCache;<br>import com.ibm.casemgmt.api.context.SimpleVWSessionCache;<br>import com.ibm.casemgmt.api.objectref.ObjectStoreReference;<br>import com.ibm.casemgmt.api.properties.CaseMgmtProperties;<br><br>/*<br> * <br> * @author P8Hub<br> *<br> */<br>public class CMCaseCreator {<br><br>    public static Logger log = Logger.getLogger(&quot;com.p8Hub.CMCaseCreator&quot;);<br>    private UserContext uc;<br>    private boolean userSubjectPushed;<br>    private Connection conn;<br>    private CaseMgmtContext origCmctx;<br><br><br>    public Connection getCMConnection() {<br><br>        String ceURI = &quot;CONNECTION_URL&quot;;           //CONNECTION_URL = &quot;http://100.10.10.213:9080/wsi/FNCEWS40MTOM/&quot;;<br>        String userId = &quot;CONNECTION_USER&quot;;         //CONNECTION_USER = &quot;P8Admin&quot;;<br>        String password = &quot;CONNECTION_PASSWORD&quot;;   //CONNECTION_PASSWORD = &quot;filenet&quot;;<br>        String stanza = &quot;JAAS_STANZA&quot;;             //JAAS_STANZA = &quot;FileNetP8WSI&quot;;<br><br>        P8ConnectionCache connCache = new SimpleP8ConnectionCache();<br>        conn = connCache.getP8Connection(ceURI);<br>        Subject subject = UserContext.createSubject(conn, userId, password, stanza);<br>        uc = UserContext.get();<br>        uc.pushSubject(subject);<br>        userSubjectPushed = true;<br><br>        uc.setLocale(Locale.ENGLISH);<br>        origCmctx = CaseMgmtContext.set(new CaseMgmtContext(new SimpleVWSessionCache(), connCache));<br><br>        return conn;<br>    }<br><br>    public void releaseCMConnection() {<br><br>        log.info(&quot;origCmctx is &quot; + origCmctx + &quot;, userSubjectPushed is &quot; + userSubjectPushed + &quot;, uc is &quot; + uc);<br>        if (userSubjectPushed) {<br>            CaseMgmtContext.set(origCmctx);<br>            Locale origLocale = uc.getLocale();<br>            uc.setLocale(origLocale);<br>            uc.popSubject();<br>            userSubjectPushed = false;<br>            conn = null;<br>            origCmctx = null;<br>            System.out.println(&quot;Connection Released&quot;);<br>            log.info(&quot;Connection Released&quot;);<br>        }<br>    }<br><br><br>    public String createCase(JsonObject caseParametersBean, String caseType, String solutionName) {<br><br>        String newCaseIdentifier = null;<br>        Connection conn = getCMConnection();<br><br>        String caseTypename = caseType;<br>        String targetOsname = &quot;CONNECTION_OBJECT_STORE&quot;;   // CONNECTION_OBJECT_STORE = &quot;CMTOS&quot;<br>        String domainName = &quot;CONNECTION_DOMAIN&quot;;           // CONNECTION_DOMAIN = &quot;fnp8domain&quot;;<br><br>        try {<br>            Domain domain = Factory.Domain.fetchInstance(conn, domainName, null);<br>            ObjectStore os = Factory.ObjectStore.fetchInstance(domain, targetOsname, null);<br>            ObjectStoreReference osRef = new ObjectStoreReference(os);<br>            DeployedSolution someSolution = DeployedSolution.getFetchlessInstance(osRef, solutionName);<br>            log.info(&quot;Solution Name &quot; + someSolution.getSolutionName());<br>            CaseType caseTypeInstance = CaseType.fetchInstance(osRef, caseTypename); {<br>                Case pendingCase = Case.createPendingInstanceFetchDefaults(caseTypeInstance);<br>                CaseMgmtProperties properties = pendingCase.getProperties();<br>                log.info(&quot;properties is &quot; + properties);<br>                Set &lt; Entry &lt; String, JsonElement &gt;&gt; jsSet = caseParametersBean.entrySet();<br><br>                for (Map.Entry &lt; String, JsonElement &gt; entry: jsSet) {<br>                    Object keyvalue = null;<br>                    String keyStr = null;<br>                    if (entry.getKey() != null) {<br>                        keyStr = entry.getKey().toString();<br>                    }<br>                    keyvalue = caseParametersBean.get(keyStr).getAsString();<br><br>                    log.info(&quot;keyStr is &quot; + keyStr.getClass() + &quot; value is &quot; + keyvalue);<br>                    properties.putObjectValue(keyStr, keyvalue);<br><br>                }<br>                log.info(&quot;Successfull Updated&quot;);<br><br>                pendingCase.save(RefreshMode.REFRESH, null, ModificationIntent.MODIFY);<br>                newCaseIdentifier = pendingCase.getIdentifier();<br><br>                log.info(&quot;newCaseIdentifier is &quot; + newCaseIdentifier);<br>            }<br>        } catch (Exception e) {<br>            e.printStackTrace();<br>            log.error(e.getMessage() + &quot; &quot; + e.fillInStackTrace());<br>        } finally {<br>            releaseCMConnection();<br>        }<br>        return newCaseIdentifier;<br>    }<br>}</pre><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=44323c4c84c5" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Enabling FileNet Case Management Features in Newly Installed IBM BAW Environment]]></title>
            <link>https://medium.com/@gihanshamikeliyanage/enabling-filenet-case-management-features-in-newly-installed-ibm-baw-environment-5125953359c7?source=rss-f465db041132------2</link>
            <guid isPermaLink="false">https://medium.com/p/5125953359c7</guid>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[enable-case-features]]></category>
            <category><![CDATA[case-manager]]></category>
            <category><![CDATA[filenet]]></category>
            <category><![CDATA[baw]]></category>
            <dc:creator><![CDATA[P8 Hub]]></dc:creator>
            <pubDate>Fri, 31 Jan 2025 03:28:51 GMT</pubDate>
            <atom:updated>2025-01-31T03:28:51.536Z</atom:updated>
            <content:encoded><![CDATA[<p>You can follow these steps to enable and configure case management features in BAW after upgrading to IBM Business Automation Workflow.</p><p>Before enabling case features in BAW, make sure you have a Business Automation Workflow license. If you’re upgrading from IBM Business Process Manager (BPM) or IBM Case Manager, you’ll also need to update your license to Business Automation Workflow.</p><p>First, we need to locate <strong>configmgr.exe</strong> and open a profile.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*wZ9SY-_I5NjwVE8ItM6KQg.png" /><figcaption>Launch IBM Business Automation Workflow Case Configuration Tool</figcaption></figure><h4><strong>Step to follow:</strong></h4><ol><li>Locate the <strong>configmgr.exe</strong> file to launch the IBM Business Automation Workflow Case Configuration Tool. Typically, the directory <strong>/CaseManagement/configure</strong> contains the IBM Case Manager Configuration Tool.</li></ol><pre>C:\IBM\Workflow\v20.0\CaseManagement\configure</pre><p>Note: The exact path may vary depending on your environment.</p><p>2. Click on <strong>Open an existing profile</strong> and here, I select the <strong>ICM_dev.cfgp</strong> default profile located in the following location:</p><pre>C:\IBM\Workflow\v20.0\profiles\DmgrProfile\CaseManagement\WorkflowCenter\profiles\ICM_dev</pre><p>After opening the profile, we need to review the list of tasks and run only the relevant tasks one by one.</p><h4>R<em>equired Tasks:</em></h4><p><strong>Task 1 — </strong>Register the Administrative Console for Content Engine (ACCE) Plug-in.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*e5ugR6xeRcSKfQdDINzDCw.png" /><figcaption>Task 1 — Register the ACCE Plug-in</figcaption></figure><p>After running this task, you will be able to access <strong>ACCE</strong> through the navigator.</p><p>Before running the next task, which is <strong>Configure the Case Management Object Stores</strong>, you need to create the <strong>Target</strong> and <strong>Design Object Stores</strong> in the embedded <strong>Content Platform Engine</strong>. We can use <strong>ACCE</strong> to accomplish this, as we already enabled ACCE in step 1.</p><p>If you’re not familiar with how to create tos &amp; dos Object Stores using ACCE, this guide will help you.</p><p><a href="https://medium.com/@gihanshamikeliyanage/creating-tos-dos-object-stores-in-embedded-cpe-of-baw-using-acce-b893289e8ee7">Creating tos &amp; dos Object Stores in Embedded CPE of BAW using ACCE</a></p><p>Alternatively, you can use other methods, such as creating Object Stores using <strong>FEM</strong>.</p><p><em>Note:<br>Case systems require multiple object stores depending on the environment.</em></p><ul><li><strong><em>Legacy IBM Case Manager environments</em></strong><em> require 2 object stores:</em></li></ul><ol><li><em>A design or staging object store</em></li><li><em>A target object store</em></li></ol><ul><li><strong><em>IBM BAW case functions</em></strong><em> require 3 object stores:</em></li></ul><ol><li><em>A content object store (which must be initially empty)</em></li><li><em>A design or staging object store (dev environments have design object store and prod environments have a staging object store.)</em></li><li><em>A target object store</em></li></ol><p><em>If using the embedded Content Platform Engine, the content object store (docs) is automatically created and initialized during the first-time startup of the application clusters.</em></p><p>As we are using the embedded Content Platform Engine here, we only need to create two object stores manually:</p><ul><li><strong>tos</strong> — Target Object Store</li><li><strong>dos</strong> — Design Object Store</li></ul><p><strong>Task 2- </strong>Configure the Case Management Object Stores.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dRNsCiGVWBWqXpKBxYM_aQ.png" /><figcaption>Task 2 — Configure the case management object stores</figcaption></figure><p>If this task fails with com.filenet.api.exception.EngineRuntimeException: FNRCE0075E: E_TRANSACTION_FAILURE: A transaction failure has occurred due to an invalid state or timeout, refer to this guide to resolve the issue.</p><p><a href="https://medium.com/@gihanshamikeliyanage/how-to-fix-ibm-baw-case-configuration-tool-task-of-configuring-the-case-management-object-stores-95b9264d874e">How to fix IBM BAW Case Configuration Tool task of Configuring the Case Management Object Stores…</a></p><p><strong>Task 3</strong> — Define the Default Project Area</p><p>Before running this task, you need to configure the workflow system in the <strong>tos (Target Object Store)</strong>, as it requires a Target Object Store connection point.</p><p>If you’re not familiar with how to add a Workflow System to an Object Store using ACCE, this guide will help you.</p><p><a href="https://medium.com/@gihanshamikeliyanage/adding-a-workflow-system-to-an-object-store-3fcec04eee25">Adding a Workflow System to an Object Store</a></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*D9NuQWvR4XmVZOYqrix37w.png" /><figcaption>Task 3 — Define the Default Project Area</figcaption></figure><p><strong>Task 4 —</strong> Configure Case Integration with IBM Business Automation Workflow</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*WyDcMlor39mDprfu34ioRg.png" /><figcaption>Task 4 — Configure Case Integration with IBM Business Automation Workflow</figcaption></figure><p><strong>Task 5</strong> — Deploy the Content Platform Engine Workflow Service</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BH2pawA0yTFhI05Mz6dG7Q.png" /><figcaption>Task 5 — Deploy the Content Platform Engine Workflow Service</figcaption></figure><p><strong>Task 6</strong> — Deploy the Content Platform Engine Gateway Service</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1rXv-ZeldQDFE66cG0truA.png" /><figcaption>Task 6 — Deploy the Content Platform Engine Gateway Service</figcaption></figure><p><strong>Task 7</strong> — Register the IBM Business Automation Workflow Plug-in</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*rjno6--foi5h4yXlJM2YKg.png" /><figcaption>Task 7 — Register the IBM Business Automation Workflow Plug-in</figcaption></figure><p><strong>Task 8 </strong>— Register the Case Management Services Plug-in</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RmuBstxxTxdIKXqfVRpyEA.png" /><figcaption>Task 8 — Register the Case Management Services Plug-in</figcaption></figure><p><strong>Task 9 </strong>— Register the Case Widgets Package</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3IYsFh029XyHqcYkLjYDCQ.png" /><figcaption>Task 9 — Register the Case Widgets Package</figcaption></figure><p><strong>Task 10</strong> — Register the IBM Business Automation Workflow Case Administration Client Plug-in</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sQ7oIBsV27IF9E1atZ4mWg.png" /><figcaption>Task 10 — Register the IBM Business Automation Workflow Case Administration Client Plug-in</figcaption></figure><p><strong>Task 11</strong> — Register Project Area</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oAjbFDj2zyQfgmPYsdgR_A.png" /><figcaption>Task 11 — Register Project Area</figcaption></figure><p><strong>Task 12</strong> — Configure Business Rules</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IS6bx5P0UJDyzBlPsSe5Ew.png" /><figcaption>Task 12 — Configure Business Rules</figcaption></figure><p><strong>Task 13</strong> — Register the Case Monitor Widgets Package</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_IA9xHsFWJd3vejo8p3vWA.png" /><figcaption>Task 13 — Register the Case Monitor Widgets Package</figcaption></figure><p>Now, you have completed running all the necessary tasks.</p><p><strong>Remember:</strong> After running the tasks, restart your entire environment, including <strong>Business Automation Workflow</strong>, <strong>Content Platform Engine</strong>, and <strong>IBM Content Navigator</strong>.</p><p>After restarting, you can start using <strong>Case Management</strong> features in this <strong>BAW environment</strong>. To verify the setup, you can create a simple <strong>case solution </strong>and<strong> deploy </strong>it using <strong>Case Builder</strong>.</p><pre>https://&lt;server&gt;:&lt;port&gt;/CaseBuilder</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LVVKUZEFTR7iEvYumDR5EQ.png" /><figcaption>Case Builder</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5125953359c7" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Adding a Workflow System to an Object Store]]></title>
            <link>https://medium.com/@gihanshamikeliyanage/adding-a-workflow-system-to-an-object-store-3fcec04eee25?source=rss-f465db041132------2</link>
            <guid isPermaLink="false">https://medium.com/p/3fcec04eee25</guid>
            <category><![CDATA[workflow-system]]></category>
            <category><![CDATA[cpe]]></category>
            <category><![CDATA[object-store]]></category>
            <category><![CDATA[filenet]]></category>
            <category><![CDATA[ibm]]></category>
            <dc:creator><![CDATA[P8 Hub]]></dc:creator>
            <pubDate>Thu, 30 Jan 2025 04:07:03 GMT</pubDate>
            <atom:updated>2025-01-30T04:07:03.743Z</atom:updated>
            <content:encoded><![CDATA[<p>Before initializing the <strong>New Workflow System wizard</strong>, you need to <strong>install Process Engine Extensions</strong> to the object store.</p><p>Otherwise, you will encounter the following error:<br>🚨 <em>“A workflow system cannot be created because the Process Engine extensions have not been installed.”</em></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LaLUlfP2P_zpogRYqlFe4g.png" /><figcaption>Install Add-on Features</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*M3BtBtoQ2FCmPNkD3Xr_Sg.png" /><figcaption>Install Add-ons</figcaption></figure><p>Now, we can start the <strong>New Workflow System wizard</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*OZxn08oyjj2RUgAF_BsDCw.png" /><figcaption>Workflow system wizard</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yKJpiXBuhlODL9d7OsRP2A.png" /><figcaption>Configuring table spaces and security groups</figcaption></figure><p>If you want to add a <strong>workflow system</strong> to an <strong>object store</strong> that does not already have one, the workflow system can use the <strong>existing table spaces</strong> of the object store.</p><p>Alternatively, you can create a <strong>new table spaces</strong> for the workflow system, according to the <strong>IBM documentation.</strong></p><p>Any <strong>table space</strong> used by the <strong>workflow system</strong> must have an <strong>all-uppercase name</strong>. If you plan to use the <strong>Content Platform Engine object store table space</strong> for the workflow system, ensure that the table space name is in <strong>uppercase</strong>.</p><p>Here, I will use the existing table space of the <strong>tos</strong> object store in the <strong>CPEDB</strong> database. To find the table space name, I am using the <strong>LIST TABLESPACES</strong> command.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PeQ6JeQaQo7LR4_wkd8ALA.jpeg" /><figcaption>db2 command line</figcaption></figure><p><strong>tos</strong> table space name : <strong>TOSSA_DATA_TS</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zBZiqgdC5AdaN8MDFsH1-g.png" /><figcaption>Define Connection Point name</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AmT5LHT6A3kzq5wr0smuBA.png" /><figcaption>Define Isolated Region</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mrrPlr7rShklx31l3WbC3A.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*3SbGjbjpJ8-OFyr8-_NTKg.png" /><figcaption>Summary</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MqdWldPocUevx7NnGyBvHg.png" /></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3fcec04eee25" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating tos & dos Object Stores in Embedded CPE of BAW using ACCE]]></title>
            <link>https://medium.com/@gihanshamikeliyanage/creating-tos-dos-object-stores-in-embedded-cpe-of-baw-using-acce-b893289e8ee7?source=rss-f465db041132------2</link>
            <guid isPermaLink="false">https://medium.com/p/b893289e8ee7</guid>
            <category><![CDATA[baw]]></category>
            <category><![CDATA[filenet]]></category>
            <category><![CDATA[ibm]]></category>
            <category><![CDATA[object-store]]></category>
            <category><![CDATA[acces]]></category>
            <dc:creator><![CDATA[P8 Hub]]></dc:creator>
            <pubDate>Wed, 29 Jan 2025 03:20:53 GMT</pubDate>
            <atom:updated>2025-01-29T03:20:53.735Z</atom:updated>
            <content:encoded><![CDATA[<p>To use <strong>ACCE </strong>for the embedded Content Platform Engine in a BAW environment, you need to enable the plug-in for the Administrative Console for Content Engine (ACCE) using the Case Configuration Tool. This allows you to access <strong>ACCE </strong>directly through <strong>IBM Content Navigator</strong>.</p><pre>https://&lt;server&gt;:&lt;port&gt;/navigator/?desktop=acce</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FnEVif1ruoX68TwlDmKD6A.png" /></figure><p>First, we will create the <strong>dos (Design Object Store)</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TcyLXD-CJZZ76licfscgYQ.png" /><figcaption>New object store wizard</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Kt8Jf1zQZ46PsjoDUOeYvA.png" /></figure><p>In the next step, you will be prompted to create or select an existing database connection for the object store. Select <strong>New</strong> to create a new database connection, and a new tab will open. After providing a name (<strong>dos</strong>) for the new connection, it will ask for the <strong>JNDI data sources</strong> (XA and Non-XA) for the database connection.</p><p>As we are planning to use this connection for Design Object Store (dos), I am using the existing data source <strong>jdbc/FNDOSDS</strong>, which was automatically created by the BAW setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Nin0paqD2hZ0u90wifQjfg.jpeg" /><figcaption>Default data sources in the application server for <strong>dos</strong> and <strong>tos</strong></figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MoRwUnj5JGd-NgxEmw-lWA.png" /></figure><p>Finish the wizard to add the connection.</p><p>After that, in the <strong>New Object Store wizard</strong>, select the newly created <strong>dos</strong> database connection. In the <strong>Schema Name</strong> field, provide a unique schema name, as both <strong>jdbc/FNDOSDS</strong> and <strong>jdbc/FNTOSDS</strong> data sources use the same database, <strong>CPEDB</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/555/1*KUsm8snHb-9JLz65_crqAg.png" /><figcaption>jdbc/FNDOSDS properties</figcaption></figure><p>Sharing a database with multiple object stores is supported in all releases of Content Engine. However, if you decide to share the database, you must use a <strong>unique schema name</strong> for each object store. This ensures that objects associated with one object store will not collide with objects from other object stores.</p><p>Therefore, I use the schema name<strong>dos</strong> for the Design Object Store.</p><p>In the next step select the storage area type.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iThOQr9mzkfBiF7layqpng.png" /><figcaption>Storage area types</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bNBpHdT2Zpl9WJOU6_rG7A.png" /><figcaption>Grant Administrative Access</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*x-sbZHBeioDjWLpIru3Rvw.png" /><figcaption>Grant Basic Access</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nNBwm2OESzhGcuIztRmhkg.png" /><figcaption>Add-ons</figcaption></figure><p>Complete the wizard by clicking <strong>Finish</strong>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/688/1*FHxWyqmAsYoF3pDdfO1HSA.png" /><figcaption>Creating Object Store</figcaption></figure><p>Follow the same steps to create a new database connection named <strong>tos</strong> for the Target Object Store. Then, create a new object store using this database connection, and in the <strong>Schema Name</strong> field of the <strong>New Object Store wizard</strong>, enter <strong>tos</strong> as schema name.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b893289e8ee7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>