Deploying ODICS Studio on a Windows Image (Compute Cloud Service)

Based on our experience, in the on-premise world, most ODI Developers are using ODI Studio on Windows. So, we thought detailing how to deploy ODICS on a Windows Image on Compute might be useful. This can be used to connect to an ODICS Repository that has already been installed.

PLEASE NOTE THAT THIS IS ONLY FOR STUDIO – USING AN AGENT ON COMPUTE AS AN IMPACT ON LICENSING

Get the Windows Image

It is now possible to deploy a Windows Server Image in Compute Cloud.

Although Linux images can be deployed out of the box from Compute Cloud Service, to get the Windows Image it is required to go to the Market Place and select the Microsoft Windows Server 2012 R2 Standard image.

ODI on Compute Windows Image 1

Once the image selected, it is required to have the Administrator privilege to be able to install it on your Compute Cloud Service

ODI on Compute Windows Image 2

The “administrator_password” is the password that will be used to access your Image once deployed – this is NOT your Oracle Cloud password. You can choose any password and then change it just before deploying your image in a next step. Do not worry to see it in clear text!

 

If you do not see the screen shown above, you have a problem linking the Market Place to you Oracle Cloud Account. In that case make sure you have checked the right preference for your Oracle Cloud Account:

ODI on Compute Windows Image 3

After clicking on Install you will get after a while:

ODI on Compute Windows Image 4

Once you have that nice picture it means you can select this image to create a Compute Instance.

Create the Compute Instance

Just follow the bellow screen shots

  • Select the correct image ( make sure you are in the Marketplace – you can do a search on Microsoft)

ODI on Compute Windows Image 5

  • Select the OCPU shape (based on your licensing – we have selected 4 for the example)

ODI on Compute Windows Image 6

  • Provide a name to the instance, select an SSH key and enable RDP – note the Administrator Password you will use to connect to your Windows Instance (it is recommended to change that password when accessing the Instance the first time as an Administrator)

ODI on Compute Windows Image 7The instance can be created

 

Access the Windows Instance using RDP

Follow the documentation: Accessing a Windows Instance Using RDP

Once you have followed the above steps to enable RDP access, you can connect to your instance using the Remote Desktop Client (select the IP of your Compute Instance) – connect as Administrator and change the password to make it secure.

ODI on Compute Windows Image 10

Finally … install ODI

Once you are connected to your Windows Image, just follow the standard steps to install ODI.

I recommend the following steps:

209.17.4.8 login.oracle.com
to host in C:\Windows\System32\drivers\etc

Create a link between DBCS and your Windows Image

We need to access a DBCS instance either to connect to an existing Repository or either to create one. In order to connect the Compute Instance with DBCS we need to create a Security rule:

Open the Compute Service Console and select the Network Tab. Click on Create Security IP List to start.

ODI on Compute Windows Image 11

  • Enter the IP of all hosts that you would like to give similar Network Security Settings. For this example it’s sufficient to use the Compute VM. Enter a description that describes the list.
  • ODI on Compute Windows Image 12Switch to the Security Rules tab and hit the “Create Security Rule” button.

 

ODI on Compute Windows Image 13

  • The application in this example will use port 1521 for the communication with the database, which is provisioned as part of the database provisioning for each instance with the name ora_dblistener. Select the Security IP List created above as the source and select the Database VM as the destination for this Security Rule.

ODI on Compute Windows Image 14

Creating this list will enable the communication between the VMs on Port 1521.

Connect ODI to the repository

You can chose to either connect to an existing one or create a new one

Conclusion

For more ODI best practices, tips, tricks, and guidance that the A-Team members gain from real-world experiences working with customers and partners, visit Oracle A-Team Chronicles for ODI.

Acknowledgements

Special thanks to David Allan, Oracle Data Integration Architect, for his help and support.

Add Your Comment