Main

Application Integration Architecture Archives

September 29, 2009

Move AIA Home from one location to another

By pavan.pvj on September 29, 2009 9:24 PM

More often, w face this issue when preparing the DEV/TEST instances. What if we install AIA in one of the directories and what we our mount point is out of space and we want to move this directory to another location?

1. The solution is very simple. The configuration for AIA home is referred only in one location i.e., opmn.xml file. This file is located in $ORACLE_HOME/opmn/conf directory, where ORACLE_HOME is the directory location where the SOA Suite is installed.

For the oc4j_soa container, the AIA home is mentioned in the module-data element as follows:

-Daia.home=/slot/ems1054/oracle/product/AIAHOME

So, if the AIA Home needs to be moved to a different location, this is one of the config files to be changed.

2. Then, in the $AIA_HOME/bin, change the locations of the directories in aiaenv.sh (aiaenv.cmd for Windows).

3. For some of the PIPs like Revenue Accounting, the AIA location is specified in the $AIA_HOME/config/AIAConfigurationProperties.xml file. So, change the locations in this file as well.

Thats it !!! Restart the SOA and everything is fine to go with new AIA Home.

Comments (0) | TrackBacks (0) AddThis Social Bookmark Button

Deploy using the deploy tool utility in AIA

By pavan.pvj on September 29, 2009 11:06 PM

One of the good utilities that can be used to deploy the BPEL/ESB is AIA deploy tool. In the BPEL and ESB projects that we create, we use the partner link locations, WSDLs and XSDs for a particular server. If we need to deploy these projects to a different server, then we need to change the locations of the WSDLs and XSDs everytime.

Instead of doing it manually, we can use AIA Deploy tool. This utility has a tokenizer which will tokenize and change the URLs accordingly in the entire project and generates the build.xml (incase of BPEL) and deploymentplan.xml (incase of ESB). We can then run the 'ant' tool to deploy our processes to the server.

The DeployTool is located in $AIA_HOME/util. Here are the steps to use it.

1. There is a file called Tokenizer.properties which we need to populate the process directory (directory of the BPEL/ESB project). Ensure the process directory has the read/write permissions. Update the Tokenizer.properties with the following properties:

a) home.dir1 -> enter the directory of the process to be deployed.
eg: home.dir1=/product/example/JMSAdapterServices/MySample

b) ESB_COPY_FOLDER =/product/AIA_HOME/util/DeployTool/EsbCopy

c) BPEL_COPY_PATH=product/AIA_HOME/util/DeployTool/BpelCopy

2. Run the command to deploy:
$ ant runesb -DTokenizerPropsFilePath=/product/AIA_HOME/util/DeployTool/Tokenizer.properties

$ ant runbpel -DTokenizerPropsFilePath=/product/AIA_HOME/util/DeployTool/Tokenizer.properties

Note: Deploy tool will only create the deployment plan for ESB. It does NOT deploy the process. Once the deployment plan is generated, goto the ESB directory and run the ant tool to deploy the process.

4. Goto $AIA_HOME/bin and source the AIA environment file - aiaenv.sh. This will source all the environment variables. Then run "ant" to deploy the process.

Comments (0) | TrackBacks (0) AddThis Social Bookmark Button

Search All Blogs

Google Search


Only search this blog

About Application Integration Architecture

This page contains an archive of all entries posted to Learn with Pavan in the Application Integration Architecture category. They are listed from oldest to newest.

General is the next category.

Many more can be found on the main index page or by looking through the archives.

Top Tags

RSS

Subscribe to this blog's feed
Creative Commons License
This weblog is licensed under a Creative Commons License.
Powered by
Movable Type and Oracle