When developing BPEL and ESB applications it is necessary to see if the message you sent actually made it on the queue. Using Hermes is an excellent way to view an application server queues and topics.
Need to view messages on a JMS Queue or Topic that you have published a message to.
By default the the password for eis/Jms/TopicConnectionFactory JMS Connection is welcome1. This needs to be changed if the oc4jadmin password is not set to this.
After creating an ESB process you are unable to write to a JMS topic. The following error message is displayed in the ESB Console:
The Adapter Framework was unable to establish an outbound JCA connection due to the following issue: ORABPEL-12133
Unable to create JMS connection due to JMS exception.
Please examine the log file to determine the problem.
[Caused by: JMSServer[soasuite01.markcallen.com:12601]: failed to authenticate "oc4jadmin/welcome1" via "[JAZNUserAdaptor: user=oc4jadmin]".]
The password for the TopicConnectionFactory needs to be changed.
Go to the SOA Suite Enterprise Manager:
Click on the Home JVM
Click on the Applications tab
Select Standalone Applications from the View drop down list
Click on the JMSAdapter link
Click on the Connection Factories tab
Click on eis/JMS/TopicConnectionFactory
Change the password to the SOA Suites oc4jadmin password.
After installing Oracle XE you should setup backups.
Backups for XE
For Oracle XE there is ready a backup script that uses Oracle’s RMAN.
Setup Archive Log Mode
After installing the database change it to archivelog mode:
[oracle@localhost ~]$ sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Sun May 25 01:28:00 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect / as sysdba
SQL> shutdown immediate
ORACLE instance shut down.
SQL> startup mount
ORACLE instance started.
Total System Global Area 289406976 bytes
Fixed Size 1258488 bytes
Variable Size 92277768 bytes
Database Buffers 192937984 bytes
Redo Buffers 2932736 bytes
SQL> alter database archivelog;
SQL> alter database open;
To make sure the database is really in archive log mode run the following sql statement:
SQL> SELECT LOG_MODE FROM SYS.V$DATABASE;
Run the Initial Backup
Windows run $ORACLE_HOME/bin/Backup.bat
Linux run $ORACLE_HOME/config/scripts/backup.sh
[oracle@localhost ~]$ $ORACLE_HOME/config/scripts/backup.sh
Doing online backup of the database.
Backup of the database succeeded.
Log file is at /usr/lib/oracle/xe/oxe_backup_current.log.
Press ENTER key to exit
Run the Backups Daily
Windows add the $ORACLE_HOME/bin/Backup.bat to a job scheduler.
Make sure the user running the job is the same user who installed Oracle.
Linux add the $ORACLE_HOME/config/scripts/backup.sh to cron.daily
Remove the user notification line from the end of the script
Backing up files
Make sure that your backup script backups up the $ORACLE_HOME directory. On windows make sure the oradata directory is excluded since this might cause file locking issues.