JAX-WS integration within OSGi

Greetings,
I'm trying to integrate a component wired together with a webservice call using the JAX-WS API. I'm utilizing JAX-WS request dispatcher to make the service call.
The service call is working as expected from my local eclipse (able to create the service object, place the dispatch call and receive the response back.)
The error that I'm getting in the CQ error log:
Caused by: org.apache.sling.api.SlingException: javax.servlet.ServletException: java.lang.LinkageError: loader constraint violation: when resolving method "javax.xml.ws.Service.create(Ljava/net/URL;Ljavax/xml/namespace/QName;)Ljavax/xml/ws/Serv ice;" the class loader (instance of org/apache/felix/framework/ModuleImpl$ModuleClassLoaderJava5) of the current class, com/mohegansun/website/api/services/facade/ServicesFacade, and the class loader (instance of <bootloader>) for resolved class, javax/xml/ws/Service, have different Class objects for the type javax/xml/namespace/QName used in the signature
The jdk used by my eclipse and CQ instance (local) are both same!
I removed the jaxws-api-2.2.8 and jaxws-rt-2.0EA3 jars from the jre/lib/ext folder, restarted my machine, hoping to get a different error/exception - It still fails with same error!
I'm banging my head against the wall as i write this!
Any help, much appreciated.
Thanks,
Sivaram

interesting behavior to note here is: I removed the jaxws jars from jre, after restarting and testing the call again on CQ, I get the same error. How's that logically possible? I'm just short of ideas here. Where does CQ look for those jars, if they are not in the underlying JRE? Looks to me like a classloader hell issue, but, i need ideas to explore further. Thanks much!

Similar Messages

  • Is eCATT a component integrated within SAP Solution Manger?

    Is eCATT (extended Computer Aided Test Tool) a component integrated within SAP Solution Manager? or Netweaver Solution Manager?
    OR
    Is eCATT automatically gets installed if we install Solution Manager?
    Further, does Solution Manager gets installed if we install SAP/Netweaver components or is it a stand alone component?
    Please let me know.
    Thanks & Regards.
    Sapster.
    Edited by: sapster on Feb 13, 2008 10:41 PM

    Dear Fr,
    I think you got confused with solman & eCATT ,this is a testing tool and has got no dependency upon solution manager.
    this a free testing tool used for testing SAP applications, it is based upon Web Application Server.
    Please follow the link,
    http://help.sap.com/saphelp_nw04/helpdata/en/1b/e81c3b84e65e7be10000000a11402f/frameset.htm
    You can link ECATT and QTP scripts,combination of both.
    In addtion you can execute them from solution manager itself.
    Whereas solution manager is used for managing your test plans and can organize all type of test cases which can be automatic like ecatt QTP etc or manual.
    follow my; blog to learn testing with solutin manager.
    https://weblogs.sdn.sap.com/cs/weblog/view/wlg/5181
    Please rewad points.

  • Is Application Migration Workshop integrated within free APEX workspace?

    Is Application Migration Workshop integrated within the free APEX workspace hosted by Oracle at.http://apex.oracle.com/pls/otn?
    I am trying to evaluate the "Oracle Application Express Application Migration Workshop" (to convert Access Applications into APEX Applications) and it would be nice to not have to create the extensive development environment which can be very time consuming.
    Thanks!

    Hello User.
    Please change your name from the default #'s to either your name or a nickname.
    From my understanding,
    No the APEX Migration workshop is not installed in the free Oracle demo apex public workspace environment.
    One of the Apex experts will be able to confirm this information.
    I've only used the tool in my own environment and I've never tried looking for it on the free oracle apex workspace.

  • Finding classes within OSGi bundles via the JNI?

    As an example, I have a class com.company.bundle.myJavaClass within the OSGi bundle com.company.bundle.MyClass.
    Within my C++ code, after starting the JNI and OSGi via the usual invocation (with com.company.bundle in the classpath), If I try the following within C++ code:
    jclass myclass = jniEnv->FindClass("com/company/bundle/MyClass/");the FindClass call returns null, because the JNI apparently could not find the bundle.
    However, if I set everything up such that once the JVM is loaded, OSGi creates an instance of MyClass which then calls the C++ library
    JNIEXPORT void JNICALL Java_com_company_bundle_MyClass_c_1SimpleCall (JNIEnv * jniEnv, jobject manager)
    jclass myclass = jniEnv->FindClass("com/company/bundle/MyClass");
    }myclass is successfully found and I can successfully invoke MyClass methods through the JNI. However, if I ever try to do this outside of the above JNICALL function, it will fail to find the class (regardless of whether or not the bundle is loaded or if an instance of class exists.) Keeping track of the jniEnv pointer returned by the JNICALL function doesn't help, either.
    How can I get my C++ code to always succesfully find MyClass?
    Any insight would be appreciated!
    Edited by: mmetzger on Aug 20, 2009 10:05 PM

    mmetzger wrote:
    Thanks, I appreciate the condescension. :)
    It turns out that the actual problem is that classes loaded by OSGi do not use the system class loader like "normal" Java classes do. So the JNI cannot load the class anymore than any other non-OSGi code could.
    [This page|http://blog.springsource.com/2009/01/19/exposing-the-boot-classpath-in-osgi/] Is a much better description of the issue than I could hope to write.
    Interesting but nothing in there nor in a brief google look suggested anything other than that a custom class loader was used.
    And one can certainly load classes in JNI via custom class loaders.
    If you attempt to load a class that is only available via custom class loader and do not use that loader then the class will fail to load.

  • Integration within SAP HR

    Hi Group,
    I wanted detailed Intergration within SAP HR.
    Can any body send to [email protected]
    Regs,
    Brahma

    Hi,
    i required Integration details within SAP HR:
    Example : Tranining and Event managent and Performance Apprisal, Recruintment and Training and event management . Etc.,
    Hope you clear my question?
    Thanks & Regs,
    Brahma

  • Problem using WebRowSetImpl within OSGI bundle.

    Hallo to everyone,
    I used to use standard WebRowSetImpl in my Java programs to pass data between application layers without problem. Now, I'm facing an issue using WebRowSetImpl in an OSGI module: I get a ClassNotFound Exception while trying to instantiate it. That sounds really strange because if I just run my bundle using java interpreter (as if it were a normal executable jar), I get no errors.
    May you help me, please ?
    Thanks you in advance.

    Use the brace notation."#{usr['user.user_name.label']}"

  • JQUERY integration within APEX

    Hi everybody and merry chrismas...
    I have a problem with jquery within apex. I looked for in previous posts but I can not achieve to make it works...
    I am running apex 3.2.1 on linux with apex listener.
    I want to refresh a report and I found that it was possible to do so using jQuery(...).trigger('apexrefresh'). So I tried to declare jquery...
    I downloaded jquery-1.8.3.js from http://jquery.com and uploaded both as static files in shared components with apex.
    Now I try to define the file in my javascript section like this :
    <script src="#APP_IMAGES#jquery-1.8.3.js" type="text/javascript"></script>
    <script type="text/javascript">
         // refresh of regions impacted by the change of PXX_ID_OPERATION item
         alert("#APP_IMAGES#jquery-1.8.3.min.js");
         alert(apex.jQuery().jquery);
    </script>
    But the javscript failed on the apex.jQuery().jquery instruction.
    What is my mistake ? I am certainly completely wrong but I did not find a clear tutorial on internet. Thank you in advance for help.
    Regards...

    >
    Please update your forum profile with a real handle instead of "975489".
    I have a problem with jquery within apex. I looked for in previous posts but I can not achieve to make it works...
    I am running apex 3.2.1 on linux with apex listener.
    I want to refresh a report and I found that it was possible to do so using jQuery(...).trigger('apexrefresh').Where did you find this?
    So I tried to declare jquery...
    I downloaded jquery-1.8.3.js from http://jquery.com and uploaded both as static files in shared components with apex.
    Now I try to define the file in my javascript section like this :
    <script src="#APP_IMAGES#jquery-1.8.3.js" type="text/javascript"></script>
    <script type="text/javascript">
         // refresh of regions impacted by the change of PXX_ID_OPERATION item
         alert("#APP_IMAGES#jquery-1.8.3.min.js");
         alert(apex.jQuery().jquery);
    </script>
    Always post code wrapped in tags<tt>\...\</tt> tags to preserve formatting and prevent it being mangled by the forum software.
    But the javscript failed on the apex.jQuery().jquery instruction.
    What is my mistake ? I am certainly completely wrong but I did not find a clear tutorial on internet. Thank you in advance for help.The <tt>apexrefresh</tt> event and <tt>apex</tt> namespaced jQuery are APEX 4.x features that are not available in 3.2&mdash;even if you add jQuery yourself.
    APEX 3.2 support expired in February 2012, so the first recommendation is to upgrade to the latest version (4.2) where reports can be refreshed declaratively using Dynamic Actions.

  • OHW RC integrated within application

    Hi,
    I have created a Help project referring to ohw-rcf-demo-thin. When I deploy this proj to Integrated Weblogic, it works fine.
    Now I created one more proj in same application. I created a new page with some link - Help.
    On click of this I want to call the helpset created in the Help proj I created earlier. Basically, I want to forward the request to OHWServlet.
    Can anyone please let me know the steps to acheive this/code if possible?
    Thanks...

    Bumping. I still haven't found a solution for this.

  • ERP integrator target applications greyed out

    Hi all,
    I'm configuring the ERP integrator within EMPA (to use with FDM later) but when registering target applications three of the four are greyed out.
    I have tried to delete and refresh them, re-deploy and so on but they stay greyed out.
    Can anyone tell me how to re-activate the target applications so i can select them again?
    Thanks,
    Marc

    Hi All,
    Did any of you had success in configuring FDM with ERPI. I am trying to configure FDM+ERPI for extracting data from Oracle Financials R12 and load it into an EPMA Planning application. When i go onto create a Metadata Rule and click on the Add Dimension button, the next page gives an error stating: There are no more dimensions remaining to be mapped under this application. and the dimension drop down in the target application area remains empty. Any idea why this happens? My Hyperion version is 11.1.1.3. I also downloaded and applied latest available patch of ERPI but no results.
    Thanks & Regards,
    Muhammad Jamshaid Nawaz

  • Xsl schema import from within a wsdl file

    I have a namespace conflict issue validating a bpel process.
    The message error is as follow:
    [bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:19:80: src-resolve.4.2: Error resolving component 'tns2:InvocationContext'. It was detected that 'tns2:InvocationContext' is in namespace 'http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns2:InvocationContext' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
    [bpelc] [Error] SMSSenderEnablerSEIWrapper.wsdl.2.wsdl:20:76: src-resolve.4.2: Error resolving component 'tns1:SMSMessageETO'. It was detected that 'tns1:SMSMessageETO' is in namespace 'http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI', but components from this namespace are not referenceable from schema document 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'. If this is the incorrect namespace, perhaps the prefix of 'tns1:SMSMessageETO' needs to be changed. If this is the correct namespace, then an appropriate 'import' tag should be added to 'file:/D:/home/guillaume/workspace/SMSMulticast2/services/SMSSenderEnablerSEIWrapper.wsdl.2.wsdl'.
    I've already seen this kind of error in other posts, but this was encountered with xsd files. In my case, I'm trying to use complexTypes defined in a schema, defined itself in a WSDL file. The needed file (SMSSenderEnablerSEI) is referenced in the bpel.xml file.
    // Here the BPEL file (SMSMulticast2.bpel)
    <pre>
    <!-- SMSMulticast2 BPEL Process [Generated by the Oracle BPEL Designer] -->
    <process name="SMSMulticast2" targetNamespace="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" suppressJoinFailure="yes" xmlns:tns="http://com.osa.mdsp.csp.ena.smms.smsmulti/V1.0" xmlns="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:bpelx="http://schemas.oracle.com/bpel/extension" xmlns:ora="http://schemas.oracle.com/xpath/extension" xmlns:nsxml0="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:bpws="http://schemas.xmlsoap.org/ws/2003/03/business-process/" xmlns:nsxml1="http://com.osa.mdsp.enabler.sei/PimEnabler:DirectService/2004/V1.0">
         <!-- ================================================================= -->
         <!-- PARTNERLINKS -->
         <!-- List of services participating in this BPEL process -->
         <!-- ================================================================= -->
         <partnerLinks>
              <!--
    The 'client' role represents the requester of this service. It is
    used for callback. The location and correlation information associated
    with the client role are automatically set using WS-Addressing.
    -->
              <partnerLink name="client" partnerLinkType="tns:SMSMulticast2" myRole="SMSMulticast2Provider"/>
              <partnerLink name="SMSEnabler" partnerLinkType="nsxml0:SMSSenderEnablerRemoteLink" partnerRole="SMSSenderEnablerRemoteProvider"/>
              <partnerLink name="PIMEnabler" partnerLinkType="nsxml1:PimDirectServiceEnablerSEIImplLink" partnerRole="PimDirectServiceEnablerSEIImplProvider"/>
         </partnerLinks>
         <!-- ================================================================= -->
         <!-- VARIABLES -->
         <!-- List of messages and XML documents used within this BPEL process -->
         <!-- ================================================================= -->
         <variables>
              <!-- Reference to the message passed as input during initiation -->
              <variable name="smsmultiRequest" messageType="tns:SMSMulticast2RequestMessage"/>
              <!-- Reference to the message that will be sent back to the
    requester during callback
    -->
              <variable name="smsmultiResponse" messageType="tns:SMSMulticast2ResponseMessage"/>
              <variable name="count" type="xsd:integer"/>
              <variable name="contactRequest" messageType="nsxml1:retrieveContactRequest"/>
              <variable name="smsRequest" messageType="nsxml0:sendSMSRequest"/>
              <variable name="smsResponse" messageType="nsxml0:sendSMSResponse"/>
              <variable name="contactResponse" messageType="nsxml1:addContactResponse"/>
         </variables>
         <!-- ================================================================= -->
         <!-- ORCHESTRATION LOGIC -->
         <!-- Set of activities coordinating the flow of messages across the -->
         <!-- services integrated within this business process -->
         <!-- ================================================================= -->
         <sequence name="main">
              <!-- Receive input from requestor.
    Note: This maps to operation defined in SMSMulticast2.wsdl
    -->
              <receive name="receiveInput" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiRequest" createInstance="yes"/>
              <!-- Asynchronous callback to the requester.
    Note: the callback location and correlation id is transparently handled
    using WS-addressing.
    -->
              <assign name="setProperties">
                   <copy>
                        <from expression="5"></from>
                        <to variable="count"/>
                   </copy>
                   <copy>
                        <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMSISDN"></from>
                        <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:senderAddress"/>
                   </copy>
                   <copy>
                        <from variable="smsmultiRequest" part="parameter" query="/tns:SMSMulticast2Request/tns:inputMessage"></from>
                        <to variable="smsRequest" part="parameters" query="/nsxml0:sendSMS/nsxml0:sms/nsxml0:content"/>
                   </copy>
              </assign>
              <while name="foreach" condition="bpws:getVariableData('count') &gt; 0"><sequence><invoke name="invoke-1" partnerLink="SMSEnabler" portType="nsxml0:SMSSenderEnablerRemote" operation="sendSMS" inputVariable="smsRequest" outputVariable="smsResponse"/>
                        <assign name="decrease"><copy>
                                  <from expression="bpws:getVariableData('count') - 1"></from>
                                  <to variable="count"/>
                             </copy>
                        </assign>
                   </sequence>
              </while>
              <!--invoke name="callbackClient" partnerLink="client" portType="tns:SMSMulticast2Callback" operation="onResult" inputVariable="output"/-->
              <reply name="sendResult" partnerLink="client" portType="tns:SMSMulticast2PT" operation="process" variable="smsmultiResponse"/>
         </sequence>
    </process>
    // Here the WSDL file: SMSSenderEnablerSEIWrapper.wsdl
    <?xml version="1.0" encoding="UTF-8"?>
    <wsdl:definitions
         name="SMSSenderEnablerSEI"
    targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
         xmlns="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
         xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
    xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema">
    <wsdl:types>
         <xsd:schema
              elementFormDefault="qualified"
              targetNamespace="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
              xmlns="http://www.w3.org/2001/XMLSchema"
              xmlns:tns="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
              <xsd:complexType name="InvocationContext">
              <xsd:sequence>
              <xsd:element
              maxOccurs="unbounded"
              name="properties"
              nillable="true"
              type="xsd:string"/>
              </xsd:sequence>
              </xsd:complexType>
              <xsd:complexType name="EnablerException">
              <xsd:sequence>
              <xsd:element name="errorMessage" nillable="true" type="xsd:string"/>
              <xsd:element name="errorCode" type="xsd:int"/>
              </xsd:sequence>
              </xsd:complexType>
              <xsd:element name="EnablerException" nillable="true" type="tns:EnablerException"/>
              </xsd:schema>
    <xsd:schema
    elementFormDefault="qualified"
    targetNamespace="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns="http://www.w3.org/2001/XMLSchema"
                   xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
    <xsd:element name="sendSMS">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sendSMSReturn" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotification">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    <xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotificationResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sendSMSWithNotificationReturn" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSToAlias">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    <xsd:element name="serviceId" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSToAliasResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="sendSMSToAliasReturn" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotificationToAlias">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element name="ctx" nillable="true" type="tns2:InvocationContext"/>
    <xsd:element name="sms" nillable="true" type="tns1:SMSMessageETO"/>
    <xsd:element name="serviceId" nillable="true" type="xsd:string"/>
    <xsd:element name="notificationURL" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    <xsd:element name="sendSMSWithNotificationToAliasResponse">
    <xsd:complexType>
    <xsd:sequence>
    <xsd:element
    name="sendSMSWithNotificationToAliasReturn"
    nillable="true"
    type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:element>
    </xsd:schema>
    <xsd:schema
    elementFormDefault="qualified"
    targetNamespace="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns="http://www.w3.org/2001/XMLSchema"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
                   xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI">
                   <xsd:complexType name="SMSMessageETO">
    <xsd:sequence>
    <xsd:element name="content" nillable="true" type="xsd:string"/>
    <xsd:element name="earliestDeliveryTime" nillable="true" type="xsd:dateTime"/>
    <xsd:element name="expiryDate" nillable="true" type="xsd:dateTime"/>
    <xsd:element name="priority" nillable="true" type="xsd:string"/>
    <xsd:element name="recipient" nillable="true" type="xsd:string"/>
    <xsd:element name="senderAddress" nillable="true" type="xsd:string"/>
    <xsd:element name="contentSentEncoding" nillable="true" type="xsd:string"/>
    <xsd:element name="smsContentSentInGsm7Bits" type="xsd:boolean"/>
    <xsd:element name="smsContentSentInUcs2" type="xsd:boolean"/>
    </xsd:sequence>
    </xsd:complexType>
    </xsd:schema>
    <xsd:schema
    elementFormDefault="qualified"
    targetNamespace="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns="http://www.w3.org/2001/XMLSchema"
    xmlns:apachesoap="http://xml.apache.org/xml-soap"
    xmlns:impl="http://com.osa.mdsp.enabler.sei/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:tns4="http://com.osa.mdsp.enabler.sei.exception/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns1="http://com.osa.mdsp.enabler.sei.eto/SMSEnabler/V1.0/SMSSenderSEI"
                   xmlns:tns2="http://com.osa.mdsp.enabler.ecf/SMSEnabler/V1.0/SMSSenderSEI"
    xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/">
    <xsd:complexType name="SMSException">
    <xsd:sequence>
    <xsd:element name="errorCode" type="xsd:int"/>
    <xsd:element name="message" nillable="true" type="xsd:string"/>
    </xsd:sequence>
    </xsd:complexType>
    <xsd:element name="SMSException" nillable="true" type="tns4:SMSException"/>
    </xsd:schema>
    </wsdl:types>
    <wsdl:message name="sendSMSRequest">
    <wsdl:part element="impl:sendSMS" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSToAliasResponse">
    <wsdl:part element="impl:sendSMSToAliasResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="EnablerException">
    <wsdl:part element="tns2:EnablerException" name="fault"/>
    </wsdl:message>
    <wsdl:message name="sendSMSToAliasRequest">
    <wsdl:part element="impl:sendSMSToAlias" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationToAliasRequest">
    <wsdl:part element="impl:sendSMSWithNotificationToAlias" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationToAliasResponse">
    <wsdl:part
    element="impl:sendSMSWithNotificationToAliasResponse"
    name="parameters"/>
    </wsdl:message>
    <wsdl:message name="SMSException">
    <wsdl:part element="tns4:SMSException" name="fault"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationResponse">
    <wsdl:part element="impl:sendSMSWithNotificationResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSWithNotificationRequest">
    <wsdl:part element="impl:sendSMSWithNotification" name="parameters"/>
    </wsdl:message>
    <wsdl:message name="sendSMSResponse">
    <wsdl:part element="impl:sendSMSResponse" name="parameters"/>
    </wsdl:message>
    <wsdl:portType name="SMSSenderEnablerRemote">
    <wsdl:operation name="sendSMS">
    <wsdl:input message="impl:sendSMSRequest" name="sendSMSRequest"/>
    <wsdl:output message="impl:sendSMSResponse" name="sendSMSResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotification">
    <wsdl:input
    message="impl:sendSMSWithNotificationRequest"
    name="sendSMSWithNotificationRequest"/>
    <wsdl:output
    message="impl:sendSMSWithNotificationResponse"
    name="sendSMSWithNotificationResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    <wsdl:operation name="sendSMSToAlias">
    <wsdl:input message="impl:sendSMSToAliasRequest" name="sendSMSToAliasRequest"/>
    <wsdl:output
    message="impl:sendSMSToAliasResponse"
    name="sendSMSToAliasResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotificationToAlias">
    <wsdl:input
    message="impl:sendSMSWithNotificationToAliasRequest"
    name="sendSMSWithNotificationToAliasRequest"/>
    <wsdl:output
    message="impl:sendSMSWithNotificationToAliasResponse"
    name="sendSMSWithNotificationToAliasResponse"/>
    <wsdl:fault message="impl:SMSException" name="SMSException"/>
    <wsdl:fault message="impl:EnablerException" name="EnablerException"/>
    </wsdl:operation>
    </wsdl:portType>
    <wsdl:binding
    name="SMSSenderEnablerRemoteSoapBinding"
    type="impl:SMSSenderEnablerRemote">
    <wsdlsoap:binding
    style="document"
    transport="http://schemas.xmlsoap.org/soap/http"/>
    <wsdl:operation name="sendSMS">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotification">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSWithNotificationRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSWithNotificationResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="sendSMSToAlias">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSToAliasRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSToAliasResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    <wsdl:operation name="sendSMSWithNotificationToAlias">
    <wsdlsoap:operation soapAction=""/>
    <wsdl:input name="sendSMSWithNotificationToAliasRequest">
    <wsdlsoap:body use="literal"/>
    </wsdl:input>
    <wsdl:output name="sendSMSWithNotificationToAliasResponse">
    <wsdlsoap:body use="literal"/>
    </wsdl:output>
    <wsdl:fault name="SMSException">
    <wsdlsoap:fault name="SMSException" use="literal"/>
    </wsdl:fault>
    <wsdl:fault name="EnablerException">
    <wsdlsoap:fault name="EnablerException" use="literal"/>
    </wsdl:fault>
    </wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="SMSSenderEnablerRemoteService">
    <wsdl:port
    binding="impl:SMSSenderEnablerRemoteSoapBinding"
    name="SMSSenderEnablerRemote">
    <wsdlsoap:address
    location="http://localhost:8888/Simulateur/services/SMSSenderEnablerRemote?wsdl"/>
    </wsdl:port>
    </wsdl:service>
    <plnk:partnerLinkType name="SMSSenderEnablerRemoteLink">
    <plnk:role name="SMSSenderEnablerRemoteProvider">
    <plnk:portType name="impl:SMSSenderEnablerRemote"/>
    </plnk:role>
    </plnk:partnerLinkType>
    </wsdl:definitions>
    Is that possible to reuse (in a BPEL file) schemas types defined in a wsdl file with Oracle PM? Could you give me a hint to solve this problem?
    Many Thanks
    Guillaume

    You need to use the XSLT before you do assignment to achieve this, to
    change the message to the correct namespace.
    Please refer to sample at
    "orabpel\samples\tutorials\114.XSLTTransformations" which talks about
    how to use XSLT transformation.
    And please refer to
    "orabpel\samples\tutorials\121.FileAdapter\ComplexStructure" sample
    especially "InvToPo.xslt" which talks about doing transformations
    between 2 structures pointing to different namespaces.

  • Business Catalyst IDX Integration

    I am creating a real estate website for a client that needs IDX integration within their website.
    For any that are unfamiliar with IDX, it is basically a way of integrating the MLS database (that is, the database of US homes for sale) into websites.
    The basic functionality I need is for registered users to be able to log in to a secure zone, select the homes they like, and log back in at a later date in order to view these homes again.
    I'll be speaking with the owners of IDX and MLS within the next few days and would like to know more about Business Catalyst's potential capabilities when integrating this kind of system within our website.
    Thanks,
    - Tyler

    Hi Tyler,
    I'm not aware of any current IDX known integration with BC. 
    However you might want to reach out to some of our custom solution implementors for possible suggestions if no luck here. 
    http://www.twoblokeswithapostie.com/ (Ask for Mario)
    http://bcgurus.com/
    http://simpleflame.com/
    Kind regards,
    -Sidney

  • Acrobat X integration with Sharepoint 2010 previous versions

    We noticed a weird issue today which I hope someone can help. Im not finding much on google.
    We have a document library with versioning enabled. When a user opens a PDF file they can view the most recent version, but when they attempt to look at a previous version thay get an error that says:
    "The URL you have provided cannot be reached. Please verify that the URL is correct and the network location is reachable."
    This only happens on older versions of a document.
    Older versions of acrobat can open these revisions without a problem.
    Also, if I disable the Adobe/SharePoint IE addon the files are accessible but that rules out the integration within SP.
    Thanks a ton!

    Hi,
    I was going to move this to a more appropriate forum but I'm not clear on where to try. Can you repost this under the Reader forum as well as on http://answers.acrobatusers.com/?
    thanks,
    Ben

  • App-v management server or SCCM 2012 integration?

    Hi,
    We are using App-V 5.0 integrated within SCCM 2012 for a while now but aren't happy with it.
    Hope was that in some update of sccm 2012 it would improve but it does not. That's why the idea arises to use the Ap-V management server again.
    Below a comparison of the two options, I was wondering what your opinion on this matter is.
    App-V via SCCM 2012:
    Pro:
    Full integration with SCCM 2012
    Contra:
    Dependency on SCCM 2012 client (when SCCM client doens’t work, App-V doesn’t work either)
    Slow responstimes before package arrives at user (SCCM needs to scan AD groups, SCCM client needs a policy refresh)
    App-V Management server:
    Pro:
    Deploy is also possible to computers as from App-V 5.0 management server
    http://virtualvibes.co.uk/enabling-computer-based-targeting-in-app-v-5-0/
    “the fact that we can now target machines instead of users when publishing packages”
    Fast respsonsetime: deploy & uninstall
    Automatic uninstall when user/computer isn’t member of AD group anymore
    Contra:
    Extra server needed
    Note: the migration from SCCM to the App-V Management server should be transparent, right? Unpublish existing packages via SCCM, publish via management server
    Please advise.
    J.
    Jan Hoedt
    Jan Hoedt

    How many data centres and sites are these RDS servers and desktops deployed across?
    If you read Rory's blog post, you'll get a sense of what the App-V Full Infrastructure's down sides are across multiple sites/DCs.
    Please remember to click "Mark as Answer" or "Vote as Helpful" on the post that answers your question (or click "Unmark as Answer" if a marked post does not actually
    answer your question). This can be beneficial to other community members reading the thread.
    This forum post is my own opinion and does not necessarily reflect the opinion or view of my employer, Microsoft, its employees, or other MVPs.
    Twitter:
    @stealthpuppy | Blog:
    stealthpuppy.com |
    The Definitive Guide to Delivering Microsoft Office with App-V

  • [Integration] Web Dynpro ABAP calling Flex in Popup (without Flash Islands)

    Hi,
    We do not intend to install Enhancement Package 1 in a near future.
    Nevertheless, we do have requirements where Flex should be integrated with Web Dynpro ABAP (Flex components embedded or 'attached' to Web Dynpro ABAP applications).
    I would like to open a popup showing a Flex component. Then, the user validates and the Web DYnpro ABAP application is resumed. All this integrated within EP 7.0.
    What, according to you, would be the most effective combination : 
    - Suspend / Resume plug
    - Server-side cookies
    - iFrame (although it is deprecated)
    Given what I have read so far, it seems encapsulating the .swf within a BSP application would be the best shot. Could it be possible to get rid of this 'additional layer' ?
    Thanks in advance.
    Best regards,
    Guillaume

    Web Dynpro ABAP
    Define a suspend and a resume plug.
    BSP
    Retrieve the parameters sent by WDA either by AUTO attributes or the following code
    CONSTANTS: c_resume_name          TYPE string  VALUE `sap-wd-resumeurl`.
    DATA: lt_tihttpnvp                TYPE tihttpnvp.
    FIELD-SYMBOLS: <fs_httpnvp>       LIKE LINE OF lt_tihttpnvp,
                   <fs_dept_magasin>  LIKE LINE OF t_dept_magasins.
    ** Lecture des paramètres envoyés (par le WD ABAP)
    CALL METHOD request->get_form_fields
      CHANGING
        fields = lt_tihttpnvp.
    READ TABLE lt_tihttpnvp ASSIGNING <fs_httpnvp> WITH KEY name = c_resume_name.
    IF sy-subrc = 0.
      e_url = <fs_httpnvp>-value.
    ENDIF.
    Flex
    To return to the Web DYnpro ABAP, call a Javascript function within the BSP using this kind of code :
    jsReturn = ExternalInterface.call("sendBackToSAP", selectedDepartmentsParam, orderParam);
    BSP
    First, to react to the user action in the Flex component, define a Javascript function in the
          function sendBackToSAP(departements, ordre) {
             fireServerEvent(departements, ordre);
             return("Done");
    To fire a server-event (in order for BSP to call the WDA resume plug), I use this declaration :
    <!--  Event used by the Javascript to trigger OnInputProcessing so as to create
                  the server-side cookie -->
           <bsp:htmlbEvent name= "fireServerEvent"
                           id  = "flexAction"
                           p1  = "departements"
                           p2  = "ordre"></bsp:htmlbEvent>
    Last, I simply call the URL that the WDA gives me first :
    navigation->goto_page( e_url ).
    If people are interested in a more detailed presentation, feel free to reply to this post, and I will write a blog about this. Nevertheless, it should become pretty obsolete with the Flash Islands release... 
    Edited by: Guillaume Garcia on Oct 11, 2008 11:13 AM

  • 3rd party storage: AoE/Coraid integration

    #### LONG POST 1/3 ####
    Hi,
    We are working on AoE/Coraid (3rd party storage driver) integration within Oracle VM 3.x, we think that will be of use for the community and we'll love to share our work.
    But we discovered some issues and hope to have some help via this forum.
    So, to let you know how far we are and the current issue we have :
    1/ Our AoE RPM package is done (using SDK 3.0.2, waiting for 3.0.3 to be release) :
    # uname -a
    Linux ovm1 2.6.32.21-41xen #1 SMP Fri Sep 9 00:47:51 EDT 2011 x86_64 x86_64 x86_64 GNU/Linux
    # rpm -qa | grep aoe
    aoe-6-78
    2/ Our AoE init script is activated on boot and work as expected :
    # aoe-version
    aoetools:     32
    installed aoe driver:     78
    running aoe driver:     78
    # aoe-stat
    e66.3 2000.398GB eth1 1024 up
    ** First issue SOLVED :
    But ovs-agent complain each time we try to discover a server using Oracle Manager (running version 3.0.3 in case it may have an impact?) :
    [2012-01-19 03:11:39 30488] DEBUG (OVSCommons:124) discover_server: ()
    [2012-01-19 03:11:39 30488] WARNING (host:443) cannot get core api version: [Errno 2] No such file or directory: '/usr/lib/python2.4/site-packages/version.properties'
    [2012-01-19 03:11:39 30488] DEBUG (OVSCommons:132) discover_server: call completed.
    [2012-01-19 03:11:40 30504] DEBUG (OVSCommons:124) discover_hardware: ()
    [2012-01-19 03:11:40 30504] ERROR (OVSCommons:143) catch_error: ERROR 0 @ 244 find_aoe_disks() Problems extracting AOE disk info
    Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py", line 178, in find_aoe_disks
    stdout_LIST, stderr_LIST, exitStatus, deltaTime = vi_utils.vi_exe_sync( vi_errorAndLog_obj, [ 'ata_id', '--export', aoe_devPath ], 10 )
    File "/usr/lib64/ovs-storage-utils/vi_utils/vi_process.py", line 615, in vi_exe_sync
    theChild     = VI_Process_OBJ( vi_errorAndLog_obj, False, args, relativeTimeoutInSecs, inputData_LIST )
    File "/usr/lib64/ovs-storage-utils/vi_utils/vi_process.py", line 106, in __init__
    ,     0 )                    # creationflags               :: Windows only CreateProcess flag
    File "/usr/lib64/python2.4/subprocess.py", line 550, in __init__
    errread, errwrite)
    File "/usr/lib64/python2.4/subprocess.py", line 1000, in executechild
    raise child_exception
    OSError: [Errno 2] No such file or directory
    Runtime errors occured [1]
    Traceback (most recent call last):
    File "/opt/ovs-agent-3.0/OVSCommons.py", line 141, in wrapper
    return func(*args)
    File "/opt/ovs-agent-3.0/OVSDiscoverHardware.py", line 81, in discover_hardware
    raise Exception(scsi_logmsg)
    Exception: ERROR 0 @ 244 find_aoe_disks() Problems extracting AOE disk info
    Traceback (most recent call last):
    File "/usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py", line 178, in find_aoe_disks
    stdout_LIST, stderr_LIST, exitStatus, deltaTime = vi_utils.vi_exe_sync( vi_errorAndLog_obj, [ 'ata_id', '--export', aoe_devPath ], 10 )
    File "/usr/lib64/ovs-storage-utils/vi_utils/vi_process.py", line 615, in vi_exe_sync
    theChild     = VI_Process_OBJ( vi_errorAndLog_obj, False, args, relativeTimeoutInSecs, inputData_LIST )
    File "/usr/lib64/ovs-storage-utils/vi_utils/vi_process.py", line 106, in __init__
    ,     0 )                    # creationflags               :: Windows only CreateProcess flag
    File "/usr/lib64/python2.4/subprocess.py", line 550, in __init__
    errread, errwrite)
    File "/usr/lib64/python2.4/subprocess.py", line 1000, in executechild
    raise child_exception
    OSError: [Errno 2] No such file or directory
    Runtime errors occured [1]
    We just discovered the st_ATAoverEthernet.py but it look like it is not able to see the available AoE LUNs.
    Is the script author (Mr Joshua Nicholas) working for Oracle ???
    We just fixed the issue above in file /usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py :
    the subprocess call the "ata_id" but this program isn't in PATH !
    To test, we did this patch :
    diff -upr /usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py.orig /usr/lib64/ovs-storage-utils/storage_tech/st_ATAoverEthernet.py
    # diff -upr st_ATAoverEthernet.py.orig st_ATAoverEthernet.py
    --- st_ATAoverEthernet.py.orig 2012-01-19 16:23:04.000000000 +0100
    +++ st_ATAoverEthernet.py 2012-01-19 11:30:45.000000000 +0100
    @@ -175,7 +175,7 @@ def find_aoe_disks( vi_errorAndLog_obj,
    aoe_disk_interface = aoe_stat_line_components[2]
    aoe_disk_interface_status = aoe_stat_line_components[4]
    - stdout_LIST, stderr_LIST, exitStatus, deltaTime = vi_utils.vi_exe_sync( vi_errorAndLog_obj, [ 'ata_id', '--export', aoe_devPath ], 10 )
    + stdout_LIST, stderr_LIST, exitStatus, deltaTime = vi_utils.vi_exe_sync( vi_errorAndLog_obj, [ '/lib/udev/ata_id', '--export', aoe_devPath ], 10 )
    serial_cmpldRegEx = re.compile( '^ID_SERIAL=\s*' )
    rev_cmpldRegEx = re.compile( '^ID_REVISION=\s*' )
    It works, so finaly, we rollback to the last version of st_ATAoverEthernet.py and just (re)created the symlink : /sbin/ata_id -> /lib/udev/ata_id
    No more error messages in /var/log/ovs-agent.log as you can see :
    [2012-01-19 16:27:05 2607] DEBUG (OVSCommons:124) discover_server: ()
    [2012-01-19 16:27:05 2607] WARNING (host:443) cannot get core api version: [Errno 2] No such file or directory: '/usr/lib/python2.4/site-packages/version.properties'
    [2012-01-19 16:27:05 2607] DEBUG (OVSCommons:132) discover_server: call completed.
    [2012-01-19 16:27:06 2623] DEBUG (OVSCommons:124) discover_hardware: ()
    [2012-01-19 16:27:06 2623] DEBUG (OVSCommons:132) discover_hardware: call completed.
    [2012-01-19 16:27:07 2672] DEBUG (OVSCommons:124) discover_network: ()
    [2012-01-19 16:27:07 2672] DEBUG (OVSCommons:132) discover_network: call completed.
    [2012-01-19 16:27:08 2673] DEBUG (OVSCommons:124) discover_storage_plugins: ()
    [2012-01-19 16:27:08 2673] DEBUG (OVSCommons:132) discover_storage_plugins: call completed.
    [2012-01-19 16:27:08 2674] DEBUG (OVSCommons:124) discover_physical_luns: ('',)
    [2012-01-19 16:27:08 2674] DEBUG (OVSCommons:132) discover_physical_luns: call completed.
    1/2 CONTINUE ON THE SECOND POST
    Edited by: 904919 on Jan 19, 2012 7:04 PM

    3/3 END OF THE POST
    Write Methods Invoked
    Class=InternalJobDbImpl vessel_id=6511 method=addTransactionIdentifier accessLevel=6
    Class=DiscoverManagerDbImpl vessel_id=165 method=discoverServer accessLevel=6
    Class=InternalJobDbImpl vessel_id=6511 method=setCompletedStep accessLevel=6
    Class=InternalJobDbImpl vessel_id=6511 method=setAssociatedHandles accessLevel=6
    Class=InternalJobDbImpl vessel_id=6511 method=setContext accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setName accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setFoundryContext accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=onPersistableCreate accessLevel=6
    Class=HashMapDbImpl vessel_id=6528 method=remove accessLevel=6
    Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=setName accessLevel=6
    Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=setFoundryContext accessLevel=6
    Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=onPersistableCreate accessLevel=6
    Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=setLifecycleState accessLevel=6
    Class=LocalStorageInitiatorDbImpl vessel_id=6529 method=setRollbackLifecycleState accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setName accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setFoundryContext accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=onPersistableCreate accessLevel=6
    Class=PortDownEventDbImpl vessel_id=6541 method=notify accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setLifecycleState accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setRollbackLifecycleState accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setNumber accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setServer accessLevel=6
    Class=RootStatisticLogDbImpl vessel_id=117 method=createStatisticSubjectLog accessLevel=6
    Class=StatisticSubjectLogDbImpl vessel_id=6542 method=setStatisticSubject accessLevel=6
    Class=StatisticSubjectLogDbImpl vessel_id=6542 method=createAllStatisticTypeLogs accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6544 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6546 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6548 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6550 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6552 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6554 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6556 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6558 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6560 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6562 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6564 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6566 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6568 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6570 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6572 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6574 method=setType accessLevel=6
    Class=StatisticTypeLogDbImpl vessel_id=6576 method=setType accessLevel=6
    Class=ServerStoppedEventDbImpl vessel_id=6578 method=notify accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setRollbackLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setType accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setEncodedAgentPassword accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setManagementInternetProtocolAddress accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setAgentVersion accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setBootGeneration accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setRpmVersion accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setOvmVersion accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setHostKernelRelease accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setHostKernelVersion accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setHostname accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setManagerUuid accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setPythonBindingVersion accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createHypervisor accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setName accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setFoundryContext accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=onPersistableCreate accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setLifecycleState accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setRollbackLifecycleState accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setServer accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setCompiler accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setCompiledBy accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setCompileDomain accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setCompiledDate accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=setVersion accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=clearCapabilities accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
    Class=XenHypervisorDbImpl vessel_id=6581 method=addCapability accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=removeAllNtpServers accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=addNtpServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=addNtpServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=addNtpServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setStatisticInterval accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=lock accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setProductName accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setManufacturer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setProductSerialNumber accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setSimpleName accessLevel=6
    Class=InternalPortDbImpl vessel_id=6535 method=setSimpleName accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setMemory accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setProcessorSpeed accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNoExecuteFlag accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNumberOfThreadsPerCore accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNumberOfProcessorSockets accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNumberOfCoresPerProcessorSocket accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNumberOfProcessorCores accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNumberOfEnabledProcessorCores accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setNumberOfPopulatedProcessorSockets accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createProcessor accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setFoundryContext accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=onPersistableCreate accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setLifecycleState accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setRollbackLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createProcessor accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setFoundryContext accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=onPersistableCreate accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setLifecycleState accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setRollbackLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createProcessor accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setFoundryContext accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=onPersistableCreate accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setLifecycleState accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setRollbackLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createProcessor accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setFoundryContext accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=onPersistableCreate accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setLifecycleState accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setRollbackLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setBIOSReleaseDate accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setBIOSVendor accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setBIOSVersion accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setManufacturer accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setLevelOneCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setLevelTwoCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setLevelThreeCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setManufacturer accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setLevelOneCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setLevelTwoCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setLevelThreeCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setManufacturer accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setLevelOneCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setLevelTwoCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setLevelThreeCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setManufacturer accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setLevelOneCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setLevelTwoCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setLevelThreeCacheSize accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setFlags accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setModelName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setVendorId accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setCpuFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6587 method=setCpuModel accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setFlags accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setModelName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setVendorId accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setCpuFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6593 method=setCpuModel accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setFlags accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setModelName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setVendorId accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setCpuFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6598 method=setCpuModel accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setFlags accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setModelName accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setVendorId accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setCpuFamily accessLevel=6
    Class=ProcessorDbImpl vessel_id=6603 method=setCpuModel accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setName accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setFoundryContext accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=onPersistableCreate accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setLifecycleState accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setRollbackLifecycleState accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=setSimpleName accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=addServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setCpuCompatibilityGroup accessLevel=6
    Class=CpuCompatibilityGroupDbImpl vessel_id=6608 method=addServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createStorageInitiator accessLevel=6
    Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=setName accessLevel=6
    Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=setFoundryContext accessLevel=6
    Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=onPersistableCreate accessLevel=6
    Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=setLifecycleState accessLevel=6
    Class=IscsiStorageInitiatorDbImpl vessel_id=6613 method=setRollbackLifecycleState accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=lock accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createNetworkPort accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setName accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setFoundryContext accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=onPersistableCreate accessLevel=6
    Class=PortDownEventDbImpl vessel_id=6625 method=notify accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setLifecycleState accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setRollbackLifecycleState accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setSimpleName accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setNumber accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setServer accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setInterfaceName accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setMediaAccessControlAddress accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setMediaTransferUnit accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setDetails accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createNetworkPort accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setName accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setFoundryContext accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=onPersistableCreate accessLevel=6
    Class=PortDownEventDbImpl vessel_id=6632 method=notify accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setLifecycleState accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setRollbackLifecycleState accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setSimpleName accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setNumber accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setServer accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setInterfaceName accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setMediaAccessControlAddress accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setMediaTransferUnit accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6627 method=setDetails accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createNetworkPort accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setName accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setFoundryContext accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=onPersistableCreate accessLevel=6
    Class=PortDownEventDbImpl vessel_id=6641 method=notify accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setLifecycleState accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setRollbackLifecycleState accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setSimpleName accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setNumber accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setServer accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=addJobOperation accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setInterfaceName accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setInternetProtocolAddress accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setNetmask accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setAddressType accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=addEthernetPort accessLevel=6
    Class=EthernetPortDbImpl vessel_id=6619 method=setBondPort accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setMediaAccessControlAddress accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=setManagementMediaAccessControlAddress accessLevel=6
    Class=EthernetNetworkDbImpl vessel_id=2837 method=addNetworkPort accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setNetworkPortGroup accessLevel=6
    Class=BondPortDbImpl vessel_id=6634 method=setJobAsset accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=lock accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=addPlugin accessLevel=6
    Class=FileSystemPluginDbImpl vessel_id=2878 method=addServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=addPlugin accessLevel=6
    Class=StorageArrayPluginDbImpl vessel_id=2843 method=addServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=addPlugin accessLevel=6
    Class=FileSystemPluginDbImpl vessel_id=2872 method=addServer accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createLocalFileServer accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setName accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setFoundryContext accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=onPersistableCreate accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setLifecycleState accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setRollbackLifecycleState accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setStoragePlugin accessLevel=6
    Class=FileSystemPluginDbImpl vessel_id=2878 method=addStorageServer accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setAdminHostname accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setAdminUsername accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setAdminPassword accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setSimpleName accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setServer accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setSimpleName accessLevel=6
    Class=LocalFileServerDbImpl vessel_id=6644 method=setValidated accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=lock accessLevel=6
    Class=ServerDbImpl vessel_id=6521 method=createLocalStorageArray accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setName accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setFoundryContext accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=onPersistableCreate accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setLifecycleState accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setRollbackLifecycleState accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setStoragePlugin accessLevel=6
    Class=StorageArrayPluginDbImpl vessel_id=2843 method=addStorageServer accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setValidated accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=setSimpleName accessLevel=6
    Class=LocalStorageArrayDbImpl vessel_id=6649 method=createVolumeGroup accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=setName accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=setFoundryContext accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=onPersistableCreate accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=setLifecycleState accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=setRollbackLifecycleState accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=setStorageArray accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=6655 method=setSimpleName accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setName accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setFoundryContext accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=onPersistableCreate accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setLifecycleState accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setRollbackLifecycleState accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setPage83Id accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setVolumeGroup accessLevel=6
    Class=VolumeGroupDbImpl vessel_id=2856 method=addStorageElement accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setVendor accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setUserFriendlyName accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setSimpleName accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setSize accessLevel=6
    Class=StorageElementDbImpl vessel_id=6660 method=setStorageElementType accessLevel=6
    Class=InternalJobDbImpl vessel_id=6511 method=setFailedOperation accessLevel=6
    Class=DiscoverManagerDbImpl vessel_id=165 method=nextJobOperation accessLevel=6
    Completed Step: ROLLBACK
    Job failed commit (internal) due to OVMAPI_6055E Discover target: ovm1, Discover failed with error: java.lang.NullPointerException
    at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.sanAddMissingStoragePath(ServerPhysicalLunDiscoverHandler.java:371)
    at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.sanDiskProcess(ServerPhysicalLunDiscoverHandler.java:243)
    at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.process(ServerPhysicalLunDiscoverHandler.java:195)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:55)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:442)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:427)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:412)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:381)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:360)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:272)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:193)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:264)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1090)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:247)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:207)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Thu Jan 19 16:35:04 CET 2012
    com.oracle.ovm.mgr.api.exception.FailedOperationException: OVMAPI_6055E Discover target: ovm1, Discover failed with error: java.lang.NullPointerException
    at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.sanAddMissingStoragePath(ServerPhysicalLunDiscoverHandler.java:371)
    at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.sanDiskProcess(ServerPhysicalLunDiscoverHandler.java:243)
    at com.oracle.ovm.mgr.discover.ovm.ServerPhysicalLunDiscoverHandler.process(ServerPhysicalLunDiscoverHandler.java:195)
    at com.oracle.ovm.mgr.discover.ovm.DiscoverHandler.execute(DiscoverHandler.java:55)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:442)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:427)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:412)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:381)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:360)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:272)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:193)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:264)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1090)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:247)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:207)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    Thu Jan 19 16:35:04 CET 2012
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:457)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:427)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDiscover(DiscoverEngine.java:412)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.handleDefaultDiscover(DiscoverEngine.java:381)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverNewServer(DiscoverEngine.java:360)
    at com.oracle.ovm.mgr.discover.DiscoverEngine.discoverServer(DiscoverEngine.java:272)
    at com.oracle.ovm.mgr.op.manager.DiscoverManagerServerDiscover.action(DiscoverManagerServerDiscover.java:48)
    at com.oracle.ovm.mgr.api.job.JobEngine.operationActioner(JobEngine.java:193)
    at com.oracle.ovm.mgr.api.job.JobEngine.objectActioner(JobEngine.java:264)
    at com.oracle.ovm.mgr.api.job.InternalJobDbImpl.objectCommitter(InternalJobDbImpl.java:1090)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:247)
    at com.oracle.odof.core.AbstractVessel.invokeMethod(AbstractVessel.java:207)
    at com.oracle.odof.core.BasicWork.invokeMethod(BasicWork.java:136)
    at com.oracle.odof.command.InvokeMethodCommand.process(InvokeMethodCommand.java:100)
    at com.oracle.odof.core.BasicWork.processCommand(BasicWork.java:81)
    at com.oracle.odof.core.TransactionManager.processCommand(TransactionManager.java:751)
    at com.oracle.odof.core.WorkflowManager.processCommand(WorkflowManager.java:401)
    at com.oracle.odof.core.WorkflowManager.processWork(WorkflowManager.java:459)
    at com.oracle.odof.io.AbstractClient.run(AbstractClient.java:42)
    at java.lang.Thread.run(Thread.java:662)
    End of Job
    If anyone have any suggestions... ?
    Thank you,
    Yacine

Maybe you are looking for

  • How to save data in a report?Urgent...

    hi all, I'm doing a project in java to create report generator..After creating a report i have to save the report..For that i have to save the datas & the program to execute the data..My doubt is that how i would store the data?.According to my idea

  • Switch over from active to passive in the cluster

    If online EMS Sun Server goes off line , the client looses the connectivity with EMS till the IP address of the other online server is updated in client PC. When the servers switch over from active to passive in the cluster, we have to change the ser

  • Account assignment to insp type

    Hi, as i understand we need to assign the account assignement in insp lot to create qm order against each insp lot generated. please advise where is that setting in spro and what is the path / t-code to do so?

  • Business Package for BI Administrators

    Hi all. I imported the <i>Business Package for BI Administrator</i> to the BI Portal (Version 7 SP10). I also did configure a SAP_BW system that test all OK and set its alias to the iViews. The problem is that when i try to execute any iView of the b

  • How to keep OI window in background with message box/pop up boxes on top.

    Hi I have a new requirement to add in OI .How to keep OI main window fixed in the background with message pop ups atop OI window. Even  with message box pop ups , i should not have the access to OI main window.To  make it more clear,when i change to