4 Replies Latest reply: Dec 8, 2011 4:38 AM by 716121 RSS

    Projects and Resource Deployments Get un-deployed automatically every day.

    716121
      Hi,

      I am getting a strange problem with SOA Server, I don't know if it is AIA Foundation pack which is troubling me that's why I am posting this question on both the forums. I have to re-deploy the projects and even JNDI names every day as they automatically get un-deployed.

      Am I missing any settings or configurations? Or there is something wrong with the installation?

      Also, whenever I deploy my projects, I deploy on soa_server1, but I can see the projects in bam_server1 and admin_server1. Is it a serious issue? What do we need to change to avoid this?

      Thanks in Advance
      Sharat
        • 1. Re: Projects and Resource Deployments Get un-deployed automatically every day.
          780756
          Hi,

          Strange one..may be you can try re-configuring the domain again and check if you are facing. What do you see in the logs when this automatic undeployment happens..there should be sth in the logs.

          Regards,
          Rahul
          • 2. Re: Projects and Resource Deployments Get un-deployed automatically every day.
            776640
            The AIA 11gR1 installer restarts SOA Server using node manager. To allow this you need to make sure that "StartScriptEnabled" property in the nodemanager.properties file under $WEBLOGIC_HOME/common/nodemanager directory is set to true.If the above step is not performed, the JRF classes will not be available to the SOA Server upon re-start and all subsequent deployments would fail. In order to ensure the above step is performed appropriately, try to shut down and restart the server from the Weblogic AdminConsole.

            Reference -http://blogs.oracle.com/aia/2010/05/troubleshoot_your_node_manager_for_aia_foundation_pack_11gr1.html
            • 3. Re: Projects and Resource Deployments Get un-deployed automatically every day.
              716121
              Recently one of my colleague sent this to me:
              ==========================================
              Dependent SCA composites fail with "503: Service Unavailable for url" after server restart
              We often design composite applications that invoke other composite applications. A typical use case would be AIA artifacts where RequestorABCS calls EBS which in turn calls ProviderABCS.

              If these are not configured correctly then after restarting SOA server the one having dependency does not work any more. Basically issue is with the order in which SOA server re-deploys these composites. You may see the below error message in EM console

              The composite SalesOrderRequestorABCS (1.0) is not available. This could happen because either the composite has been undeployed or soa-infra has not yet loaded this composite.
              [JCABinding] [SalesOrderRequestorABCS/1.0]Unable to complete load due to: Error in getting XML input stream: http://hostname:port/soa-infra/services/default/SalesOrderEBS/SalesOrderEBS_ep?WSDL: Response: '503: Service Unavailable' for url

              The recommendations to avoid dependencies between composites are :

              1. In the composite.xml of the calling composite have the import refer to an abstract wsdl and
              not a concrete one to avoid loading issues.
              2. Make sure you refer to the MDS location for common XSDs, WSDLs and deployed composites.

              For example in case of RequestorABCS if you are having references to end point URL of EBS(obtained from EM console after deployment of EBS) then make sure you change that to oramds location for abstract WSDL.

              FROM
              ==========================================
              <import namespace="http://xmlns.oracle.com/EnterpriseServices/Core/SalesOrder/V2" location="http://hostname:port/soa-infra/services/default/SalesOrderEBS/SalesOrderEBS_ep?WSDL" importType="wsdl"/>
              <reference name="SalesOrderEBS" ui:wsdlLocation="http://hostname:port/soa-infra/services/default/SalesOrderEBS/SalesOrderEBS_ep?WSDL">
              <interface.wsdl interface="http://xmlns.oracle.com/EnterpriseServices/Core/SalesOrder/V2#wsdl.interface(SalesOrderEBS)"/>
              <binding.ws port="http://xmlns.oracle.com/EnterpriseServices/Core/SalesOrder/V2#wsdl.endpoint(SalesOrderEBS_ep/SalesOrderEBS_pt)" location="http://hostname:port/soa-infra/services/default/SalesOrderEBS/SalesOrderEBS_ep?WSDL"/>
              </reference>
              ==========================================
              TO
              ==========================================
                   <import namespace="http://xmlns.oracle.com/EnterpriseServices/Core/SalesOrder/V2" location="oramds:/apps/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Core/EBO/SalesOrder/V2/SalesOrderEBSV2.wsdl" importType="wsdl"/>
              <reference name="SalesOrderEBS" ui:wsdlLocation="oramds:/apps/AIAMetaData/AIAComponents/EnterpriseBusinessServiceLibrary/Core/EBO/SalesOrder/V2/SalesOrderEBSV2.wsdl">
              <interface.wsdl interface="http://xmlns.oracle.com/EnterpriseServices/Core/SalesOrder/V2#wsdl.interface(SalesOrderEBS)"/>
              <binding.ws port="http://xmlns.oracle.com/EnterpriseServices/Core/SalesOrder/V2#wsdl.endpoint(SalesOrderEBS_ep/SalesOrderEBS_pt)" location="http://hostname:port/soa-infra/services/default/SalesOrderEBS/SalesOrderEBS_ep?WSDL"/>
              </reference>
              ==========================================

              Similarily if you are referring to ProviderABCS from EBS composite.xml of EBS will look something as below
              ==========================================
                   <reference name="SalesOrderProviderABCS" ui:wsdlLocation="oramds:/deployed-composites/SalesOrderProviderABCS_rev1.0/SalesOrderProvABCSImpl.wsdl">
              ..
              ..

              ==========================================
              I tried above things but again I started facing another issue:

              Then, I created EBS through Mediator, ItemEBS

              Here I gave oramds path of the PABCS, oramds:/deployed-composites/QueryItemEbizProvABCSImpl_rev1.0/QueryItemEbizProvABCSImpl.wsdl
              But got following error: Error(12,61): Parse of component type files failed, check the adf-config.xml file : "Error at line 34 char 38: Malformed WS Binding port. Missing # between namespace URI and service/port names."

              I checked Line 34 in composite.xml and it contained following :
              ==========================================
              <reference name="QueryItemPABCS" ui:wsdlLocation="oramds:/deployed-composites/QueryItemEbizProvABCSImpl_rev1.0/QueryItemEbizProvABCSImpl.wsdl">
              <interface.wsdl interface="http://xmlns.oracle.com/ABCSImpl/Ebiz/Core/QueryItemEbizProvABCSImpl/V1.0#wsdl.interface(QueryItemEbizProvABCSImpl)"/>
              *<binding.ws port="" location=""/>*
              </reference>
              ==========================================
              I found following thread Re: AIA Service Constructor - End Point not being populated.

              And it says that
              ==========================================
              “Try giving the entire wsdllocation of the deployed composite rather than improting it from MDS--deployed composites. Because in MDS you will have the abstract wsdls only.

              During runtime, the reference has to be original wsdllocation.

              location="http://<soa-host>:<port>/soa-infra/services/default/CreateYYYYAdapterService/CreateYYYYProcess_ep?WSDL"

              Then your endpoint will automatically fixed in composite.xml. Try giving the wsdl path in Target service details in Service Constructor.

              Hope this works fine. If not i assume it to be a bug.

              Answer to second question, there is no need of uploading the composite to MDS. Its only the abstract wsdls will be loaded into MDS.”
              ==========================================
              This all has again confused me. What do you suggest?
              • 4. Re: Projects and Resource Deployments Get un-deployed automatically every day.
                716121
                Seeing my own post after a long time, I realize that I should answer this now as I am a little more comfortable with the approach. Earlier, I think the error used to come because of "Absolute endpoint Path" of the Target composites being used. If we avoid any type of absolute path in our soa composite for Reference WSDLs, XSDs or anything we can eradicate this problem. Only at the "binding location" the whole endpoint of the composite should be given. While development Jdeveloper and SOA give us the facility of MDS for "Designing purpose" but we have to give the binding location as the exact endpoint of the composite at the server.

                I hope this resolves the problem if anybody else has faced it in recent times.

                Thanks all for your suggestions :)