Showing posts with label AIA. Show all posts
Showing posts with label AIA. Show all posts

Saturday, 6 April 2013

Lost password for AIA? How to recover password for AIA?


Lost password for AIA? How to recover password for AIA?

Lost password for AIA and want to recover it ? Below steps may help recover the password.


1. Create a file called password.xml with the following contents in the $HOME directory:

<?xml version="1.0" standalone="yes"?>
<DeploymentPlan component="FP" version="3.0"> <PreInstallScript> <echo message="fp.server.username ${fp.server.username}"></echo> <echo message="fp.server.password ${fp.server.password}"></echo> </PreInstallScript> </DeploymentPlan>


2. Set the AIA environment

   cd $AIA_INSTANCE/bin
   run the command . ./aiaenv.sh

3. Run the following command

 ant -f $AIA_HOME/Infrastructure/Install/AID/AIAInstallDriver.xml
-DPropertiesFile=$AIA_INSTANCE/config/AIAInstallProperties.xml
-DDeploymentPlan=$HOME/password.xml


Copy the content from screen to a file and then search for the word "fp.server.username" , after that keyword.. you will have the username right below it, you will find the password in plain text

      [echo] fp.server.username ohsadmin
      [echo] fp.server.password pa$$w0rd



Friday, 5 April 2013

Changing IP address in Weblogic servers in SOA / IPM / AventX environments


Changing IP address in Weblogic servers in Oracle SOA / IPM / AventX environments

It is a common practice to configure weblogic servers and their respective nodemangers to use IP addresses instead of hostnames.

While using IP addresses is common but always better to use hostnames on safe side.

There are instances when organizations decide to re-ip / change IP addresses of servers for some or the other project / business related decisions.

It is then a headache to change IP addresses in the respective configuration files.

Because if you end of changing the IP addresses on the hosts, weblogic server and nodemanager service will not start.

So how do we change IP address or rather configure hostnames in configuration files instead of IP address.

1) Changing IP address in nodemanager

- Go to "$MW_HOME/wlserver_10.3/common/nodemanager/nodemanager.properties" 
- Backup the file
- Replace old IP with new IP (or instead replace it with hostname to avoid doing this again in future!)
- Login to weblogic console -> Machines -> machine_name -> Nodemanager
- Replace old IP with new IP (or instead replace it with hostname to avoid doing this again in future!)
- Restart node manager


2) Remove old IP references from config.xml file

- Go to "$DOMAIN_HOME/config/config.xml"
- Backup the file
- Replace old IP with new IP (or instead replace it with hostname to avoid doing this again in future!)
- Repeat this step for config.xml located in aserver and mserver in case you have split your admin server and managed servers into different directories aserver and mserver.
- Restart MT services including admin server


Friday, 29 March 2013

AIAReadJMSNotificationProcess [1.0] in unknown state in SOA 11g EM Fusion Middleware Console


AIAReadJMSNotificationProcess [1.0] in unknown state in SOA 11g EM Fusion Middleware Console


Are you seeing AIAReadJMSNotificationProcess [1.0] composites in unknown states in your SOA enterprise manager console?


Errors as below:

<Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "AIAReadJMSNotificationProcess" failed: Error in getting XML input stream: http://soa.localhost.com:port/soa-infra/services/default/AIAErrorTaskAdministrationProcess/AIAErrorTaskAdministrationProcess.wsdl: Connection reset.>
====> CubeEngine load AIAErrorTaskAdministrationProcess/AIAErrorTaskAdministrationProcess took 476 ms


AIAReadJMSNotificationProcess appears in unknown state on SOA cluster nodes


Composite is in Failed state because it may not have got deployed when soa_server has been started. This may be because you have dependencies between your SOA Composites and AIAReadJMSNotificationProcess that has been deployed before AIAErrorTaskAdministrationProcess it depends on. 

For quick fix:

- restart soa_servers but it may happen again because deployment order of SOA Composites cannot be configured

or 

- redeploy AIAReadJMSNotificationProcess composite


For long term fix, follow:

Doc ID 1151973.1 Boot Order Of The Composites Upon Soa Suite Restart


Doc ID 1369101.1 SOA Server With AIA Unable to Look Up WSDL's At Startup

associated with bug: 12979076 - SOA11G MANAGED SERVER WITH AIA FAILS LOOKING UP WSDL AT STARTUP