Lombardi Admin Training Notes 18dec2008
Client install
on day one, we covered being able to create a client for end users, where you can copy from the server install directory to the client machine (no install needed). You need to copy the full path, so if your server is installed in C:\Teamworks61bsr you need to make sure to create that same directory c:\Teamworks61brs on the target machine, then just copy both ae-eclipse and java directories and contents. You dont need any of the other data for the client to work.
You can launch the AE in advance and customize it for your users in advance. When you launch the AE, if you go to window->preferences->teamworks->capabilities you can remove options to create processes, services, etc. This does not lock out the user from re-enabling these options, it only limits what they initially see. so, if your users only need to create specific things, you can only show those options here.
User Attributes
You can create user attributes, which are basically datatypes in teamworks. The difference is, these datatypes are assigned to users, and you can then provide these values for users as a kind of metadata. You can then use these pieces of metadata for routing later in the process. We should be able to import the attribute list from AD. not sure how to do it, but the instructor says its possible. Here is how we do it by hand, using local teamworks users and attributes.
Calendars
- Calendars are implemented in timer events
- Calendars are assigned to users or user groups for use in timer events
- if you check "Use business calendar" when setting up a timer event, it will look at the participants and follow the rules of the participants calendar to determine the actual duration of the timer based on their working calendar. For example, if a task is assigned and set to be done within 4 hours and a task is started at 10pm at night for the assigned person, if the "use business calendar" is set, the timer will not start until the time the calendar says the assigned person is available, which in this case might be 9am the next morning (for a normal business day).
Setup Calendars for Use
- Calendars are bound by region (you can select the proper timezone, weekend days, holidays, etc
- Calendars should always be assigned to groups rather than individual users, and the groups should be based on region.
- When you create the initial calendars, you can give process developers access to the link to "Maintain calendars" in the process server console so that they can modify work time, holidays, etc.
- Calendars are created in the AE, but assigned to groups in the process server console.
Maintain Blackout Periods
- From the process server console, Admin tools->Event Manager->Blackout Periods
- Specifying a blackout period means that scheduled events will not run during that time. you can use that for scheduled system maintenance.
Customizing the Portal
The portal HTML is laid out using the following
- HTML for basic layout
- CSS for skinning (colors, etc)
- XML with items and constraints for displaying navigation and menu items
- jsp for rendering dynamic page content
JBoss DataSources
- the datasource config file is here C:\Teamworks61bsr\process-server\deploy\mssql-ds.xml (or oracle-ds.xml for oracle)
- you can make copy the entire <local-tx-datasource> element, change the jndi connection name and connection url. You'll then be able to access this datasource from code using the jndi name.
- you need to increase the min connection pool size. The teamworks recommendation is 2 times the number of expected connections. (info in the wiki)
- after you make changes and save the file, restart the process server.
Log Files
Two general log types, process server logs and performance server logs. You can also access the same logs via the server console under Admin tools->View TW Logs
- Process server logs: C:\Teamworks61bsr\process-server\logs
- Performance server logs: C:\Teamworks61bsr\performance-server\logs
- Important log files
- TW Error Log (tw-error.log, most any error anywhere in the java server should show here)
- Event Manager Log (tw-eventmgr.log, for event manager specific info)
- Logs are configured via an xml file: C:\Teamworks61bsr\process-server\conf\log4j-jboss.xml
- Log4j is a standardized logging tool, many of the configurations should be work the same here as in Log4j
- in the file, "Limit Categories" section defines what is logged. In a dev environment, you can uncomment the debug categories.
- you can change what logs your developers have access to in the server console by modifying this file: C:\Teamworks61bsr\process-server\resources\config\system\50AppServer.xml
Cleanup Utility
For use when the database grows large over time. Running the cleanup utility will remove no longer needed database records for comlpeted and/or orphaned process instances.
- Accessed via the process portal under Admin Tools->Cleanup Utility
Process Monitor
this is the server console view of processes currently running on the server. Individual users running the AE can see their own processes, but here you can see all processes and statistics.
- in the process server console, goto Admin tool -> Process Monitor
- to troubleshoot runaway processes, you should check this view, look for the most expensive process and check the number of steps and the runtime. If the step count is high (in the thousands or more) it is most likely in an infinate loop and needs to be halted.