Skip navigation.

Eric Rajkovic

Syndicate content
Web 2.0 experimentation and more...Eric Rajkovicnoreply@blogger.comBlogger116125
Updated: 2 hours 56 min ago

Test locally first, then deploy to the cloud.

Tue, 2015-01-06 22:12
As recommended by Cheuk Chau on Medium, I read 'How to Develop a Daily Writing Habit’ - I’ll try to put it in practice here with my second advise - should have been my #1 advise:
Run a local copy of your application first, before to test it on your cloud instance.
While it’s simple to run directly on the Cloud, and we have a lot of samples available to get started, working local first is the best way to get ready when trouble come your way.
Samples are available from:One challenge you will face : there are many ways to get code deployed - you need to find the best option for you and your organization. Here are a few :
  1. JDeveloper workspace, using build.
  2. ant build.xml (part of the SDK samples)
  3. maven pom.xml (part of the SDK samples)
  4. java cli (part of the SDK samples)
  5. the web console
The other step important is to check the output of the deployment and minimize the number of error and warning you see.
In one case, I started to look at some error I was seeing first in my Cloud instance, assuming it was a new issue. After a few trials, I finally run another test with my local setup and found that I was getting the same error. I made a mistake while editing some of the source code for my application and did not catch the error with local testing, which would have been cheaper for me.

For my next post, my advise is going to be of a different form - what you should not try. The do not advices are as valuable as the do advises - In some case. you have to learn from your mistakes, but sometime, it’s cheaper to leverage someone else mistakes.

Learning about the Oracle Cloud and the new Alta skin.

Wed, 2014-12-31 19:36
I had a conversation with +David Haimes on twitter the other day about blogging, and realized I have not been blogging for a long long time.

While I can find information about almost everything with Google or Stack Overflow, I realized that it's sometime hard to find the one piece of information which is relevant for you, in your current context.

It usually ends up being a compilation of multiple blog posts or answers; it's the curated content which brings most of the $$$ value.

As I go through the process to discover how to use the Oracle public cloud, I am going to blog about the learning process, here.

The first advise I'll share is this one:

For any sample you are using, start with Git
Here is why:

  1. Once you have a working version, commit and push to the remote.

    It give you the following benefits: easy to share with your peers - you have a backup for 'free' - in case the next set of changes break something in a bad way, rolling back is a breeze.
  2. Once you have a broken version, rollback is cheap - see above ;)
  3. Once you are happy with your work, it's ready for other to view and use

    You have no extra step required, and other may even find it valuable before you consider to be done with it. 
Here is my new GitHub account where I will start to follow the same rule in the coming days:
The specific blog post I wanted to reference today is this one:
It's a great post, and I do not need to replicate it's content here. 
Only issue I had was that jersey-bundle-1.9.war was not present on the distribution I used to deploy to my cloud instance - I was using JDeveloper and I could only find jersey-bundle- on my local wlserver_10.3\common\deployable-libraries folder.
The fix is also trivial - get a newer version and install it as documented in the blog post referenced above.

Today, the sample I'll love to see in a Git repository, so I can Scan the code to learn how it was built before I Commit to it and run the sample on my local instance - it's the Oracle Alta demo.

There is a new code sample available on OTN for Alta skin - source: (or It would have been nice to get it from (or some other repo).

As I am proof reading my billet, I realized that this is the second advise I would have love to get from someone more knowledgeable -my mentor- with the Oracle public cloud development model.

It's give me an easy follow-up post for next year.