1. Download the JD Edwards EnterpriseOne Data Access Driver (DAD) driver:
Select My Oracle Support, then Patches, and then Software and Patch Search Sites.
- Reading and Writing Complex XML files in ODI - Part1. I have installed ODI11g in my windows laptop and put the all_employees.properties file in the below location C: Oracle product 11.1.1 Oracle_ODI_1 oracledi agent drivers. ODI 12c Installation and ODI 12c Repository upgrade ODI 12c version is releases and it has come with.
- Driver in the following location. C: oracle ODI ODI1213 odi. Component in ODI 12c. 3) Rename the file back to the original name,archive in a different folder (folder2) and delete it from the folder1. 4) Repeat the steps until there is no file left to process in folder1. But my problem is ODI is not recognizing the named ranges in the second file even though they are exactly same as the first file. Kindly help me with this. Thanks in advance.
- ODI 12c Tutorial Lession4 on Topology Overview How to create Physical Data Server, Physical Schema and Logical Schema and Context in Topology. ODI 12c Tutorial ODI 12c Tutorial for beginners ODI.
- It's time for a refresher on ODI 12c. I’m continuing the Oracle Data Integrator 12c: Getting Started series with the topic: Installation and Configuration.
- From JDEdwards, enter: EnterpriseOne Tools Releases.
- In Release, select All Releases.
- In Platform, select Multiplatform.
- In Description (*text*), select *Data Access Driver*.
- Select the License Agreement check box.
- Click Search.
- Click the plus sign (+) to add Tools 9.1 Data Access Driver to the Download Basket.
- Click the Item(s) hyperlink and download the tools release specific item.
How to enable or disable ewallet password in ODI? Below screenshot shows how to enable or disable ewallet password storage in ODI 12c. Go to ODI studio -> Tools -> Preferences. Cselect ODI -> user_Interface, here we can see Save Login Credentials into Wallet option.
2. To copy the DAD Drive to the ODI Agent Driver directory, unzip the archive file to a temporary directory. Extract the JAR file DADriver_EAR.jar. Then, copy the extracted contents of DADriver_EAR.jar to the ODI Agent Driver directory. If you are running the standalone ODI Agent, then the directory in a default installation is: C:Oracleproduct11.1.1Oracle_DI_1oraclediagentdrivers
![Odi Odi](https://i2.wp.com/dbaontap.com/wp-content/uploads/2015/09/OPC-DB5.png)
3. Register the JD Edwards EnterpriseOne Data Access Driver by way of the Server Manager.
The combined Server Manager Agent (installed on the Oracle Data Integrator server) and Server Manager Console are used to register the JD Edwards EnterpriseOne Data Access Driver. This process generates the jas.ini file, jdbj.ini file, and jdelog.properties file, and extracts the JD Edwards EnterpriseOne Data Access Driver jar files to a target location.
The combined Server Manager Agent (installed on the Oracle Data Integrator server) and Server Manager Console are used to register the JD Edwards EnterpriseOne Data Access Driver. This process generates the jas.ini file, jdbj.ini file, and jdelog.properties file, and extracts the JD Edwards EnterpriseOne Data Access Driver jar files to a target location.
- From the Server Manager Console, select the Managed Home Location named for your Oracle Data Integrator Server.
- Click Create New Managed Instance.
- From the panel that follows, select the EnterpriseOne Data Access Driver radio button.
- Click Continue.
- Complete the form fields as follows, and click Continue.
6. Complete the form fields based upon configuration attributes of the environment; and click Continue.
Caution! Click Continue only once and wait for the panel to change.
7. Click Create Instance.
4. Navigate to the recently created Server Manager Agent JDBC driver configuration install location.
For example, navigate to: C:JDE_HOMEtargetsJDEJDBC_DADconfig
5. Copy the jas.ini file, jdbj.ini file, and jdelog.properties file from the JDE Application Server to the ODI Agent Driver directory. If you are running a standalone ODI Agent, then the directory in a default installation is: C:Oracleproduct11.1.1Oracle_DI_1oraclediagentdrivers
6. Ensure that the security server of the jas.ini file is set correctly.
7. Review and edit the jdbj.ini file as follows:
If the JD Edwards application database is Oracle, update the location to the tnsnames.ora file. It is imperative that you encrypt the [JDBj-BOOTSTRAP SESSION] stanza, then the password value.
Modifications to the .INI file password encryption can only be accomplished through the use of Server Manager.
Set the value of following parameters under [JDBj-RUNTIME PROPERTIES] stanza to:
Modifications to the .INI file password encryption can only be accomplished through the use of Server Manager.
Set the value of following parameters under [JDBj-RUNTIME PROPERTIES] stanza to:
resultSetTimeout=-1
transactionTimeout=-1
usageExecutionThreshold=20000
usageResultSetOpenThreshold=120000
usageTracking=false
msSQLQueryTimeout=1800000
8. Edit the jdelog.properties file and set the log level as needed. In a production environment, set the log level to SEVERE so that only severe errors are reported in the log file.
9. Ensure you can access the server specified in the jdbj.ini file from the ODI Server. Sometimes the .INI file may contain a server host name without a domain suffix. If needed, create an entry in the host file of the ODI Server so that the JDE server can be accessed.
Thanks,
~KKT~
~KKT~
Advertisements
How many times have you been working on a project and something goes wrong, or the power shuts off, or you go on vacation and someone has messed with your code or somehow your work is lost? Well, now you have an alternative to safe proof your project work.
Versioning in ODI is allowed at various hierarchy levels within the instances and is stored in the master repository. What this means is that if you have multiple work repositories connected to the same master, you can see all the versions when connected to either work repository.
A version is a backup copy of an object that is saved as a checkpoint in ODI. ODI allows you to version Projects, Folders, Packages, Scenarios, Load Plans, Mappings, Procedures, Knowledge Modules, Models, Model Folders and Solutions. You will need to decide which objects to create and manage versions for, but this tutorial will review the process using Packages.
Fast Review: A package is made up of steps organized into a diagram that is executed. The steps include mappings, variables, procedures, ODI tools (such as OdiXMLConcat, OdiZip, etc), models, sub-models and datastores.
- Connect and move to the Designer Navigator and expand the Projects folder.
- Select and expand Packages. In our example I will open up Target Data Load.
- As you see below a well trained ODI developer has set up the load plans to run in a specific execution and if any fail, to send an email.
In addition to a fail notification, a new manager also wants to know the package executed successfully. We will create an original version of the package and then add a new email notification. Once we have finished our changes, we will create a new version. - Right-click on the Target Data Load package and select Version > Create Version
- Type 'Target Data Load v1' as the name and 'Existing Target Data Load package (original)' in the description. You can name the original (or next version, depending on where you are in your versions) whatever you would like. Best practice is to keep the name simple and a version. Make sure to put more descriptive details about the purpose of the version in the description box below the version name.
Now that we have our original version safely created, we can make our changes to the package. - If it is not expanded, expand the Internet accordion of the ODI toolbox and locate OdiSendMail. Highlight OdiSendMail and place it on the canvas to the right
- Using the toolbar connect your last mapping to OdiSendMail 2 using the green ok arrow. Remember to click on the mapping and drag your cursor to OdiSendMail 2.
- Make sure to click on the white cursor from menu (above the Toolbox, to the left of the green arrows) and click Odi Send Mail 2 so the properties window populates with the mail server information. Press Save. Contact your company email or network admin to get the required smtp information. Pro-tip: For our demonstrations and tutorials we use mailtrap.io. It is a working dummy smtp testing server.
- Once completed your screen should look similar to the image below.
- Before we version the changes, we should test them. Execute the new package by right clicking on the newly modified package, in our tutorial it will be Target Data Load. Click OK and accept the defaults in the Run window.
WARNING: Make sure you are in the correct environment for testing and development. DO NOT run any package that will change or affect any real data. - Now check your execution under the Operator tab to make sure it was successfully executed.
- Now we will create a new version of the package that will be the latest version. We will repeat earlier steps, so return to the Designer Navigator > Projects window and click on the Target Data Load package. Right-click Target Data Load package and go to Version > Create Version. Note when the window appears you see the original version in the bottom box.
Leave the default name and change it to v2. Then for a description put 'Added successful execution for Target Data Load mappings OdiSendMail' and click ok.
You have now created 2 versions of your package: the original version and the modified version with the success email. Versioning is a key feature in ODI that really allows multiple developers to interact and work together to achieve the best results for data integration projects.
Special Note:
In this post, we reviewed how to use internal versioning in ODI. Rittman Mead always recommend to use an external configuration management systems (ex: GitHub) in ODI releases earlier than 12.2.1.2, rather than the internal versioning. In the next ODI patchset, there will be integration with Git for better work flow control. Subversion integration is currently available as of ODI 12.1.3.
Drivers Location In Odi 12c Tutorials 2016
If you are interested in seeing how to use Git in conjunction with older versions of ODI (prior to 12.2.1.2.6) stay tuned and check out an upcoming video here using Rittman Mead Principal Consultant Pete Tamsin's method for 'Using Git in an ODI Procedure'.
Huge thanks to Pete Tamsin and Michael Rainey for their help editing this post. No man, or woman, is an island!
Find me on:
Odi 12c Installation Steps
Related Videos: