MDB from AQ in OC4J Developers perview

Hi,
Can anyone help me solve the following error, when trying to instantiate MDB's from an Oracle
AQ ?
28/03/02 16:52 Error listening to 'AQ.QUEUE1'
java.lang.InstantiationException: Error: JMS-137: Payload factory must be specified for destinations with ADT payloads
     at com.evermind.server.jms.OrionServerSessionPool.getServerSessionFull(OrionServerSessionPool.java:377)
     at com.evermind.server.ejb.MessageDrivenHome.run(MessageDrivenHome.java:769)
     at com.evermind.util.ThreadPoolThread.run(ThreadPoolThread.java:66)
I am unable to find anyway in the docs to specify the Payload factory. Does a tag exist, or has
this been overlooked, and if so, are there any plans to introduce one?
I raised a TAR ( ref: 2048127.995 ) when this failed with the previous developers preview, and was
told it would be fixed in the next update ( 03/25/02 ), which I have now, and generated the above
error.
Thanks a lot,
Paul

Paul,
could you send me a small sample case if you have one, including a script to generate your queues, and I'll have a look into it.
Thanks,
Rob Cole
Oracle

Similar Messages

MDB from AQ in OC4J R2 developers preview.

Does any one have an example of the configuration reqired to instantiate MDBs from an Oracle AQ.
I can see no Oracle docs on this although it is listed as one of the features in OC4J R2.
Cheers,
Matt

good afternoon all -
The Oracle AQ integration for OC4J should function with the developer's release available on OTN. I do recall seeing a few issues that needed to be worked around, I will dig the email I have up and send that in a separate post.
What follows is a text cut-n-paste of a few sections from the J2EE Services Guide documentation we are providing for Release 2. These books are not yet published on OTN - I'll try and find out when we will be making them available, they contain a lot of good information.
Please take a read of this see if it helps you to configure Oracle AQ/OJMS as a JMS resource provider for OC4J.
cheers!
-steve-
Resource Providers
The ResourceProvider interface allows you to plug in third-party message providers (such as Oracle Advanced Queuing, MQSeries and SonicMQ) as JMS resource providers. This allows EJBs, servlets, and OC4J clients to access many different queue implementations. The third-party message providers are accessed through the ResourceProvider interface.
Note:
Except as noted here, you configure OC4J JMS as you would any other JMS implementation.
Plugging In Resource Providers
To add a custom resource provider to OC4J, you must add the <resource-provider> tag to orion-application.xml. This section describes how to add one such ResourceProvider.
An example ResourceProvider, ContextScanningResourceProvider, is bundled with OC4J. To use this ResourceProvider, you would add the following tag to orion-application.xml:
<resource-provider
class="com.evermind.server.deloyment.ContextScanningResourceProvider"
display-name="SwiftMQ">
<description>
SwiftMQ resource provider.
</description>
<property name="java.naming.factory.initial"
value="com.swiftmq.jndi.InitialContextFactoryImpl">
<property name="java.naming.provider.url"
value="smqp://localhost:4001">
</resource-provider>
This example makes SwiftMQ the default ResourceProvider for JMS connections -- the first <resource-provider> tag in orion-application.xml becomes the default resource provider for the types it handles. Adding this tag makes the resource available in the Orion JNDI under java:comp/resource/, as well as making SwiftMQ the default JMS resource for such actions as deploying a message-driven bean.
Configuring Message Providers
Install and configure the message provider according to the instructions in its documentation, then verify the installation by running any examples or tools supplied by the vendor.
Register the message provider in some JNDI-accessible store (a file system, an LDAP OiD, or the like.) Use JMS provider tools to configure and populate this JNDI store with, for instance, the provider's QueueConnectionFactory and the queues of interest.
Make the JNDI store accessible to OC4J by adding a <resource-provider> entity to orion-application.xml pointing to the JNDI store. This example demonstrates using SonicMQ as the message provider and the file system as the JNDI store:
<resource-provider
class="com.evermind.server.deployment.ContextScanningResourceProvider"
name="SonicJMS">
<property name="java.naming.factory.initial"
value="com.sun.jndi.fscontext.RefFSContextFactory" />
<property name="java.naming.provider.url"
value="file:/private/jndi-directory" />
</resource-provider>
Copy the required JNDI files (for a file-system JNDI, fscontext.jar and providerutils.jar) to $J2EE_HOME/lib.
Restart OC4J. Whenever you add, delete, or reconfigure a resource provider, you must restart OC4J.
JNDI Resource Provider Names
OC4J resource provider extensions create resources under the java:comp/resource JNDI name tree. OJMS resource names take the form:
java:comp/resource/ProviderName/ResourceType/ResourceName
where:
ProviderName
is the user-chosen name of the resource provider.
ResourceType
(required for Oracle AQ/OJMS resource providers only) is a fixed string that can take one of four values: QueueConnectionFactories, TopicConnectionFactories, Queues, or Topics. The specified value identifies the JMS resource as being of the appropriate administered object type.
ResourceName
is a user-chosen name for a JMS connection factory or a valid AQ queue name for a JMS destination. Valid Oracle AQ names conform to the [schema.]queue_name scheme.
Accessing Message Queues
OC4J applications can now access the message queues. Message queues can be accessed in one of two ways:
Through their names, as in
java:comp/resource/<Provider_Name>/<Queue_Name>
An application would access the queue like this:
queueConnectionFactory=(QueueConnectionFactory)
jndiContext.lookup("java:comp/resource/SonicJMS/QueueConnectionFactory");
By binding message-driven beans to queues in orion-ejb-jar.xml
To bind message-driven beans to queues in orion-ejb-jar, you would add a tag like:
<message-driven-deployment
connection-factory-location="java:comp/resource/SonicJMS/QueueConnectionFactory"
destination-location="java:comp/resource/SonicJMS/SampleQ1"
name="MessageBean">
Using Oracle AQ as a Resource Provider
To access Oracle AQ queues through JMS, you must do the following:
Create an RDBMS user through which the JMS application will connect to the back-end database. The user should have the necessary privileges to perform AQ operations. AQ allows any database user to access queues in any schema, provided the user has and the schema exports the appropriate access privileges.
Configure an OC4J resource provider with information about the back-end database. Create data sources or LDAP directory entries, if needed.
Access the resource using Oracle AQ/OJMS resource names, which include the ResourceName name component.
Configuration
The OC4J resource provider for OJMS is implemented by the class oracle.jms.OjmsContext. Each OJMS resource provider instance is a <resource-provider ...> XML element (a child element of the orion-application element) in the $J2EE_HOME/config/application.xml file.
There are 3 ways of configuring the OJMS resource provider.
Inline configuration (all relevant information for accessing the back-end database is specified within the resource-provider element in application.xml).
Data Source configuration (the resource-provider element in application.xml refers to a data-source element configured in data-sources.xml which contains information on accessing the back-end database).
LDAP configuration (the resource provider contains information to access an OID/LDAP directory which contains information on accessing the back-end database).
This section describes only the inline and data source configuration methods.
Inline Configuration
An inline resource provider configuration consists of a resource provider instance name (user-chosen, but unique among all resource providers configured in OC4J), a JDBC URL to connect to the back-end database, and the user/password to connect as. For example:
<resource-provider class="oracle.jms.OjmsContext" name="MyContext1">
<description>OJMS Context using thin JDBC</description>
<property name="url"
value="jdbc:oracle:thin:@myhost.foo.com:1521:mydb"></property>
<property name="username" value="myuser"></property>
<property name="password" value="mypass"></property>
</resource-provider>
<resource-provider class="oracle.jms.OjmsContext" name="MyContext2">
<description>OJMS Context using OCI JDBC</description>
<property name="url" value="jdbc:oracle:oci:@mydb.foo.com"></property>
<property name="username" value="myuser"></property>
<property name="password" value="mypass"></property>
</resource-provider>
This creates 2 resource providers, MyContext1 and MyContext2, that log in as myuser/mypass to the back-end database mydb using the thin and OCI JDBC drivers respectively.
Data Source Configuration
A data source resource provider configuration consists of a resource provider instance name (user-chosen, but unique among all resource providers configured in OC4J), a data source name, and the data source configuration (in data-sources.xml). For example:
<resource-provider class="oracle.jms.OjmsContext" name="MyContext3">
<description>OJMS Context using a datasource</description>
<property name="datasource" value="jdbc/MyDS3"></property>
</resource-provider>
<resource-provider class="oracle.jms.OjmsContext" name="MyContext4">
<description>OJMS Context using a datasource</description>
<property name="datasource" value="jdbc/MyDS4"></property>
</resource-provider>
in application.xml and the following data sources in data-sources.xml:
<data-source
class="oracle.jdbc.pool.OracleDataSource"
name="MyDS3"
location="jdbc/MyDS3"
xa-location="jdbc/xa/MyXADS3"
ejb-location="jdbc/MyEjbDS3"
url="jdbc:oracle:thin:@myhost.foo.com:1521:mydb"
username="myuser"
password="myuser"
inactivity-timeout="30"
/>
<data-source
class="oracle.jdbc.pool.OracleDataSource"
name="MyDS4"
location="jdbc/MyDS4"
xa-location="jdbc/xa/MyXADS4"
ejb-location="jdbc/MyEjbDS4"
url="jdbc:oracle:oci:@mydb.foo.com"
username="myuser"
password="myuser"
inactivity-timeout="30"
/>
This creates 2 resource providers, MyContext3 and MyContext4, that use the data sources jdbc/MyDS3 and jdbc/MyDS4 respectively to connect to the back-end database. The data sources themselves contain the appropriate JDBC driver/connect information.

Installing BPEL PM 10.1.2.0.2 for OC4J Developers on AIX

Hi
I'm trying to install BPEL PM 10.1.2.0.2 for OC4J Developers on AIX. I downloaded the as_aix5l_power_bpel_101202.cpio and ran the "./runInstaller" from the "bpel_oc4j" directory. As per the installation instructions(it did not specifically have instructions for AIX, only Windows and Unix), i should get a screen in which i can choose the Type of Installation as "BPEL Process Manager for Developers", but this option never showed up, instead after accepting the path this dialog came up.,
Error :
BPEL Process Manager for OracleAS Middle Tier will run on top of a supported Oracle Application Server 10.1.2 j2ee and Web Cache orPortal and Wireless instance. This location does not contain this instance. Please refer to the installation Guide for supported versions.Please select a new Oracle Home that contains a supported instance.
Has anyone installed the Developer's version of the BPEL PM on AIX?
Or is the download available is actually only for Middletier?
Alll help is appreciated.
Thanks
Sam

I also have a customer who is running BPEL on AIX / WAS 4.0. He has reported some issues while running some specific Java codes (JDK 1.5). Has anyone faced any issues with BPEL deployed on WAS having issues due to compatibility?
Any help is appreciated.

URGENT: Can't connect to a MDB from a standalone application

Hi, I hope somebody can help me. I'm trying to send messages to a MDB from a standalone client, but I have problems when looking up JMS queues and connection factories. The code is the following:
try {
Hashtable env = new Hashtable();
env.put(Context.INITIAL_CONTEXT_FACTORY, "com.evermind.server.rmi.RMIInitialContextFactory");
env.put(Context.PROVIDER_URL, "ormi://192.168.64.173:3101/PruebaAS");
env.put(Context.SECURITY_PRINCIPAL,"admin");
env.put(Context.SECURITY_CREDENTIALS, "admin");
jndiContext = new InitialContext(env);
catch (NamingException e) {
System.out.println("Can't create JNDI API" +
"Context:" + e.toString());
System.exit(1);
* Look up connection factory and queue. If either does
not exist, exit.
try {
queue = (Queue)
jndiContext.lookup("java:comp/resource/ojms/Queues/queue2");
catch (NamingException e) {
System.out.println("JNDI API lookup failed." +
e.toString());
System.exit(1);
When program tries to look up the queue, I get the message: "JNDI API lookup failed.javax.naming.NamingException: Disconnected: Unknown command: 7"
What's the meaning of "unknown command:7?? I have deployed the MDB to an Oracle 9iAS 9.0.2 using enterprise manager, and create queues in an Oracle 9i 9.2.0 Server.
Please, I need some help. Thanks in advance.

I'm no expert, but I did get something like this working. One gotcha is that you need to have an instance of the database driver, since the Oracle queues use the database. Try something like this before you attempt the JNDI lookup:
Class.forName("oracle.jdbc.driver.OracleDriver");
If necessary, replace "oracle.jdbc.driver.OracleDriver" with the appropriate driver for your environment. Good luck.

Urgent!!!!How to deploy only an EJB from Weblogic to oc4j.

Hi
How can i deploy only EJB from Weblogic into oc4j without any web application or client coming into pitcture as my client access bean remotely....
regards,
Sapthapathi

If you are migrating from ejb1.1->ejb1.1 you shouldn't have many changes - your ejb-jar.xml file should be the same (I assume you are still talking about ejbs). Once you pull over the base ejb - then if you want to, mess around with the automatically generated orion-ejb-jar.xml file. Obviously - those are all app server specific. I go back and forth between wls6.1 and oc4j all the time. When going from wls5.1 to oc4j - what particular issues do you run into. What do you mean, in particular, by configuration changes?
Curious -
Ray
hi,
EJBs and other applications can be migrated from weblogic to oc4j but many changes are required.These changes are mainly configuration changes rather than code changes.Infact there are many problems in effect while migrating and delloyment.Hope oracle is a bit more attentive to this issue.
regards,
chennai

Copying 1.2 GB mdb from pc to network

When copying 1.2 GB mdb from pc to network, it seems that the copy created in the network is corrupted although I'm not able to tell by looking at the size of the file. Does anyone have an experience of copying a big mdb file from pc to network?

Restore an entire database
When you restore an entire database, you replace a database file that is damaged, has data problems, or is missing altogether, with a backup of the entire database.
If the database file is missing, copy the backup to the location where the database should be.
IMPORTANT If other databases or programs have links to objects in the database that you are restoring, it is critical that you restore the database to the correct location. If you do not, links to the database objects will not work and will have to be
re-created, such as by using the Linked Table Manager.
If the database file is damaged or has data problems, delete the damaged file and then replace the damaged file with the backup.

Migrating from jserv to OC4J

Are there some documents related to this theme?
Please help me.
I'm obtaining an error when i deploy the app to oc4j, referent to jdbc connection.

There was a generic Migration guide produced for the earlier 9.0.2 release with some content on migrating from JServ to OC4J.
http://download-west.oracle.com/docs/cd/A97331_08/migrate.902/migrate/intapps.htm#1006415
It's hard to provide much help without more details.
cheers
-steve-

Migrating from JServ to OC4J: problems with XSQLServlet configuration

I'm trying to move an application using xsql pages from 9iAS to 10g (9.04). Development is currently done under JDev9 (9.02) an its OC4J standalone server.
I guess I've done most of the configurations, since the application is working correctly now, BUT only with the connections defined statically in the XSQLConfig.xml of the XSQLServlet. On JServ, we implemented our own connection manager to pass our connections to the XSQLServlet as defined by the <connection-manager><factory> tag. Now, under OC4J, this no longer works:
The log files tells:
Failed to create custom connection manager factory: "our.connection.manager.factory": Using default.
And with the default one, we get of course the 'cannot acquire database connection' error message which is ok, since we're not using one of those defined under XSQLConfig.xml...
Background: Our connection manager is contained in a jar file with many other classes. These are visible to the 2 applications ("P" and "T") we're running successfully under OC4J Standalone. As I interprete the message as the XSQLServlet not being able to create an instance of our ConnectionManager, I guess I missed somewhere an library or classpath entry??
Many thanx for any hints!

There was a generic Migration guide produced for the earlier 9.0.2 release with some content on migrating from JServ to OC4J.
http://download-west.oracle.com/docs/cd/A97331_08/migrate.902/migrate/intapps.htm#1006415
It's hard to provide much help without more details.
cheers
-steve-

Stop MDB from listening to a JMS queue

Hello,
From time to time we would like to stop the processing done in our application.
The processing is started by onMessage() in MDB. Is it possible to tell the MDB
to stop listening
to the JMS queue or stop the delivery of messages by JMS ? We do not intent to
stop the processing of messages that have already started by only to stop processing
of further messages (the ones still in the JMS queue).
We are using 6.1SP3.
Any help is appreciated.
Eric Poupaert,
Approach Belgium SA.

If you can tune the number of messages that should be sent to the MDB to 0, that would
temporarily stop the MDB from consuming messages. Thsi is the "Messages maximum"
parameter on ur connectionfactory. WL6 doesnt support changing this value to 0 but there
were some newsgroup discussions last year that it might be supported in a future
release. Maybe its fixed in 8?
Eric Poupaert wrote:
Hello,
From time to time we would like to stop the processing done in our application.
The processing is started by onMessage() in MDB. Is it possible to tell the MDB
to stop listening
to the JMS queue or stop the delivery of messages by JMS ? We do not intent to
stop the processing of messages that have already started by only to stop processing
of further messages (the ones still in the JMS queue).
We are using 6.1SP3.
Any help is appreciated.
Eric Poupaert,
Approach Belgium SA.

Porting EJB 3 MDB from OC4J to WLS

Posting this again since my last post didn't seem to take.
I get the following three deployment error messages when attempting to deploy an application to WebLogic Server 10.3 technical preview. The problem is centered around my deployment of an EJB 3 message driven bean.
1. An error occurred during activation of changes, please see the log for details.
2. Exception preparing module: EJBModule(EngineEjb.jar) Unable to deploy EJB: Requestor from EngineEjb.jar: [EJB:011026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment. weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'jms/demoQueue' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation. at weblogic.ejb.container.deployer.EnvironmentBuilder.addResourceEnvReferences(EnvironmentBuilder.java:641) at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentContext(EJBDeployer.java:246) at weblogic.ejb.container.deployer.EJBDeployer.setupEnvironmentFor(EJBDeployer.java:1013) at weblogic.ejb.container.deployer.EJBDeployer.setupBeanInfos(EJBDeployer.java:907) at weblogic.ejb.container.deployer.EJBDeployer.prepare(EJBDeployer.java:1211) at weblogic.ejb.container.deployer.EJBModule.prepare(EJBModule.java:387) at weblogic.application.internal.flow.ModuleListenerInvoker.prepare(ModuleListenerInvoker.java:93) at weblogic.application.internal.flow.DeploymentCallbackFlow$1.next(DeploymentCallbackFlow.java:381) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:56) at weblogic.application.internal.flow.DeploymentCallbackFlow.prepare(DeploymentCallbackFlow.java:46) at weblogic.application.internal.BaseDeployment$1.next(BaseDeployment.java:615) at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26) at weblogic.application.internal.BaseDeployment.prepare(BaseDeployment.java:191) at weblogic.application.internal.EarDeployment.prepare(EarDeployment.java:16) at weblogic.application.internal.DeploymentStateChecker.prepare(DeploymentStateChecker.java:147) at weblogic.deploy.internal.targetserver.AppContainerInvoker.prepare(AppContainerInvoker.java:61) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.createAndPrepareContainer(ActivateOperation.java:197) at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doPrepare(ActivateOperation.java:89) at weblogic.deploy.internal.targetserver.operations.AbstractOperation.prepare(AbstractOperation.java:217) at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentPrepare(DeploymentManager.java:723) at weblogic.deploy.internal.targetserver.DeploymentManager.prepareDeploymentList(DeploymentManager.java:1190) at weblogic.deploy.internal.targetserver.DeploymentManager.handlePrepare(DeploymentManager.java:248) at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.prepare(DeploymentServiceDispatcher.java:159) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doPrepareCallback(DeploymentReceiverCallbackDeliverer.java:157) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$000(DeploymentReceiverCallbackDeliverer.java:12) at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$1.run(DeploymentReceiverCallbackDeliverer.java:45) at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:517) at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201) at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
3. Substituted for missing class [EJB - 11026]The EJB container failed while creating the java:/comp/env namespace for this EJB deployment. weblogic.deployment.EnvironmentException: [EJB:010176]The resource-env-ref 'jms/demoQueue' declared in the ejb-jar.xml descriptor or annotation has no JNDI name mapped to it. The resource-ref must be mapped to a JNDI name using the resource-description element of the weblogic-ejb-jar.xml descriptor or corresponding annotation.
My MDB uses an annotation like the following:
@MessageDriven(mappedName = "jms/demoQueue", name = "MyMDB",
activationConfig =
@ActivationConfigProperty(propertyName = "destinationType",
propertyValue = "javax.jms.Queue")
@ActivationConfigProperty(propertyName = "messageSelector", propertyValue =
"RECIPIENT = 'MyRecipient'")
Earlier, I did create a JMS Module named demoQueue with the following resources:
Name Type JNDI Name
testQueue Queue jms/demoQueue
ConnectionFactory-0 Connection Factory jms/QueueConnectionFactory
Any suggestions to fix the WLS deployment error?
For continuing compatibility with my OC4J deployment, I would like to continue using a connection factory with the following JNDI name "jms/QueueConnectionFactory" shown above.
So I plan to add the following properties to the @MessageDriven annotation above. These are needed to continue working with our OC4J deployment. However, my primary concern is to get this MDB working with WLS. Does this strategy seem reasonable for allowing deployment to both OC4J and WLS?
@ActivationConfigProperty(propertyName = "connectionFactoryJndiName",
propertyValue =
"jms/QueueConnectionFactory") ,
@ActivationConfigProperty(propertyName = "destinationName", propertyValue =
"jms/demoQueue")
Thanks,
Travis

Travis, you pose a very good question. If I understand your goal, you would like to use code that compiles and works in OC4J and WLS. For example, you want to use javax.ejb.MessageDriven instead of weblogic.ejbgen.MessageDriven.
Using something like mappedName as it is referred to here allows you specify the JNDI name in WLS if it is not defined elsewhere, but it appears to be specific to the WLS implementation.
I've seen several other questions posed about finding all of the available ActivationConfigProperty name / value pairs and I have been unable to find it myself.
I tried several permutations of annotations, and I can't figure out why something like this would even work, but it does. The mapped name is my JNDI name, but I never specify that it is a javax.jms.Queue or which connection factory to use. How does WLS figure that out?
@MessageDriven(
     mappedName = "exampleQueue", name = "HelloWorldMDB"
public class HelloWorldMDB implements MessageListener {
     @Override
     @TransactionAttribute(value = javax.ejb.TransactionAttributeType.REQUIRED)
     public void onMessage(Message message) {
          System.out.println( "received message " + message );
}This is a good question for support as the documentation seems to be incomplete here.

Error while creating a connection from JDeveloper to OC4J instance on 9iAS

I m trying to create a connection to the application server(9iAS release 2) from the JDeveloper(9.0.2.822) using the JDeveloper connection wizard. I followed all the steps, but when i click on "Test Connection" button to test the connection the error i get is "IO Error: Connection refused: connect". The description of the settings i provided in the wizard step are as follows,
Step 1
Connection name:- Connection1
Connection Type:- Oracle 9i Application Server
Step 2
Username:- admin
Password:- welcome
Deploy Password checkbox: Unchecked
Step 3 (the 9iAS server address is 192.168.30.162)
URL:- ormi://192.168.30.162/
Target Web Site:- http-web-site
Local dir where admin.jar is installed for Oracle 9iAS is installed:- C:\ora9i_d2k\j2ee\home
Step 4
Test Connection: “IO Error: Connection refused: connect”
Please advise.
Thanks
Unmesh

Hi,
You cannot connect to an Oracle9iAS environment directly using the connections node. You can only connect to an individual OC4J instance using this technique.
You need to use Oracle9iAS Distributed Management Configuration (DCM). See JDeveloper Help under Creating Application Server Connections

OC4J developers preview edition

hi!
At the moment I'm in a starting J2EE project involved.
I have to decide, which OC4J version to use. My choice would be the developers preview edition,
but will the production release be shipped by november?
Because this would be the deadline of the project, and I can't install a developers edition
on a production system.
thanx
ed

Hi Paul,
I had similiar problems like the one you describe.
I got the JMS example (CoffeeMaker) running, but had problems with my own application ( Object not bound).
In my case, I got it running now when I only use the absolute necessary (oc4j.jar, junit.jar in my case) in my classpath
(of course the application client xml's must contain your lookup names, but I did not !!! have to setup
my queue in jms.xml (wonder why).
You might try this (oc4j.jar references the required libs for jms,jndi,etc. internally)
[Comment to "absolute necessary": of course I have a CLASSPATH which contains only the necessary libs.
But since we are working on a framework which does not only want to connect to OC4J JMS (or EJB), I have
a CLASSPATH containing other libs. I have to find the correct order, I guess.]
But still my question to this forum: how is it possible that a queue is started "implicitly" (that means it is
not configured in jms.xml). Is this desired or mandatory (Sun J2EE reference implementation does the same).
Or am I missing something ?
Regards,
Armin

Accessing *.mdb from java

Hello,
I�m working in an aplicattion (developed under Linux), that reads an access file and update an Oracle Database. It works under Windows, but not in Linux.
I can�t install a driver, because I need to be root, so I can�t. Can anyone help me?
import java.sql.Connection; import java.sql.DriverManager; import java.sql.PreparedStatement; import java.sql.ResultSet; import java.sql.SQLException; public class AccesoMdb { /** * @param args */ public static void main(String[] args)throws SQLException { ResultSet rs=null; PreparedStatement ps = null; try{ Class.forName("sun.jdbc.odbc.JdbcOdbcDriver"); System.out.println("inicio"); String url = "jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=/home/user/Database.mdb"; //It breaks here, line down Connection db = DriverManager.getConnection (url, "",""); String query="SELECT * FROM ....."; ps = db.prepareStatement(query); rs = ps.executeQuery(); while(rs.next()){ //Oracle inserts } System.out.println("finish"); }catch (Exception e) { e.getMessage(); } } }
Edited by: Abel_Zafra on Jun 27, 2008 3:44 AM

kajbj wrote:
duffymo wrote:
Use the Oracle JDBC driver and you won't need to be root. It's pure Java, and doesn't require ODBC to be installed.
Google for "Oracle JDBC download" and get the version that matches your JDK.
%I think the problem is the access database (isn't that what an mdb is?)reading too fast again. my brain took in the "to Oracle" and forgot about the "from Access".
%

Accessing MSAccess DB mdb from java program deployed on Unix

Could someone provide the solution for connecting MSAccess DB which is on a Windows Server
from a java web application deployed on weblogic in Unix platform.
Basically i would like to know how we can get access to the mdb file on windows.
jdbc:odbc:Driver={Microsoft Access Driver (*.mdb)};DBQ=c:/employee.mdb;DriverID=22;READONLY=true"
Im using sun.jdbc.odbc.JdbcOdbcDriver.

spectator wrote:
Thanks for the reply ..
This url given works perfectly for a java appln in windows as the .mdb path (c:/employee.mdb or from a shared drive \\shared\employee.mdb) is understood by the appln
But my java application in Unix wants to call AccessDB in Windows.
I wanted know how we can connect from java appln in Unix to an Access DB which is in Windows like any other database ie through a hostname port etc. or any other wayBasically you can't.
You can start by reading the following.
[http://forums.sun.com/thread.jspa?threadID=211735&start=2&forumID=48]
There is an update to that post in that now there is a java only commercial (you must pay for it) driver that one can use for MS Access. So that option exists now.

Deploying Session EJB From Jdev9i(Beta) - OC4J 9i

Hi All ,
I wanted from u , i have recently Upgraded to Oracle 9i 1.0.2.2.1 (OC4J) . Now i want a simple Step wise process as how can i deploy my Ejb (Session Bean ) into the OC4J container and Use its DataSource .
Is it possible to deploy using Jdev 9i (Beta) .
Can any one please help me out to point to a Documentaion , give me a breif process .
Regards
Asif

Asif -
Yes you can use Jdeveloper 9i beta to deploy your session ejb.
Step 1 should be setting up your Data Source. In the System
Navigator Panel expand the "Connections" listing. Right-click
on "Database" and select "New Connection..." - follow the
wizard's instructions to set up your data source. Step 2 should
be setting up a connection to the OC4J container - again on the
System Navigator Panel ->Connections->Application Servers -
follow the instructions there. I am assuming that you have
developed your session ejb using Jdeveloper, right click on
your .jpr entry (or wherever suits you) and choose "New..." then
Deployment Profiles. You need to package your session ejb into a
jar file and I would recommend packaging your jar file into an
ear file (it really helps for clean deployment). If you have a
web portion, package that and make it dependent on the jar file
just to keep it straight. Once you have these, you will be able
to right click on the jar or web file and deploy to an ear file,
or straight to the server. If this is what you are looking for,
you will then just select this and away you go.
Apparently there are some howtos here:
http://otn.oracle.com/docs/products/jdev/howto.html
although I don't know how good they are.
I wasn't quite sure what you were looking for so this post is
vague. If you have specific questions, let me know and I will
try and answer them!
Cheers
Ray

MDB from AQ in OC4J Developers perview

Similar Messages

Maybe you are looking for