Choice of server hosting environment
IBM BPM is typically installed and executed on a Windows environment although Linux can be used as an alternative. The amount of RAM should be 4GBytes or better. 8GBytes is ideal. During solution development, the logs of the WAS server will need to be consulted frequently. This can cause problems if the developer's workstations hosting PD are remote from the Process Center/Process Server. The ideal solution is to export the directory hosting the logs on a network share so that they can be mounted/accessed remotely. This is easier if Process Center is installed on Windows but much more difficult if the Process Center is installed on Linux. Technology options exist to share files on Linux such as Samba but they need to be explicitly set up and we need to ensure that the evaluator has the skills to do this.
Choice of developer environment
The developer's environment should be a Windows machine for installation of Process Designer and/or Integration Designer. 4GBytes of RAM is sufficient for this task. Screen resolution should be as large as possible. Process Designer assumes high screen resolutions and the larger the better. The developer's environment should mount the directory from the server to show the logs from the server. This is also affected by the choice of hosting environment.
Even if IBM BPM Standard is the edition of the product being evaluated, install IBM BPM Advanced. The reason for this is to recognize that even though IBM BPM Advanced is being installed, we can trivially create profiles for IBM BPM Standard. Although having Advanced installed will consume additional disk space that is a small price to play. Experience has shown that as a PoC progresses, the evaluator may wish to see Advanced or, alternatively, a decision that Standard would suffice turns out to be incorrect. The penalty of installing Standard and then wishing to move up to Advanced is huge if Standard was what was installed in the first place.
When it is time to install the software, ensure that all possible packages are in your possession before starting out. Never assumes that additional packages or parts can be download while at the evaluators location. This includes the latest maintenance. Don't assume that Installation Manager can "reach out" to the Internet to download additional parts.
If all things are equal, use IBM DB2 as the database. Although the product is supported on a number of databases, it is a good bet that the developers who build the product are using DB2 on a constant basis. It is extremely likely that DB2 has been more thoroughly tested as a database than the other database types.
Bring any additional software packages that may be used with you. This includes any "tail tools" such as
LogExpert. If Web Services or REST APIs are to be used, brining soapUI is also strongly recommended.
|| |Item|Example|Reality| |DB Type|DB2, Oracle ...|| |DB Hostname|myhost.ibm.com|| |DB Port|50000|| |DB Admin Userid|db2admin|| |DB Admin Password|db2admin|| |PDW DB Name|PDWDB|| |||| |||| |||| ||||
|| |Item|Example|Reality| |Hostname|myhost.ibm.com|| |Admin userid|admin|| |Admin password|admin|| |||| |||| |||| ||||