Datasource being required by JBEDS Translator for a VDB - Red Hat Customer Portal

Log in to Your Red Hat Account

Your Red Hat account gives you access to your profile, preferences, and services, depending on your status.

If you are a new customer, register now for access to product evaluations and purchasing capabilities.

Need access to an account?

If your company has an existing Red Hat account, your organization administrator can grant you access.

If you have any questions, please contact customer service.

Red Hat Account Number:

Red Hat Account

Customer Portal

For your security, if you’re on a public computer and have finished using your Red Hat services, please be sure to log out.

Select Your Language

Issue

I have a custom translator, it connects to an external system using a bespoke API. I have configured the VDB and left out the JNDI name for the translator, the translator is not using a resource adapter. For the translator to work, it must be deployed along with a datasource of the same name. This datasource is not used, however the VDB looks for it when being deployed. Can you please assist with why a datasource is being required? How do I get it to deploy and not look for this datasource?

Environment

Red Hat JBoss Data Services (EDS) 5.2. 5.3.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.

Here are the common uses of Markdown.

Code blocks

~~~
Code surrounded in tildes is easier to read
~~~

Links/URLs

[Red Hat Customer Portal](https://access.redhat.com)