Client application
To run this sample, use the client application that is delivered with this sample. In case you experience problems, please check the troubleshooting section below.
Client application delivered with the sample
To start the client application on a WebSphere® Process Server, follow these steps:
- In a web browser, open the URL
http://yourhost:yourport/SCAClientModuleWeb. - Unless you have already authenticated during the browser session, a login dialog will show up.
Enter userid and password, the default userid is
admin.
Note: Replace yourhost with your server's internet address and replace yourport with the port of your server's HTTP transport,
for example
The client application is displayed:
Start the sample
To start the business process, follow these steps:
- Switch to the client application.
- In the input field, enter a value of type string.
- Click Submit.
The output page is displayed:
Process output
Server log
Inspect the server log of your WebSphere Process Server. The simple process prints statements similar to the following to the server log:
Troubleshooting
Under certain circumstances, you may see error messages while working with the client application. In this section, some error symptoms are listed, together with possible root causes that may lead to those error symptoms.
Symptom:
When you open the URL http://yourhost:yourport/SCAClientModuleWeb,
for example http://localhost:9080/SCAClientModuleWeb,
you see this error message in the browser window:
HTTP 404 Not found - The webpage cannot be found
Possible reasons:
- The client application is not installed on the server, or the application is not started, or the server is not started. Make sure that the application SCAClientModuleApp is installed and started without errors.
- You have created then Web project SCAClientModuleWeb with a different context root rather the default context root (which is
SCAClientModuleWeb). In this case, the URL to use would have to reflect your context root and would no longer behttp://yourhost:yourport/SCAClientModuleWeb.
The context root can be modified via SCAClientModuleWeb > Properties > Web Project Settings. - You have created the files index.html and invoke.jsp in the wrong folder.
Make sure these files are located in the folder
/SCAClientModuleWeb/WebContent/.
Symptom:
You see the first screen of the client, but when you press Submit, you see this error message in browser window:
HTTP 500 Internal Server Error
In addition, in the server log you can see an error message containing this string:
Exception data: org.omg.CORBA.OBJECT_NOT_EXIST: SERVANT_NOT_FOUND
Possible reason:
- This error will show up if the application SCAClientModuleApp is installed but the application SimpleProcessModuleApp is not installed or not started. Make sure that the application SimpleProcessModuleApp is installed and started without errors.
Symptom:
You see the first screen of the client, but when you press Submit, you see this error message in browser window:
Error 500: javax.ejb.TransactionRolledbackLocalException: ; nested exception is: com.ibm.websphere.sca.ServiceRuntimeException: com.ibm.bpe.api.EngineStateObserverEventError: CWWBE0013E: An error occurred during the event handling of 'processStarted' in the observer plug-in type 'com.ibm.bpe.engine.observer.CEMStateObserverPlugin'
Possible reason:
- You have created the files index.html and invoke.jsp but accessing these
files is possible without login dialog.
Make sure these files are protected by a J2EE role that is mapped to authenticated users (not to "everyone"). Then test with a new browser session that a login dialog shows up when starting the client application.
If you think that further troubleshooting hints should be added to this list, you can send your feedback using the Questions? link.