Wednesday
Jul182012

Own your Content

Blogging/Publishing Steps:

  1. Complete your blog, video, pictures and other content publish.
  2. Write a tease to your content for twitter, I use twitter since it is de-facto for the short summary.
  3. Link to your content that you own on your own property: Google+FacebookTwitter, Evernote, etc...

Read below to see why I choose these steps when it comes to publishing content.

After thinking for sometime about starting to record and share my thoughts with others I needed to make a choice on the medium. I have used Evernote to store my notes and instructions but this is more of a create and store with authorization. I still use it to keep my scrambled thoughts and quick notes.

I knew that I would be recording my technical steps and info when developing code and some technical ideas like this one.

So I considered Facebook, Google+, Twitter etc... but the one thing all these platforms have in common you do not own the data. I do not care how evil or not evil these services are now in the future maybe they loose your content maybe decide to change or alter it or use it for advertisement for some sex toy who knows the possibilities are endless.

So I decided to own my data by paying a small fee to host my own site which offers blog's and other out of the box services.

This is my day job but after the end of day the last thing I want to do is the samething I do for work. I would rather hack and develop on my pet projects instead of managing a website.

Tuesday
Jul172012

WebCenter Portal Restful Services Setup PS4 and PS5

 

Here is the original document from Oracle but I have added a little more steps to help clarify the setup.

Original Instructions

All of the REST APIs, except for the navigations REST API, require WebCenter Spaces. For information on the navigation REST API, see Section 13.3.2, "Using the Navigation REST APIs."

51.2.1 Introduction

Before you can use the WebCenter REST APIs, you must perform the server-side configurations described in this section. You must perform two separate configurations. You must configure an identity asserter and you must seed required entries in the credential store, which enables the REST security tokens to function properly.

Perform these configuration tasks when WebCenter Spaces is installed for the first time or if you otherwise know the configuration tasks have not been previously performed.

For more information on security tokens, see Section 51.9, "Security Considerations for WebCenter REST APIs."

Note:

This configuration is not required for the navigation REST APIs or for the CMIS REST APIs.

51.2.2 Configuring an Identity Asserter

First, you must configure an identity asserter before using the REST APIs. For detailed instructions, see "Configuring the REST Service" in the Oracle Fusion Middleware Administrator's Guide for Oracle WebCenter.

 

 Here the start use your own admin password do not change anything even the copied instructions use verbatium.

First do this to see it not working in a browser hit the url localhost:8888/rest/api/resourceIndex put in you userid:youruserid and password yourpassword

Now after all this you will see all the xml just follow the steps.

WebCenter Domain Keystore

  1. Go to JDK_HOME/jdk/bin 
  2. RUN THIS COMMAND: keytool -genkeypair -keyalg RSA -dname "cn=spaces,dc=example,dc=com" -alias orakey  -keypass welcome1 -keystore default-keystore.jks -storepass welcome1 -validity 1064
  3. RUN THIS COMMAND:keytool -exportcert -v -alias orakey -keystore default-keystore.jks -storepass password -rfc -file orakey.cer
  4. RUN THIS COMMAND keytool -importcert -alias webcenter_spaces_ws -file orakey.cer -keystore default-keystore.jks -storepass yourpassword
  5. Ensure that the default-keystore.jks keystore file is copied to the <DOMAIN_HOME>/config/fmwconfig directory, and then specify the location as ./default-keystore.jks.
  6. Open Fusion Middleware Control and log in to the WebCenter domain.
  7. In the Navigation pane, expand the WebLogic Domain node and click the WebCenter domain (wc_domain by default).
  8. From the WebLogic Domain menu, select Security -> Security Provider Configuration.
  9. Expand the Keystore section on the Security Provider Configuration page
  10. Click Configure


Description of "Figure 32-4 Keystore Configuration Page"

11. Use the following settings to specify the location of the keystore that contains the certificate and private key, and the signature key and encryption key aliases:

  1. Keystore Path: 
  2. Password
  3. Key Alias: orakey
  4. Signature Password
  5. Crypt Alias: orakey
  6. Crypt Password

12. Click OK to save your settings.

13. Restart the Administration server for the domain.

 

28.8.3 Configuring the WLS Trust Service Asserter

This section describes how to configure the WebLogic Server Trust Service asserter.

To configure the WebLogic Server Trust Service asserter:

The Create a New Authentication Provider page displays.

  1. Enter the Name of the new asserter (for example, TrustServiceIdAsserter).
  2. Select TrustServiceIdentityAsserter 

This asserter calls the Trust Service APIs to decode and validate the token from the incoming request, and pass the username to the WebLogic for establishing the asserted subject.

  1. REBOOT everything again

 

 

NOW RUN THESE wlst:

wlst.cmd in the ECM directory common/bin

connect(‘userid’,’password’, ‘localhost:7001’)

 

createCred(map="o.webcenter.jf.csf.map", key="keygen.algorithm",

    user="keygen.algorithm", password="AES")

 

THIS ONE told me it already exsisted after running it no harm no foul it worked

createCred(map="o.webcenter.jf.csf.map", key="cipher.transformation",

    user="cipher.transformation", password="AES/CBC/PKCS5Padding")

 

OK you are done lets test it out :-) 

 In a browser hit the url localhost:8888/rest/api/resourceIndex put in you userid:myuserid and password yourpassword when prompted by browser.

Try the RestConsole for chrome 

Saturday
Jul142012

BlackBerry can Survive

BlackBerry is known for their top notch set of business applications on a solid piece of hardware. What they do not have is an application Ecosystem. I think it was a little greed and little closeness of their Ecosystem that did not invite the developer community to write applications for them. Let's face it they had the market for a long time and for whatever reason was not able to capitalize on it. 

So BlackBerry here is the plan and yes you will need to concede and work within a flourishing open Ecosystem where unless you are original and keep innovating you will not survive. The plan would be to do what Amazon has done but with your phone and provide the same awesome user interface that the business has grown to love but underneath is android. This will allow you to partner with maybe Google or even amazon to host their application store or even better provide a curated application store for the business community! But you would stand behind the OS and your applications on your hardware to be secure and reliable like the past.

The only reason why I see this not working is pride on BlackBerry's part. Amazon has proven you can have successful branded version of android and be successful. The lawsuit crap between the super powers has finished so you will not be brought in to the courts. Let's face it too you would not have to spend as much on development from the ground up. Google is doing this you might want to have a team work on an addition and contribute back just like any other OS community.

Well people know I am a fan of android. one reason the OS community creates the best products just look at any big product company and under the hood there is OS everywhere.

There I said my peace to myself and if you want to read have at it.

Page 1 ... 1 2 3 4 5