You have now installed your K2 blackpearl environment and have validated some of the areas which frequently experiences issues. But how do you ensure that your environment is working as expected?
Below are the recommended steps one should follow to validate that your environment is working as expected:
On the K2 Server
- Stop the K2 blackpearl Service
On the SQL Server
- Backup K2 databases (if desired)
On the K2 Server
- Start the K2 blackpearl Service in console mode
- Be sure to do a run as and use credentials of the K2 blackpearl Service (Service Account) shortcut
- Watch the console window, are there any error messages?
- Open K2 Workspace
- Does it open?
- If Workspace was installed on another server, view it directly from the server to verify the installation without the use of Kerberos
On the Developer Machine
This is recommended to be physically different computer than K2 Server if you need to validate Kerberos.
- Open K2 Workspace
- Are you prompted for credentials? Then the site is probably not trusted in IE
- Are proper user credentials displayed? If not, Kerberos is probably not setup correctly
- Test Visual Studio
- Open Visual Studio and create a new Project
-
- Do the K2 Project templates exist?
- Create a new Process
- View the Visual Studio Toolbox
-
- View the K2 Object Browser
-
- Are you able to connect to an Environment?
- Build out a simple process that contains at least one client event.
-
- Below are some things you may consider when building out the test process:
- Set the destination of that client event to Process Originator to make testing easier
- Consider having multiple activities with client events so the process instance does not complete. This way you can delete the test instance(s) from the database via Workspace
- Include an e-mail event to make sure the SMTP connection is working.
- Build and Export the process
-
- Does it build OK?
- Does it export to the server OK?
- If you have a previously designed K2 Visual Studio Solution, try opening it up on the new machine.
- Test the newly deployed Process within K2 Workspace
- Open K2 Workspace \ Management
- Assign the test account Admin permissions on newly deployed process
- Start a new process instance under the Instances section
-
- Go to the Worklist (home icon in Workspace)
-
- Does the task appear here?
- Check the Viewflow for this worklist item
-
- Does it appear correctly?
- Action this item (via checkbox or the context menu)
- Test Reports within K2 Workspace
- Click the Home icon
- Select the Process Overview report
-
- Does the report appear?
- Does it contain the data for the new process instance?
- Test Notification Events and E-mail
- Within K2 Workspace browse to the Notification Events \ Notification Event Designer module
- Create a new event notification for the OnProcessStarted event for the test process previously create
-
- It is recommended to use an e-mail address of the current user so it can be easily verified
- Start a new process instance via K2 Workspace
- Does an e-mail get sent via the K2 event bus?
-
- If not:
-
- Check console for specific errors
- Make sure MSMQ is configured correctly
- Make sure K2 has correct SMTP configuration
- Test SmartObject Deployment
- Test K2 Worklist web part in SharePoint (Note: This is optional, only required if the web part has been deployed to a SharePoint environment)
- Do K2 tasks appear there?
-
- If not:
-
- Check Kerberos configuration between SharePoint and K2 (for a distributed install)
- Check Web Part configuration settings
- Test K2 Designer for SharePoint (Note: This is optional, only required if the feature has been deployed to a SharePoint environment)
- Build and deploy a simple workflow within this designer
-
- As stated in the Visual Studio section, you may consider having multiple activities with client events so the process instance does not complete. This way you can delete the test instance(s) from the database via Workspace.
- Confirm that this builds and deploys correctly.
- Test the starting of this process as appropriate (e.g., upload a new document)
- In K2 Workspace, delete any unwanted, active test process instances
- If the intent is to restore the original, clean backed up databases, this step can be skipped.
On the K2 Server
- Close the K2 Server console window
On the SQL Server
- Restore the original, clean backed up databases, if desired.
On the K2 Server
- Startup the K2 blackpearl Server service via Windows Services
