A new integration developer has just deployed a new business module to the test cell using WebSphere Integration Developer (WID). The new integration developer does not have access to the Integrated Solutions Console (ISC) for the test cell, so the integration developer used the servers panel in WID to deploy the business module and got no errors. The new integration developer is complaining that any output in the SystemOut.log cannot be seen. What is the likely problem? The business module was:

• A. not started.
• B. not deployed using the ejbdeploy tool.
• C. not deployed using serviceDeploy tool.
• D. packaged in a JAR and not an EAR.

Thousands of parallel business processes are running in a production environment. The database administrator monitoring the Business Process Choreographer database observes that the amount of runtime data is filling up the available space and will reach the space limits very soon. What action should the deployment professional take to address the problem?

• A. Verify if the business integration applications in the environment provide different versions for
  business processes.
  Remove all unnecessary process templates using the deleteInvalidProcessTemplate script.
• B. Verify if process instances in the database are completed and are not needed for any reporting.
  Automate the process deletion using the deleteCompletedProcessInstances script.
• C. Review the database records and identify all work items for completed process instances.
  Advise the database administrator to remove all work item records for completed process
  instances.
• D. Review the status of all process instances using the Business Process Choreographer
  Explorer.
  Manually delete all process instances that are in completed status.

An application has been deployed on a clustered WebSphere Process Server environment using the Remote Messaging and Remote Support pattern. To handle asynchronous invocation problems, the store-and-forward capability is enabled for several applications. During the test phase one of the target services invoked by the application became unavailable. Which of the following statements is TRUE regarding recovery of events?

• A. No manual intervention is necessary. WebSphere Process Server will poll the target service
  and once it is available, all remaining sequenced
  events will be automatically processed.
• B. No manual intervention is necessary. If the store-and-forward feature is activated on a single
  cluster member due to a target service outage,
  the remaining cluster members will take over and complete the invocation transactions.
• C. Multiple failed events might have been created by different cluster members. All failed events
  must be resubmitted before the Store and
  Forward widget in the Business Space is set to Forward mode.
• D. A single failed event has been generated by one of the cluster members when the target
  service became unavailable. Resubmit all failed
  events once the target service is available.

Select the BEST order for creating a standalone profile for WebSphere Process Server 7.0.

• A. Install the product -> Run installer_wbi checksum tool -> Create profile -> Perform Installation Verification test
• B. Install the product -> Create profile -> Run installer_wbi checksum tool -> Perform Installation Verification test
• C. Install the product -> Create profile -> Perform Installation Verification test -> Run installver_wbi checksum tool
• D. Install the product -> Perform Installation Verification test -> Create profile -> Run installver_wbi checksum tool

A company has severe problems with two SCA modules being deployed on a production environment. The cluster consists of multiple nodes and many other applications are deployed already. After a first investigation of the problem, the root cause seems to be related to inter-module SCA invocations. The problem must be solved as soon as possible with a minimal effect on other applications. Which approach should a deployment professional recommend to troubleshoot the problem on a production environment?

• A. Enable a SCA component-related trace on all application servers and analyze the data using the Log Analyzer in the IBM Support Assistant (ISA).
• B. Enable a cross-component trace for both SCA modules on all application servers. Capture a snapshot data to correlate the problem with the application workflow.
• C. Enable a SCA component-related trace on all application servers in the clustered environment.
  Analyze the traces for the problem by comparing the data for all servers.
• D. Enable a SCA component-related performance metric using the Tivoli Performance Viewer (TPV) in the administrative console. Monitor the number of failing SCA invocations for both modules.