• OracleXE112_Win64.zip
• run the setup.exe
• Click SQL Command Line window.
• Credentials :  connect / as sysdba
• GRANT DBA to system;
• GRANT sysdba to system;
• GRANT ALL ON dbms_aqadm TO system WITH GRANT OPTION;
• GRANT ALL ON dbms_aq TO system WITH GRANT OPTION;
• GRANT aq_user_role TO system;
• GRANT EXECUTE ON dbms_aqin to system WITH GRANT OPTION;
• GRANT EXECUTE ON dbms_aqjms to system WITH GRANT OPTION;
• If you want to create your own user and tables this is a good starting point
• CREATE USER ref_data IDENTIFIED BY Welcome01 DEFAULT TABLESPACE users;
• ALTER USER ref_data QUOTA UNLIMITED ON USERS;
• GRANT CREATE SESSION TO ref_data;
• GRANT CREATE TABLE TO ref_data;
• GRANT CREATE VIEW TO ref_data;
• GRANT CREATE ANY TRIGGER TO ref_data;
• GRANT CREATE ANY PROCEDURE TO ref_data;
• GRANT CREATE SEQUENCE TO ref_data;
• GRANT CREATE SYNONYM TO ref_data;

ORA-28002: the password will expire within 7 days

You may see this message when you login as user mwconfig using SQL Developer. In Oracle 11g the default password policy changed such that the passwords now expire every 180 days. For a development box this is a bit of a pain. It's possible to create a profile with a policy that should mean the password does not expire. Note: even after creating the new password policy it still seemed to be necessary to update mwconfig's password.

1. Login to the database as sysdba

2. Execute the following SQL commands:

   CREATE PROFILE VAGRANT_DEFAULT_PROFILE LIMIT SESSIONS_PER_USER UNLIMITED PASSWORD_REUSE_TIME UNLIMITED FAILED_LOGIN_ATTEMPTS UNLIMITED PASSWORD_LIFE_TIME UNLIMITED PASSWORD_REUSE_MAX UNLIMITED; ALTER USER mwconfig PROFILE VAGRANT_DEFAULT_PROFILE;  ALTER USER mwconfig IDENTIFIED BY Welcome01;

RCU Installation

Copy below installable available in shared directory into any location in your c:\ drive.

ofm_rcu_win_11.1.1.7.0_64_disk1_1of1.zip

Step 2)

Make sure we set this environment variable before we run the installation.

RCU_JDBC_TRIM_BLOCKS  =>  TRUE

Step 3) Unzip the rcu zip folder and open cmd and navigate to bin folder and execute rcu

open - > create - > db connection - > hostname : localhost, port :1521 , service name : XE username : sys, password : role sysdba

create a new prefix : Dev

select : Metadata service under AS common schema and SOA and BPM infrastructure

Weblogic Server 10.3.6 Installation Steps

Follow below steps for upgrading the Weblogic to use JDK 1.7 / higher versions of JDK.

Steps for updating the JDK version for Weblogic on Windows

1. First step is to install the desired JDK - here we are installing JDK 1.7
2. Download latest version of JDK 1.7 from Internet (http://www.oracle.com/technetwork/java/javase/downloads/jdk7-downloads-1880260.html) OR download from loading bay from '/app/caps/Middleware_Dev_Softwares/Java/64-bit/jdk-7u75-windows-x64.exe'
3. Install the JDK 1.7 follow the steps as prompted while installing.
4. After installing JDK its now time to update Weblogic to point to JDK 1.7. First Shutdown all managed servers in Weblogic domain including domain.
5. Backup the files:
   
           $MW_HOME/user_projects/domains/<domain_name>/bin/setDomainEnv.cmd
           $MW_HOME/wlserver_10.3/common/bin/commEnv.cmd
   
   For Example:
           copy $MW_HOME/user_projects/domains/<domain_name>/bin/setDomainEnv.cmd_before_jdk_changes
           copy $MW_HOME/common/bin/commEnv.cmd_before_jdk_changes

6. After taking the copy of the files than edit the 'setDomainEnv.cmd' file and find JAVA_HOME / SUN_JAVA_HOME and replace the path with new JAVA_HOME
   
   For Example:

           @REM is used for commenting the line. So in below I am commenting the existing JDK and adding the path to new JDK version.

           @REM set SUN_JAVA_HOME=C:\Program Files\Java\jdk1.6.0_11

           set SUN_JAVA_HOME=C:\Program Files\Java\jdk1.7.0_75

7. Save and close the file.
8. Now edit the commEnv.cmd file and similarly search for JAVA_HOME and update the JDK path.
   
   For Example:
           @ren is used for commenting the line. So in below I am commenting the existing JDK and adding the path to new JDK version.
   
           @rem set  JAVA_HOME=C:\Program Files\Java\jdk1.6.0_11
           set  JAVA_HOME=C:\Program Files\Java\jdk1.7.0_75
9. Start the AdminServer and check the logs now it should be pointed to new JDK; thats all you are done Weblogic is now pointed to new JDK. Test your services and see the behaviour.
   
   For Sample:
   
   ************************************************************
   *  To start WebLogic Server, use a username and   *
   *  password assigned to an admin-level user.  For   *
   *  server administration, use the WebLogic Server   *
   *  console at http:\\hostname:port\console                *
   ************************************************************
   starting weblogic with Java version:
   Listening for transport dt_socket at address: 8453
   java version "1.7.0_75"

Similarly follow below steps for updating on Linux:

1. Download the JDK Unix version depending on Unix server version compatible.
2. FTP the file to Unix server where you want to install or install from.
3. If it's a ZIP than unzip the file in a location:
   
   For Example:
               unzip jdk_1.7_75u.zip
   
   The above will extract a .bin file.
   
   
4. Change the permission of the file to run it.
   
   For Example:
               chmod 755 jdk_1.7_75u.bin
   
   
5. Run the .bin file:
   
   For Example:
               ./jdk_1.7_75u.bin
   
   
6. After installing JDK now update Weblogic to point to JDK 1.7 / latest JDK version. First Shutdown all managed servers in Weblogic domain including domain.
   
   
7. Backup the files:
           $MW_HOME/user_projects/domains/<domain_name>/bin/setDomainEnv.sh
           $MW_HOME/common/bin/commEnv.sh
   
   For Example:
           cp $MW_HOME/user_projects/domains/<domain_name>/bin/setDomainEnv.sh $MW_HOME/user_projects/domains/<domain_name>/bin/setDomainEnv.sh_before_jdk_changes
           cp $MW_HOME/common/bin/commEnv.sh $MW_HOME/common/bin/commEnv.sh_before_jdk_changes
   
   

8. After taking the backup of the files than edit the 'setDomainEnv.sh' file and find JAVA_HOME and replace the path with new JAVA_HOME

   For Example:

           # is used for commenting the lines in Unix.

           #JAVA_HOME="/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre"
           JAVA_HOME="/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64/jre"

9. Save and close the file.
   
   
10. Now edit the commEnv.sh file and similarly search for JAVA_HOME and update the JDK path.
    
    For Example:
            # is used for commenting the lines in Unix.
    
            # Set up JAVA HOME
            #JAVA_HOME="/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64"
            JAVA_HOME="/usr/lib/jvm/java-1.7.0-openjdk-1.7.0.0.x86_64"
    
    
11. Start the AdminServer and check the logs now it should be pointed to new JDK. Test your services and see the behaviour.
    

 Make sure below zip files are exploded before we start installation.These files are available in loading bay in the same location which is mentioned in index page.

ofm_soa_generic_11.1.1.7.0_disk1_1of1.zip
ofm_soa_generic_11.1.1.7.0_disk1_1of2.zip

OSB installation 

Run the setup.exe from the following location <osb_install_file_location>/Disk1/install/win64