Google Plus invitations

I still have some left if anyone wants one:

http://tinyurl.com/3dmbz6k

New (5/2/11) OUAF SDK patch

I guess I should install this patch soon.

11896891  SDK 4.0.0.6 release for FW 4.0.2 and FW 4.1.0 based apps

Oracle Utilities Application Framework (OUAF) SDK 4.0.0.5 Install

Here are just a few notes to myself for any upcoming installs.
The first time I tried to install the SDK I run into many problems. Mainly not knowing the correct install steps.

Here was my first problem:
I run the clientSetup.exe and get to the location where the Appserver direcory is located and select it and get error of:
The directory does not contain a valid appserver installation. Choose
another directory or click CANCEL.


After searching for a long time I came up with this:
For development / SDK the application has to be install with Tomcat and in 'Exploded directory' format (Default: 'false' - only change to 'true' if installing on Tomcat.) We do not provide SDK documentation for other version than Windows/Tomcat .


But what does that mean ('Exploded directory' format ) ? Run the configenv command and change the Expanded directories to true.
Run the initialSetup.cmd to apply the changes.
I wish this could have been in the Install Guide.
This was by far not my only problem, I will continue this in a later post.





C:\ouaf\DEMO\bin>splenviron.cmd -e DEMO
Version ................ (OUAFVERSION) : 4.1.0
Database Type ............... (OUAFDB) : oracle
ORACLE_SID ............. (ORACLE_SID) : DEMO
NLS_LANG ................. (NLS_LANG) : AMERICAN_AMERICA.AL32UTF8
Environment Name ....... (SPLENVIRON) : DEMO
Environment Code Directory (SPLEBASE) : C:\ouaf\DEMO
App Output Dir - Logs ... (SPLOUTPUT) : C:\ouaf\sploutput\DEMO
Build Directory .......... (SPLBUILD) : C:\ouaf\DEMO\cobol\build
Runtime Directory .......... (SPLRUN) : C:\ouaf\DEMO\runtime
Cobol Copy Path ......... (SPLCOBCPY) :


C:\ouaf\DEMO\bin>configureEnv.cmd


**********************************
* Environment Configuration DEMO *
**********************************


 1. Environment Description
       Environment Description:                           DEMO env


 2. Business Application Server Configuration
       Business Server Host:                              MDM2008
       WebLogic Server Name:                              myserver
       Business Server Application Name:                  SPLService
       MPL Admin Port Number:                             6502
       MPL Automatic startup:                             false


 3. Web Application Server Configuration
       Web Server Host:                                   MDM2008
       Web Server Port Number:                            6500
       Web Context Root:                                  ouaf
       WebLogic JNDI User ID:                             sysuser
       WebLogic JNDI Password:                            ENC(BJWbp4JQs5VFnc9DHM1zoLp15wjn44JmfCMYHoNXUrE=)
       WebLogic Admin System User ID:                     {3DES}ip2hoc3F8k4=
       WebLogic Admin System Password:                    {3DES}gEa2D33Ly9O+cgXvZgy3Ug==
       WebLogic Server Name:                              myserver
       Web Server Application Name:                       SPLWeb
       Application Admin User ID:                         sysuser
       Application Admin Password:                        ENC(nKmtsqF60GbiM50OoQt1T2vuhZY89tIDrytnZ7RAaLE=)
       Expanded Directories:                              true
       Application Viewer Module:                         true

Initial install

**UPDATE**

This entry was for my first install. Meanwhile I installed many times over including other supporting apps. I will add new entries soon about those installs.

****************

After installing Oracle Utilities MDM 2.0 about 4 times I realized that is you make the smallest mistake with the environment variables, the whole install will be jacked up.


I also noticed it is not very good documented on which variables you should set and what to call them. If you use MDM_Installation_Guide_2_0_0.pdf you will notice it.

I will try to keep this updated as I run into more install problems. I am still fine tuning an install document I write to make my life easier later on.

It is sad that now I have to have a real powerful laptop in order to run MDM 2.0. Before I was able to install the EIP and everything was fine.