Start the Visual Administrator for the SAP Application Server.
Once you are connected, select the Cluster tab.
Expand the server instance.
Click on the [Deploy] service.
On the bottom of the middle pane select the [Application] radio button.
Figure 21: Deploy Application
The frame now displays all the deployed applications on this server instance.
On the right side, click on the [Deploy]button.
A deploy dialog will appear.
Click on the button to the right of the File input field.
A Choose ear file dialog will appear.
Browse to the path of the others/terajmsa.ear file.
Click the [OK] button.
Figure 22: Deploy
You might see a WARNING dialog stating that directory contents used for extracting the EAR file will be deleted.
Click the [OK] button.
After a while, a dialog displaying the EAR file contents will be displayed.
You can expand the modules under the terajmsa.ear to view the subcomponents.
Click the [OK] button to start the deployment.
Figure 23: Deploy
The deployment usually takes a few minutes.
The progress bar is on the bottom right of the visual administrator window.
When the icon on the bottom left changes from a stopwatch to a green diamond, deployment is complete.
If there were problems during deployment, the stopwatch changes to a red diamond.
Click on the 'i' button next to the progress bar to see a short explanation of the problem.
If the deployment was successful you will see the application added to the list of deployed components.
Click on the com.teradata/Teradata JMS Universal Connector application and then click on the [Start Application] button on the right.
Figure 24: Start Application
You will see a Start Application dialog.
Make sure the “include” is checked for the given server Name.
Click on the [OK] button.
You should now see a blue check mark next to the application.
This completes the deployment process.
Standard Out log files are located in the following directory.
The log file name is defaultTraceX.trc where X is a number between 0 and 19.
After a restart of the SAP Application Server, any Loader or Router services with a status of started before the Application Server restart fails to start. Any attempts to restart the service by first stopping the service will produce a "Stop service -- Unable to find Service [MyService]!" error. This is an issue because the default configuration for the Deployment service starts before the JDBC Connector service or the JMS Provider service starts. The JMS Universal Connector requires both the JDBC Connector service and the JMS Provider service to be started before initialization of the JMS Universal Connector Servlet. The workaround is to restart the JMS Universal Connector Servlet.
Stopping a Loader service is dependent on the receiveTimeout. That is the Loader service must wait at most receiveTimeout seconds before the Loader service stops completely even if the service is idle. This is an issue because SAP’s JMS implementation does not conform to the JMS specification. According to the JMS specification, a call to MessageConsumer.close() should close the connection immediately if the connection is idle. For SAP, calling MessageConsumer.close() appears to do nothing.
Services using Durable Topics can stop working after some period of time. If you copy the Service with the non-working Durable Topic, the newly created service will work. This is an intermittent issue with the SAP Application Server.