Using a self-hosted integration runtime, I would like to use Azure Data Factory to connect to an on-premise Oracle database. Using the provided Oracle linked service, I can specify Host and Port, which works fine. Now I need to make a connection using an LDAP server, and I cannot find a way to do this using any connector in Azure Data Factory. Is this even possible?
You can use Teradata connector to authenticate LDAP.
Create Teradata linked service in Azure Data Factory.
Browse to the Manage tab on the left panel in your Azure Data Factory and select Linked Services, then click + New.
Search for Teradata and select the Teradata connector.
Configure the service details, select Authentication type as LDAP and test the connection, and create the new linked service.
Related
I want to connect to a Mondrian cube that I've developed using IBM Cognos.
On the Cognose framework I can't see the XMLA datasource on the list, the datasource connection should be an ODBO.
How can I made the ODBO connection available?
Regards
Monwabisa
https://sourceforge.net/projects/xmlaconnect/ works for connecting Excel with Mondrian via ODBO. Maybe it also works for your use case.
I have database username and password to access oracle db and also have service url like https://X-X.X.X.oraclecloudapps.com/apex/.
Can anybody know how to connect this db using JDBC connection.
I tried using oracle thin driver but somehow it failes.
Sample java code:
Connection conn = DriverManager.getConnection("jdbc:oracle:thin:#//X.X.X.X.oraclecloudapps.com:1521/sid", "username", "****");
It throws
Exception in thread "main" java.sql.SQLRecoverableException: Io exception: The Network Adapter could not establish the connection
I don't know SID here, it would be helpful if anybody give steps to find SID/ServiceName from Oracle Cloud dashboard.
You can't use JDBC to connect to the Database Schema Service. You can connect using the API or tools that utilize the REST API. For data upload to Oracle Database Schema Service, use Oracle SQL Developer, the Oracle Application Express SQL Workshop Data Upload Utility or the Oracle Application Express Data Load utility. Read more here: http://docs.oracle.com/cloud/latest/dbcs_schema/CSDBU/GUID-3B14CF7A-637B-4019-AAA7-A6DC5FF3D2AE.htm#CSDBU177
There is only three way to connect Database Schema Service.
From an Oracle Application Express application running in Database Schema Service
From a Java application running in an Oracle Java Cloud Service
Through RESTful Web services
Try the following JDBC URL to resolve the issue
"jdbc:oracle:thin:#host-address:1521/sid";
Note / is used after port and Not :
I'm trying to set up part of an application which uses MDBs to consume messages from a JMS Queue. I've looked through the Oracle documentation but can't seem to make sense of it. Examples on the internet seem to be for situations where your JMS server is the same weblogic server where you are consuming but in my case there is a separate server.
I've found this post Weblogic EJB connection to external Tibco EMS JMS Queue which gives broad strokes but seems to be written more for experienced weblogic users.
Specifically with the linked here is where I'm having trouble:
Create a foreign server with all the normal details (local/remote JNDI lookup names for destination and connection factories).
Not sure how to do this.
Create a local WL user with the same name as the remote EMS user, including password.
I cannot do this as my password is less than 8 characters
Create an ejb credential mapping (NOT security credential mapping)
do this by clicking on the relevant deployment, click on the relevant ejb name in the list, then Security tab then Credentials Mapping tab.
add the same name for WLS and Remote users (password doesn't seem to be necessary here).
Under Security I see Application/Module Scope tabs and Roles/Policies underneath those.
Can anyone give more detailed steps on how to set up a simple MDB in Weblogic 10.3.5 which consumes JMS messages from an external server (Tibco EMS)?
I have an ldap url, a selector (to filter out unwanted messages, not completely necessary), username and password, Queue name, EMS server url (which specifies a port), connection factory ldap. What do I do with this information?
You can configure a foreign server in weblogic and inside the foreign server you can provide the connection factory & destination details. The username, passwd & queue name that you have will be required to create these weblogic admin objects.
Weblogic foreign server configuration
While creating the destination you can provide the local jndi name which you can use in your MDB Activation configuration to connect to.
I'm inheriting an existing WMB flow that is ESQL-centric (Compute nodes) that accesses its database via an ODBC DSN. I'd prefer to use a configurable service for database access in lieu of an ODBC DSN, which is what I use with Java-centric flows (JavaCompute nodes).
Is it possible to configure a Compute node to talk to a db via a configurable service?
Yes, but you need to call a Java class from the ESQL.
See Connecting to an application database using JDBC
Can someone help me understand how to expose the SYS schema objects of a JBoss Teiid Virtual Database when connected via an ODBC-JDBC bridge ?
The client is connecting to ODBC side of the bridge and the JDBC side of it is connecting to the Virtual Database (VDB) running on the JBoss SOA server.
With the current setting only the tables and columns modeled thru the JBoss Studio's Teiid Designer are exposed but not the SYS schema and its underlying objects. Client App is Microstrategy BI application.
You are able to traverse all metadata from all used data sources using native JDBC JAVA API.
I am new to Teiid and had the similar question.
When you create the VDB with JBoss designer you can specify which models will be exposed to the client applications. As a good practice, only View models are exposed and Source models are not. As a result, querying against the System tables of the VDB will only show you the metadata within the View models, which will be a subset of the metadata in the underlying data sources.
Hope this helps.