Installation of ODI 12.2 on Centos 7.4 – Part 3 – ODI Repository and Standalone Agent Creation

Following previous posts:

Installation of ODI 12.2 on Centos 7.4 – Part 1 – Machine setup

Installation of ODI 12.2 on Centos 7.4 – Part 2 – ODI Installation

ODI Studio is ready but missing repositories and an agent.

Repositories creation

Go to your installation directory  + /oracle_common/bin and run rcu :

./rcu

image061
Next >

image063
We will provide dba user and perform all in once  (other options create scripts for dba to run).
Next >

image065
Fill your DB info  (First real test for our XE db).
Next >

Here, I got issue with connection, at first I got error :

Could not get JDBC Connection; nested exception is java.sql.SQLException: Unable to start the Universal Connection Pool: oracle.ucp.UniversalConnectionPoolException: Cannot get Connection from Datasource: java.sql.SQLException: ORA-00604: error occurred at recursive SQL level 1ORA-01882: timezone region not found

After some investigation it’s a driver incompatibility because XE is an oracle 11g.

I chose « an easy » solution. I edited the rcu script  (in /oracle_common/bin) and added following option to the commande line:

-Duser.timezone=CET

This solve the issue for rcu, but same issue will arise later with all the tools conecting to the repositories.
image067

After this was done, I got warned I used Oracle XE which is not certified…   …not an issue for my install test.
image069
Ignore >

image071
Why 6h on screenshot ?  (It was 4am and decided to take a nap before clicking Ignore)
OK

image072
Selecting the component as on screenshot  (Kept thE DEV prefix as this is just a install test); Added the master and work repo component.
Next>

image074
OK

image077
Chose a password for all oracle schema created (Will be 4 of them).

Select :

  • Odi SUPERVISOR password : maximum 12 characters
  • Type of install : Dev or Exploitation. (Exploit does not allow Studio connection)
  • The name of the work repo. I chose DEV_REPO, not to take all default values 🙂
  • Set the workrepo password : maximum 10 character
  • Encryption Algorithm

Warning FAILURE AES-256: At first I though : why AES-128 when proposing 256…  …so selected 256. But this lead afterward to repository creation to fails with an unsupported encryption algorithm. Its seems a configuration need to be adapted for AES-256 to work. I did not investigate further ans selected AES-128. Not bothering for my test.

Next >

image079
Summary of users and Tablespaces to be used.

Note that there is a 4th schema created and not listed : DEV_WLS_RUNTIME.

In addition it creates objects in the SYSTEM schema (you can find documentation about those info).
Next >

image081
A warning about tablespace creation.
OK

image083
A summary of your choices
Create

image085
Full sucess
Close

repositories are created, time to launch for the first time the studio and connect to the repository.

ODI Studio first connection

Go to /Oracle_Home/odi/studio in your odi directory.

Before running the odi.sh, I wanted to prevent the timezone issue I edited the config file (/Oracle_Home/odi/studio/bin.odi.conf) to add AddVMOption -Duser.timezone=CET
image087

./odi.sh

image088
image089
No previous install, I do not import anything.
No

image090
Here we are. We can connect to the repository

Create a new connection.
+

image092
OK

image093
Time to know if you noted everything down correctly.
Fill everything, select Work repository and click the magnifier. If db info are correct you will be prompted to select the available work repo.
image094
OK

image095
You can Test than click OK.

For info, my first test took some time. Some stuff needed seeding according to logs 😉
image096
image098
OK

image099
You are proposed to store your password in a wallet. You can chose that option and create a wallet.
I chose the unsecure path for this test.
OK
image100
OK

image0101
We are now connected.

Environement is nearly ready. We just need an agent to execute our packages.

This is done in two steps :

  • Creating agent in studio
  • Setup the « agent service »

Order is not supposed to be important but as I’m connected to the studio, I’ll start with it.

Creating Physical agent in Studio

Right clicks Agents and select New Agent
image102

image103
Chose a suiting name and fill host info.
Save

image105
It’s done.

Create WebLogic domain and Standalone Agent

Browse /oracle_common/common/bin and run config tool

Rem : I added once more the JVM option about timezone to the config_internal.sh file.

./config.sh

image106
We create a new domain and select location
Next >

image108
I want a standalone agent.
Next>

image110
I keep my effective jdk.
Next >

image112
Fill repository information.
Get RCU Configuration.
If successful, Next >

image114
Next>

image116
Checks should be successful
Next>

image118
Enter the Physical agent name you setup in studio
Next>

image120
Fill the Agent ip and supervisor password.
Next >

image122
Create the WebLogic NodeManager username and password
Next>

image124
Create

image126
Next>

image128
Finish

We can now start and test the agent

Start StandAlone Agent

Go to your Domain Location /bin

./agent.sh -NAME=Agent-dev-akabi-odi-centos7

Replace with your agent name.
image130

Now you can log to the studio, right click the agent and test it.

image132
Congratulation, ODI is now ready for you!

Note you still need to setup security and topology… …this will be for another night…

Do not hesitate to contact us for more info.

Advertisements

One thought on “Installation of ODI 12.2 on Centos 7.4 – Part 3 – ODI Repository and Standalone Agent Creation

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

w

Connecting to %s