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

Wednesday 18 July 2012

AIA Artifacts reference problem in JDeveloper using oramds

After finishing up with AIA 3.0 Installation when I starts building my component in JDeveloper on compilation I got errors which were pointing to my bpelprocess.wsdl and from there I come to know that one import is not proper which is actually pointing to AIA Artifact.

<wsdl:import namespace="http://schemas.oracle.com/bpel/extension"
              location="oramds/apps/AIAMetaData/AIAComponents/UtilityArtifacts/RuntimeFault.wsdl"/>

Solution

1.Check if the connection to MDS repositery is Created and if not then create a database connection to connect to the repository with either DEV_MDS or equivalent user.

2. Check if you have already created SOA-MDS connection (from resource palette) If not then create a new SOA-MDS connection. Make sure it uses the DB connection in step1 and also the partition is soa_infra. as by default its not soa_infra.

3. Now check for successful connection and installation of AIA Components by browsing AIAComponent files from MDS. These will be shown under /Apps/MetaData.

4. The last and very important step is to update adf-config.xml file in application home of your Jdeveloper(directory where .jws file exists). This will be used at design time to access files from MDS using oramds protocol. This is located in directory named %APPLICATION_HOME%/.adf/META-INF.
    
Add following line in adf-config.xml

      <metadata-namespaces>
          <namespace metadata-store-usage="mstore-usage_3" path="/apps" />
      </metadata-namespaces>

     <metadata-store-usage id="mstore-usage_3">
        <metadata-store class-name="oracle.mds.persistence.stores.db.DBMetadataStore">
         <property value="DEV_MDS" name="jdbc-userid" />
         <property value="welcome1" name="jdbc-password" />
         <property value="jdbc:oracle:thin:@hostname:port:sid" name="jdbc-url" />
         <property value="soa-infra" name="partition-name" />
     </metadata-store>
     </metadata-store-usage>

After updating file now you can recompile and this time you will surely end up with no errors.
You can now start accessing the artifacts like WSDLs, XSDs etc using oramds. 
eg:oramds/apps/AIAMetaData/AIAComponents/UtilityArtifacts/RuntimeFault.wsdl

Tuesday 29 May 2012

Step by Step Installation Guide for SOA 11g

Download all the software to get started.

  1. Oracle Database OracleXEUniv.exe
  2. WebLogic Server  wls1035_oepe111172_win32.exe
  3. Repository Creation Utility  ofm_rcu_win_11.1.1.5.0_disk1_1of1.zip
  4. SOA Suite  ofm_soa_generic_11.1.1.5.0_disk1_1of2.zip, ofm_soa_generic_11.1.1.5.0_disk1_2of2.zip
  5. OSB  ofm_osb_generic_11.1.1.5.0_disk1_1of1.zip

Oracle Database Setup


This is the first step towards Installation of SOA Suite.

For this you need to have anyone of following versions but I will be using Oracle XE Universal database version 10.2.0.1 as it is already installed on my machine  
                   i. Oracle XE Universal database version 10.2.0.1
                  ii. Oracle 10g database version 10.2.0.4+
                 iii. Oracle 11g database version 11.1.0.7+  


Note: You can not use any other database version in 11gR1 (certification of additional database is on the road map). Specifically, you cannot use XE Standard, It must be Universal.  


Note: When you are using XE, you will see a warning when you install the database schema that this database version is too old. You can safely Ignore this warning as it applies only to production environments.

Once you are done with Installation of Oracle XE, you must update database parameters.
Set the processes parameter to >=500 using the following instructions.
Login to sqlplus with sysdba and run following commands

sqlplus connect sys as sysdba
SQL> show parameter session
SQL> show parameter processes
SQL> alter system reset sessions scope=spfile sid='*';
SQL> alter system set processes=500 scope=spfile;
SQL> shutdown immediate
SQL> startup
SQL> show parameter session


SQL> show parameter processes

Schema Configuration 

Note: If you want to use Oracle XE as your database, you need to set the RCU_JDBC_TRIM_BLOCKS environment variable to TRUE *prior* to running RCU

1. To create the new schema, unzip ofm_rcu_win_11.1.1.5.0_disk1_1of1.zip navigate to rcuHome\bin and open a command window and run rcu.bat

2. The bat command returns to the prompt immediately and, after a few seconds, the Repository Creation Utility opens (if you just ran the utility to drop the schema, it opens the second time much more quickly).

3. On the Welcome screen, click on Next..
4. Select Create and click on Next.
5. Enter the database information.
6. Click on Next.
7. If you are using XE, you will see a warning at this point that this version is too old. You can safely ignore this warning as it applies only to production environments.

Monday 14 May 2012

Root cause of ServletException java.lang.AssertionError: CurrencyKey not preserved


After finishing up with the installation of AIA on SOA 11g when I access AIA home I was disappointed to see empty tabs of AIA including Project Life Cycle, CAVA, ect. When I check server log file I found following big error log.. which says....

Referer: http://localhost:7001/AIA/faces/oracle/apps/aia/home/ui/page/Home.jspx?_afrWindowMode=0&_afrLoop=8046694499161&_adf.ctrl-state=1b2migk5rh_9
Cookie: JSESSIONID=82k3PwvbRfLGCv3hGL5rK2sHQPJlzsWyBSmylvLLRptRhcmjS1T2!273321565; ADMINCONSOLESESSION=LMKjPwnCf10njbLYhNKwbPFGHX7cW2L94zgT7TC1jyYhJrJpyMyM!273321565
Content-Type: application/x-www-form-urlencoded
Content-Length: 263

]] Root cause of ServletException.
java.lang.AssertionError: CurrencyKey not preserved
    at org.apache.myfaces.trinidad.component.UIXCollection.encodeEnd(UIXCollection.java:540)
    at javax.faces.component.UIComponent.encodeAll(UIComponent.java:937)
    at org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:399)
    at oracle.adf.view.rich.render.RichRenderer.encodeChild(RichRenderer.java:2633)
    at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer.encodeCenterFacet(PanelStretchLayoutRenderer.java:769)
    at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer._encodeCenterPane(PanelStretchLayoutRenderer.java:1140)
    at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer._encodeMiddlePanes(PanelStretchLayoutRenderer.java:348)
    at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer.encodeAll(PanelStretchLayoutRenderer.java:313)
    at oracle.adf.view.rich.render.RichRenderer.encodeAll(RichRenderer.java:1396)
    at org.apache.myfaces.trinidad.render.CoreRenderer.encodeEnd(CoreRenderer.java:335)
    at org.apache.myfaces.trinidad.component.UIXComponentBase.encodeEnd(UIXComponentBase.java:767)
    at javax.faces.component.UIComponent.encodeAll(UIComponent.java:937)
    at org.apache.myfaces.trinidad.render.CoreRenderer.encodeChild(CoreRenderer.java:399)
    at oracle.adf.view.rich.render.RichRenderer.encodeChild(RichRenderer.java:2633)
    at oracle.adfinternal.view.faces.renderkit.rich.PanelStretchLayoutRenderer.encodeTopFacet(PanelStretchLayoutRenderer.java:781)

Solution
For this we need to update your Environment file which is available at following location
  
  <MiddlwareHome>/user_projects/domains/<Domainname>/bin/setSOADomainEnv.cmd  
                                                               OR
<MiddlwareHome>/user_projects/domains/<Domainname>/bin/setSOADomainEnv.sh 



set EXTRA_JAVA_PROPERTIES=%EXTRA_JAVA_PROPERTIES% -da:org.apache.myfaces.trinidad.component.UIXCollection
 
and restart the server... 
Now tabs will be successfully visible with no error