AIA 11.1.1.6.0 Installation on Windows 7




AIA 11.1.1.6.0 Installation

Install AIA 11.1.1.6.0 from scratch:

Undoubtedly, it was a little challenge while trying to install AIA 11.1.1.6.0. Firstly the long Installation guide and very generic error descriptions leave you nothing but perplexed, secondly, our OS being Windows 7 adds fuel to the fire. But, despite all the odds, what matters most is that AIA 11.1.1.1.6.0 runs successfully. However, just to save the time of world's greatest developers, I'm writing this document to give some of the tips and tricks that I found while installing in my machine.

Below are the steps that I followed to install AIA:

1. Install Oracle Database 11g (Express Edition).
  • Download the Oracle database installable as zip file and extract that file into a directory.
  • Run the setup file (Don’t forget to Run as administrator).
  • Proceed with the steps and after successful installation check the database console http://<host-name>:8080/apex/f?p=4950
2. Create schemas using the Repository Creation Utility (RCU 11.1.1.6.0).
  • While creating the schemas, give the same password for all the schemas. However, we can give different passwords as desired.
3. Install Weblogic server (10.3.6).
  • Download the server installable and installation guide and follow the guide to install the Weblogic Server.
4. Install Oracle SOA Suite (11.1.1.6.0).
  • Study the software and hardware requirements before installing and also gather the necessary supporting documents as Installation guide, Administration guides etc.
  •  Follow the installation guide and install the WLS. After installation do not wonder if you are not able to see the soa_server1 folder under <Middleware>/user_projects/domains directory. It will come when you start your managed server first time using the startManagedWeblogic soa_server1.
5.  Finally Installing the AIA 11.1.1.6.0.
  • Go through the Hardware-Software requirements carefully and download the AIA installable from Oracle e-delivery website. Also download the following supporting documents from Oracle Support.
6. Prerequisite configurations for AIA installation.

While following the installation guide and preparing for installation, pay attention to the steps mentioned below.
·          
      Configuring JVM Parameters

Instead of modifying the file setDomainEnv.cmd, make the change in the setSOADomainEnv.cmd as this file seems to override all the changes in the other domain files. Set the if condition as described.

If "%PROCESSOR_ARCHITECTURE%"=="AMD64"
(set USER_MEM_ARGS=%PORT_MEM_ARGS%)
else
(set USER_MEM_ARGS=-Xms1024m -Xmx1024m -XX:PermSize=512m XX:MaxPermSize=512m)

·         Enable Remote JDBC Connection in Weblogic Server

 Go to MiddlewareHome-UserProjects-Domains-YourDomain-Bin-SetDomainEnv.cmd. Then search for the string WLS_JDBC_REMOTE_ENABLED="-Dweblogic.jdbc.remoteEnabled”.
 
               Set it to “true”.

·    Setting up Time zone
  • Firstly verify the current time zone in the database from the sqlprompt(by running sqlplus.exe) and connect with SYS user, and using SELECT  SESSION TIMEZONE  FROM DUAL. Then you can set it to whatever you want using ALTER SESSION SET TIME_ZONE = ‘EST’. 
  • Don’t close this sql prompt window till AIA installation is complete as it is maintained only for a session. Specify the same time zone in the Weblogic managed server start too as given in the guide. 
  • Don’t specify any time zones like +5:30 to avoid any errors.
  • Now restart the Admin server and SOA servers.
·         Configuring and Verifying the node manager

Start your SOA server using the Node Manager before installation. Follow the below steps carefully. Before you can use the Node Manager utility, you need to configure/verify the Node Manager.
  
 First, configure your Node Manager
  • For this start the Admin Server as usual by running the <Middleware_home>\user_projects\domains\soa_domain\startWebLogic.cmd.
  • Go to Weblogic Console and navigate to Machines-->LocalMachine-->Configuration Tab-->Node Manager Tab. Specify the ListenAddress (where Node Manager will run) and ListenPort as per you installation. By default the port is 5556. Be sure to provide the exact URL/Host name in ListenAddress as localhost will disallow starting the servers from remote location. See below image.
                                         
  • Goto <Middleware_home>\wlserver_10.3\common\nodemanager\nodemanager.properties. Set StartScriptEnabled=true.
  • Start WLST from <Middleware_home>\wlserver_10.3\common\bin\wlst.cmd in a separate command prompt window. You can double click on the wlst.cmd also to start WLST.
  • Once WLST starts, connect to Admin Server from the WLST console. To connect type the connect() command on the WLST console and press Enter. Accept defaults or provide inputs as required. Once it connects successfully, the WLST prompt will change to wls:/mydomain/serverConfig>.
  • Now type nmEnroll ('<Middleware_home>/user_projects/domains/<domain_name>','<Middleware_home>/wlserver_10.3/common/nodemanager'). This command enrolls the current machine with the Node Manager and creates some properties file (nm_password.properties, SerializedSystemIni.dat).
  • If the message displays as "Successfully enrolled this machine with the domain directory at", Enrollment is successful. 
  • Exit from the WLST console using the exit() command and shut down your Admin Server and Close the Browser Console window.
 Secondly Verifying the node manager
  • After the Node Manager is properly configured, you can start the Node Manager by following the below mentioned steps.
  • Open a new command window and go to <Middleware_home>\wlserver_10.3\server\bin using cd command. Type startNodeManager and press Enter.
  • It starts your Node Manager and gives the output as shown in below image.   


  • To verify if the Node Manager is running successfully, start your Admin Server if it is not Running and go to Weblogic Server Console.
  • Navigate to Environment --> Machines --> LocalMachine --> Monitoring Tab --> Node Manager Status. It should display Reachable. See below image.

                                        
                                              Hence the Node Manager is running properly.

Once you verify and complete the above steps, I recommend, stop and close everything open till now. Then follow the following steps.
  1. Start your Node Manager using <Middleware_home>\wlserver_10.3\server\bin\startNodeManager.cmd command from the command prompt.
  2. Open a fresh command prompt window and run WLST.cmd from <Middleware_home>\wlserver_10.3\common\bin\WLST.cmd.
  3. Next task is to connect to the Node Manager using nmConnect (). In the WLST console window type nmConnect('weblogic','welcome1','neeraj-pc','5556','soa_domain').
  4. Once connected to Node Manager the command prompt will change.
  5. Now to start your Admin server type nmStart() e.g. nmStart('AdminServer')
  6. To start your managed server type nmStart() e.g. nmStart('soa_server1')
If it gives the success notification, you are done. Also, you can verify the same from the Weblogic Console. 

Press Read More Here.....


  • Check whether the Admin Sever and ,soa_server1 and Node Manager is running properly or not.
  • If not, start the Node Manager as I said above steps and also start the Admin  server and soa_server1 also by using Node Manager as the above steps.
  • Now go ahead with your AIA installation using the AIA Installer. While installation, at the time of Deployment Configuration step it will say sometimes as Failed due to Unable to reserve space in Heap. Click Retry. Close all open programs and make sure there is enough memory available as specified in the USER_MEM_ARGS. It should solve the error next time.
  •  AIA installation screens are as follows.








  
Now your system is ready with AIA 11.1.1..6.0

Verify the installation from the AIA Console http://<localhost>:8001/AIA


Thank you...
subhash chakka
subbu.3823@gmail.com

Comments

Post a Comment

Popular posts from this blog

Difference between Route, Service Callout, Publish

When you are first starting with OSB it can be a little tricky to determine when to use a Route, Service Callout or a Publish node.  All three can be used to call either a Business service or a local Proxy service.  You can use the following lists to determine which will best fit your needs. Route Last node in request processing.  It can be thought of as a bridge between request pipeline processing and the response pipeline processing. You can only execute one route in your Proxy Service. Can only be created in a route node. OSB will wait for the Route call to finish before continuing to process. If you are calling a Business service  and  you specify  Best Effort  for QoS (Quality of Service), then OSB will release the thread it is holding while the business service executes. If you are calling a Business service  and  you specify  Exactly Once  or  At Least Once  for QoS, then OSB will hold onto the thread while the business service executes. If you are calling a l
Read more

OSB actions in proxy service

Image
In this post we will see about different types of actions to message flows using the Oracle Service Bus Administration Console, such as route, publish, service callout, transport headers, conditional actions, error actions, and message transformation actions. Actions are the elements of pipeline stages, error handler stages, route nodes, and branch nodes that define how messages are to be defined as they flow through a pipeline            Action                           Description                     Dynamic Publish Publish a message to a service identified by an XQuery expression                          Publish Publish a message to a statically specified service.                        Publish Table Publish a message to zero or more statically specified services. Switch-style condition logic is used to determine at run time which services will be used for the publis
Read more

XQuery functions that supported by OSB

NAMESPACES ------------------------------------------------------------------------ xml=http://www.w3.org/XML/1998/namespace fn=http://www.w3.org/2004/07/xpath-functions op=http://www.w3.org/2004/07/xpath-operators err=http://www.w3.org/2004/07/xqt-errors fn-bea=http://www.bea.com/xquery/xquery-functions op-bea=http://www.bea.com/xquery/xquery-operators dt-bea=http://www.bea.com/xquery/xquery-datatypes var-bea=http://www.bea.com/xquery/xquery-variables xf-aug02=http://www.w3.org/2002/08/xquery-function op-aug02=http://www.w3.org/2002/08/xquery-operators xs=http://www.w3.org/2001/XMLSchema xsd=http://www.w3.org/2001/XMLSchema xdt=http://www.w3.org/2004/07/xpath-datatypes local=http://www.w3.org/2004/07/xquery-local-functions declare default function namespace "http://www.w3.org/2004/07/xpath-functions XQUERY FUNCTIONS ------------------------------------------------------------------------ fn:node-name($arg as node()?) as xs:QName? fn:
Read more