WebLogic missing data on JNDI Tree Structure

I need to work with Tuxedo through WebLogic, but I am having a bad time trying to figure what is going wrong in here. I have installed WebLogic 10.3 twice and still can't make it right.
In the JNDI Tree Structure many data is missing (among them tuxedo) and can't find a way to fix it.
Please, if anyone can give me a light I'll appreciate it.
Regards.
Pablo Bustos.
EDIT: I am running WebLogic 10.3 on Windows XP 32bits.

Hi,
Check this debug in ur environment.
-Dweblogic.jndi.retainenvironment=true
this should show you the path.
Regards,
Kal.

Similar Messages

  • Updating data using a tree structure?

    Hi,
    I need to change some hierarchical data and wondered the best way to do it.
    Basically I have a menu table which I query as a tree structure:
    select menu_name, level, option_text, displayed
    from menu_option
    start with menu_name = 'CONTROL' and option_number >= 0
    connect by prior command_line = menu_name
    command line has the next menu in the level, unless its a leaf!
    What I want to do is, if a 'parent' has the displayed flag set to N, change all the children underneath to N as well. Whats the neatest way to do this in PL/SQL or SQL statements?
    Thanks,
    Tracey.

    How about
    update menu_option m1
    set displayed = 'N'
    where exists
    (select 1
    from menu_option m2
    where m2.displayed = 'N'
    start with m2.menu_name = m1.menu_name
    connect by prior m2.menu_name = m2.command_line)

  • How to  create Tree Structure for given data?

    Hi,
    I have to create a tree structure of Folders and the contents in the Folder.
    I have a XML, it contains data for the tree structure to display. How can I create a tree structure which would look like below
    Parent
       Child
         Supporting Views
            Raw eInfotree Table Views
            Background Calculations
            QC Data Views
         Calculation Views
         Unit Operation Views
            Cell Culture Views
            Purification Views
            MFR Views
         Personal Views
    All the nodes should have folder Icon.
    Please find the XML as
    <?xml version="1.0" encoding="UTF-8"?><Rowsets DateCreated="2007-05-02T07:37:37" EndDate="2007-05-02T16:59:53" StartDate="2007-05-02T16:59:53" Version="11.5.3"><Rowset><Columns><Column Description="" MaxRange="1" MinRange="0" Name="TK" SQLDataType="4" SourceColumn="TK"/><Column Description="" MaxRange="1" MinRange="0" Name="NAME" SQLDataType="1" SourceColumn="NAME"/><Column Description="" MaxRange="1" MinRange="0" Name="TYPE" SQLDataType="1" SourceColumn="TYPE"/><Column Description="" MaxRange="1" MinRange="0" Name="PK" SQLDataType="4" SourceColumn="PK"/></Columns>
    <Row><TK>1</TK><NAME>Parent</NAME><TYPE>F</TYPE><PK>0</PK></Row>
    <Row><TK>2</TK><NAME>Child</NAME><TYPE>F</TYPE><PK>1</PK></Row>
    <Row><TK>3</TK><NAME>Supporting Views</NAME><TYPE>F</TYPE><PK>2</PK></Row>
    <Row><TK>4</TK><NAME>Raw eInfotree Table Views</NAME><TYPE>F</TYPE><PK>3</PK></Row>
    <Row><TK>5</TK><NAME>Background Calculations</NAME><TYPE>F</TYPE><PK>3</PK></Row>
    <Row><TK>6</TK><NAME>QC Data Views</NAME><TYPE>F</TYPE><PK>3</PK></Row>
    <Row><TK>7</TK><NAME>Calculation Views</NAME><TYPE>F</TYPE><PK>2</PK></Row>
    <Row><TK>8</TK><NAME>Unit Operation Views</NAME><TYPE>F</TYPE><PK>2</PK></Row>
    <Row><TK>9</TK><NAME>Cell Culture Views</NAME><TYPE>F</TYPE><PK>8</PK></Row>
    <Row><TK>10</TK><NAME>Purification Views</NAME><TYPE>F</TYPE><PK>8</PK></Row>
    <Row><TK>11</TK><NAME>MFR Views</NAME><TYPE>F</TYPE><PK>8</PK></Row>
    <Row><TK>12</TK><NAME>Personal Views</NAME><TYPE>F</TYPE><PK>2</PK></Row>
    </Rowset>
    </Rowsets>

    Vishal,
    If you structure your data with two columns, the first being the Node name and the second being the Parent node name (see your information below), the iBrowser applet will make a nice data driven tree with all of the SelectionEvent or navigational capabilities you want.
    <?xml version="1.0" encoding="UTF-8"?>
    <Rowsets DateCreated="2007-05-02T07:37:37" EndDate="2007-05-02T16:59:53" StartDate="2007-05-02T16:59:53" Version="11.5.3">
    <Rowset><Columns><Column Description="" MaxRange="1" MinRange="0" Name="NAME" SQLDataType="1" SourceColumn="NAME"/><Column Description="" MaxRange="1" MinRange="0" Name="PARENT" SQLDataType="1" SourceColumn="PARENT"/></Columns>
    <Row><NAME>Parent</NAME><PARENT></PARENT></Row>
    <Row><NAME>Child</NAME><PARENT>Parent</PARENT></Row>
    <Row><NAME>Supporting Views</NAME><PARENT>Child</PARENT></Row>
    <Row><NAME>Calculation Views</NAME><PARENT>Child</PARENT></Row>
    <Row><NAME>Unit Operation Views</NAME><PARENT>Child</PARENT></Row>
    <Row><NAME>Personal Views</NAME><PARENT>Child</PARENT></Row>
    <Row><NAME>Raw eInfotree Table Views</NAME><PARENT>Supporting Views</PARENT></Row>
    <Row><NAME>Background Calculations</NAME><PARENT>Supporting Views</PARENT></Row>
    <Row><NAME>QC Data Views</NAME><PARENT>Supporting Views</PARENT></Row>
    <Row><NAME>Cell Culture Views</NAME><PARENT>Unit Operation Views</PARENT></Row>
    <Row><NAME>Purification Views</NAME><PARENT>Unit Operation Views</PARENT></Row>
    <Row><NAME>MFR Views</NAME><PARENT>Unit Operation Views</PARENT></Row>
    </Rowset>
    </Rowsets>
    Regards,
    Jeremy

  • Tree Structure?

    Hi Experts,
    I need to create a screen like a Tree Structure like below. If I click on the Reporting Group values folder, it should populate data from one table and by clicking on Reporting Group Levels, it should open the subfolder and need to populate the values based on the selection of folder.
    Is this Tree Structure can be done in Web Dynpro?If yes, how can I go ahead for my development.
    Please clarify me experts.
    BR,
    RAM.

    Hi RAM,
    Yes, it can be done in WDA.
    Your requirement can be achieved as below
    you can create 2 containers side by side in your view i.e. by using PANEL or transparent containers
    Tree structure
    Create tree uielement
    Create context node for tree with required attributes
    Populate the data for tree structure with node key
    Details Display
    Create a table to display data based on tree structure element
    if structure of table of each node/leaf element of tree is different, you can create table ui element dynamically based on your data
    On click of tree element, based on KEY of the selected element, you can populate the details and fill the table in the right side container
    Please refer the demo component for Tree example:
    WDR_TEST_TREE
    Also, check the below links
    Web DynPro ABAP Application using Tree and Frame - Web Dynpro ABAP - SCN Wiki
    SAP nxt: How to create a three level tree node in Webdynpro ABAP
    Hope this helps you.
    Regards,
    Rama

  • Required info on tree structure.

    Hi All,
    Can any body help me in displaying data in a tree structure in PDA.
    We have a requirement where the data comes with parent & child relationship, each child may or may not be a parent and the tree may drill more than 10 levels.
    when user clicks on the node all the subsequent childs need to be displayed and on the second click the tree need to be collapsed to that node level.(this should be similar to some of the data in sap ex: functional locations)
    IS there a component in MI / MAM application to acheive the same else what is the possible way for this.
    Your help will be well appriciated.
    Thanks & Regards,
    Sai.K. K

    Hi Sai,
    well, the answer is unfortunally a NO in the first place.
    MI is based on standard JSP and AWT functionality - up to Version 7.0 - and both runtime environments do not support that stuff on PDA.
    If you run the APP on Lapop only, you could build something like that with Java Script in HTML or extend the functionality there with some Add ons externally available that can be filled by normal XML. But this is outside the usual MI scope, it depends on your creative level. WebDynpro on the other side supports you with a tree view as I remember, so this could be an option - but again, only on Laptop.
    The question is: why do you not split the tree view to several pages? I have no idea about the amount of data you need to carry with you, just in the first place already. Usually tree view could mean a lot of data and this could end up in a long waiting time just to display the first page. Perhaps it is an option to show the actual level of the tree and if the user selects on item, then this item is added to the path (how has he got there) and the next level is displayed in the screen. Pretty much like the Windows Workplace, where every klick on a folder opens a new window with just the info of that window. Performance wise tis could perhaps be the better option.
    Does this help?
    Regards,
    Oliver

  • Adapter JNDI are errored out in JNDI tree on Weblogic

    Hey,
    I have setup weblogic 10.3.4 and SOA Suite 11g.
    The adapters seem to be deployed and active with a green 'OK' status in the deployments on the soa_server1. However when I go to the jndi tree for the soa_server1, all the adapters have an '!' for errored out.
    This is causing various problems. In particular when a process using the Oracle Apps Adapter is deployed it is unable to find the jdbc connection associated with the adapter. However, the jdbc jndi entry is in the tree and the jdbc connection test's just fine.
    So there seems to be a missing link in how the adapters are deployed and how the JNDI is getting updated or something.
    The error is below. Any help appreciated.
    ====> CubeEngine load MIS_INB_WorkOrder_AR_Sync/Process_WO_AR_Sync took 726 ms
    INFO: DeploymentEventPublisher.invoke Publishing deploy event for default/MIS_INB_WorkOrder_AR_Sync!1.0*soa_85dcf1de-1d63-4b34-9f99-3e52c1f04366
    <Aug 10, 2011 1:25:33 PM EDT> <Warning> <oracle.soa.services.notification> <BEA-000000> <<.> Notification via email, voice, SMS or IM will not be sent. If you would like to enable them, please configure corresponding sdpmessaging driver. Then modify the accounts and set NotificationMode attribute to either NONE, EMAIL or ALL in workflow-notification-config.xml>
    INFO: SchemaManager.isIncrementalBuildSupported XMLSchema incremental build enabled.
    <Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> MIS_INB_WorkOrder_AR_Sync Error while performing endpoint Activation: javax.resource.ResourceException: Unable to find data source null>
    <Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> MIS_INB_WorkOrder_AR_Sync
    javax.resource.ResourceException: Unable to find data source null
         at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:52)
         at oracle.tip.adapter.aq.v2.AppsEndpoint.activate(AppsEndpoint.java:51)
         at oracle.tip.adapter.aq.v2.jca.AQResourceAdapter.endpointActivation(AQResourceAdapter.java:62)
         at oracle.tip.adapter.apps.AppsResourceAdapter.endpointActivation(AppsResourceAdapter.java:152)
         at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:494)
         at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performEndpointActivation(JCAEndpointActivation.java:637)
         at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:620)
         at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performActivation(JCAEndpointActivation.java:383)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:583)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.java:438)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisionRegistry.java:403)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionRegistry.java:328)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisionRegistry.java:134)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:96)
         at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevisionChanged(AdapterService.java:309)
         at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.processDefaultInSeries(FabricKernelInitializerServlet.java:577)
         at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:526)
         at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
         at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
         at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused by: java.sql.SQLException: javax.resource.ResourceException: Unable to find data source null
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:97)
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:68)
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:216)
         at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:49)
         ... 19 more
    Caused by: javax.resource.ResourceException: Unable to find data source null
         at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:429)
         at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getConnection(AppsManagedConnectionFactory.java:308)
         at oracle.tip.adapter.apps.AppsManagedConnection.getConnection(AppsManagedConnection.java:147)
         at oracle.tip.adapter.apps.AppsConnection.getJdbcConnection(AppsConnection.java:77)
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:94)
         ... 22 more
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AppsDataSource'. Resolved 'jdbc'; remaining name 'AppsDataSource'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:426)
         ... 26 more
    >
    oracle.fabric.common.FabricDeploymentException: [JCABinding] [MIS_INB_WorkOrder_AR_Sync.consumeARTrgReq/1.0]Unable to complete initialization due to: Endpoint Activation Error.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
    Please correct the reported issue and redeploy the BPEL process.
    : Endpoint Activation Error.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
    Please correct the reported issue and redeploy the BPEL process.
    {rootCauses=[]}
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.access$3600(AdapterServiceRevisionRegistry.java:66)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:608)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.java:438)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisionRegistry.java:403)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionRegistry.java:328)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisionRegistry.java:134)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:96)
         at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevisionChanged(AdapterService.java:309)
         at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.processDefaultInSeries(FabricKernelInitializerServlet.java:577)
         at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:526)
         at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
         at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
         at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused by: BINDING.JCA-12517
    Endpoint Activation Error.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
    Please correct the reported issue and redeploy the BPEL process.
         at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:513)
         at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performEndpointActivation(JCAEndpointActivation.java:637)
         at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:620)
         at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performActivation(JCAEndpointActivation.java:383)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:583)
         ... 11 more
    Caused by: javax.resource.ResourceException: Unable to find data source null
         at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:52)
         at oracle.tip.adapter.aq.v2.AppsEndpoint.activate(AppsEndpoint.java:51)
         at oracle.tip.adapter.aq.v2.jca.AQResourceAdapter.endpointActivation(AQResourceAdapter.java:62)
         at oracle.tip.adapter.apps.AppsResourceAdapter.endpointActivation(AppsResourceAdapter.java:152)
         at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:494)
         ... 15 more
    Caused by: java.sql.SQLException: javax.resource.ResourceException: Unable to find data source null
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:97)
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:68)
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:216)
         at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:49)
         ... 19 more
    Caused by: javax.resource.ResourceException: Unable to find data source null
         at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:429)
         at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getConnection(AppsManagedConnectionFactory.java:308)
         at oracle.tip.adapter.apps.AppsManagedConnection.getConnection(AppsManagedConnection.java:147)
         at oracle.tip.adapter.apps.AppsConnection.getJdbcConnection(AppsConnection.java:77)
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:94)
         ... 22 more
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AppsDataSource'. Resolved 'jdbc'; remaining name 'AppsDataSource'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:426)
         ... 26 more
    <Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "MIS_INB_WorkOrder_AR_Sync" failed: [JCABinding] [MIS_INB_WorkOrder_AR_Sync.consumeARTrgReq/1.0]Unable to complete initialization due to: Endpoint Activation Error.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
    Please correct the reported issue and redeploy the BPEL process.
    : Endpoint Activation Error.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
    Please correct the reported issue and redeploy the BPEL process.

    Hey,
    I have setup weblogic 10.3.4 and SOA Suite 11g.
    The adapters seem to be deployed and active with a green 'OK' status in the deployments on the soa_server1. However when I go to the jndi tree for the soa_server1, all the adapters have an '!' for errored out.
    This is causing various problems. In particular when a process using the Oracle Apps Adapter is deployed it is unable to find the jdbc connection associated with the adapter. However, the jdbc jndi entry is in the tree and the jdbc connection test's just fine.
    So there seems to be a missing link in how the adapters are deployed and how the JNDI is getting updated or something.
    The error is below. Any help appreciated.
    ====> CubeEngine load MIS_INB_WorkOrder_AR_Sync/Process_WO_AR_Sync took 726 ms
    INFO: DeploymentEventPublisher.invoke Publishing deploy event for default/MIS_INB_WorkOrder_AR_Sync!1.0*soa_85dcf1de-1d63-4b34-9f99-3e52c1f04366
    <Aug 10, 2011 1:25:33 PM EDT> <Warning> <oracle.soa.services.notification> <BEA-000000> <<.> Notification via email, voice, SMS or IM will not be sent. If you would like to enable them, please configure corresponding sdpmessaging driver. Then modify the accounts and set NotificationMode attribute to either NONE, EMAIL or ALL in workflow-notification-config.xml>
    INFO: SchemaManager.isIncrementalBuildSupported XMLSchema incremental build enabled.
    <Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> MIS_INB_WorkOrder_AR_Sync Error while performing endpoint Activation: javax.resource.ResourceException: Unable to find data source null>
    <Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.soa.adapter> <BEA-000000> <JCABinding=> MIS_INB_WorkOrder_AR_Sync
    javax.resource.ResourceException: Unable to find data source null
         at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:52)
         at oracle.tip.adapter.aq.v2.AppsEndpoint.activate(AppsEndpoint.java:51)
         at oracle.tip.adapter.aq.v2.jca.AQResourceAdapter.endpointActivation(AQResourceAdapter.java:62)
         at oracle.tip.adapter.apps.AppsResourceAdapter.endpointActivation(AppsResourceAdapter.java:152)
         at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:494)
         at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performEndpointActivation(JCAEndpointActivation.java:637)
         at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:620)
         at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performActivation(JCAEndpointActivation.java:383)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:583)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.java:438)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisionRegistry.java:403)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionRegistry.java:328)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisionRegistry.java:134)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:96)
         at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevisionChanged(AdapterService.java:309)
         at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.processDefaultInSeries(FabricKernelInitializerServlet.java:577)
         at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:526)
         at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
         at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
         at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused by: java.sql.SQLException: javax.resource.ResourceException: Unable to find data source null
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:97)
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:68)
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:216)
         at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:49)
         ... 19 more
    Caused by: javax.resource.ResourceException: Unable to find data source null
         at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:429)
         at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getConnection(AppsManagedConnectionFactory.java:308)
         at oracle.tip.adapter.apps.AppsManagedConnection.getConnection(AppsManagedConnection.java:147)
         at oracle.tip.adapter.apps.AppsConnection.getJdbcConnection(AppsConnection.java:77)
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:94)
         ... 22 more
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AppsDataSource'. Resolved 'jdbc'; remaining name 'AppsDataSource'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:426)
         ... 26 more
    >
    oracle.fabric.common.FabricDeploymentException: [JCABinding] [MIS_INB_WorkOrder_AR_Sync.consumeARTrgReq/1.0]Unable to complete initialization due to: Endpoint Activation Error.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
    Please correct the reported issue and redeploy the BPEL process.
    : Endpoint Activation Error.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
    Please correct the reported issue and redeploy the BPEL process.
    {rootCauses=[]}
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.access$3600(AdapterServiceRevisionRegistry.java:66)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:608)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.activate(AdapterServiceRevisionRegistry.java:438)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.setDefaultRevision(AdapterServiceRevisionRegistry.java:403)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeries.setDefaultRevision(AdapterServiceRevisionRegistry.java:328)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceSeriesSet.setDefaultRevision(AdapterServiceRevisionRegistry.java:134)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry.setDefaultRevision(AdapterServiceRevisionRegistry.java:96)
         at oracle.integration.platform.blocks.adapter.AdapterService.defaultRevisionChanged(AdapterService.java:309)
         at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.processDefaultInSeries(FabricKernelInitializerServlet.java:577)
         at oracle.integration.platform.kernel.FabricKernelInitializerServlet$1.run(FabricKernelInitializerServlet.java:526)
         at oracle.integration.platform.blocks.executor.WorkManagerExecutor$1.run(WorkManagerExecutor.java:120)
         at weblogic.work.j2ee.J2EEWorkManager$WorkWithListener.run(J2EEWorkManager.java:183)
         at weblogic.work.DaemonWorkThread.run(DaemonWorkThread.java:30)
    Caused by: BINDING.JCA-12517
    Endpoint Activation Error.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
    Please correct the reported issue and redeploy the BPEL process.
         at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:513)
         at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performEndpointActivation(JCAEndpointActivation.java:637)
         at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.activateInboundJcaEndpoint(JCAEndpointActivation.java:620)
         at oracle.integration.platform.blocks.adapter.fw.jca.lifecycle.JCAEndpointActivation.performActivation(JCAEndpointActivation.java:383)
         at oracle.integration.platform.blocks.adapter.fw.metadata.AdapterServiceRevisionRegistry$AdapterServiceRevision.endpointActivation(AdapterServiceRevisionRegistry.java:583)
         ... 11 more
    Caused by: javax.resource.ResourceException: Unable to find data source null
         at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:52)
         at oracle.tip.adapter.aq.v2.AppsEndpoint.activate(AppsEndpoint.java:51)
         at oracle.tip.adapter.aq.v2.jca.AQResourceAdapter.endpointActivation(AQResourceAdapter.java:62)
         at oracle.tip.adapter.apps.AppsResourceAdapter.endpointActivation(AppsResourceAdapter.java:152)
         at oracle.integration.platform.blocks.adapter.fw.impl.AdapterFrameworkImpl.endpointActivation(AdapterFrameworkImpl.java:494)
         ... 15 more
    Caused by: java.sql.SQLException: javax.resource.ResourceException: Unable to find data source null
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:97)
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:68)
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getQueue(DBQueueFactory.java:216)
         at oracle.tip.adapter.aq.v2.database.AppsDequeueAgentFactory.createAppsDequeueAgent(AppsDequeueAgentFactory.java:49)
         ... 19 more
    Caused by: javax.resource.ResourceException: Unable to find data source null
         at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:429)
         at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getConnection(AppsManagedConnectionFactory.java:308)
         at oracle.tip.adapter.apps.AppsManagedConnection.getConnection(AppsManagedConnection.java:147)
         at oracle.tip.adapter.apps.AppsConnection.getJdbcConnection(AppsConnection.java:77)
         at oracle.tip.adapter.aq.v2.database.DBQueueFactory.getDatabaseConnection(DBQueueFactory.java:94)
         ... 22 more
    Caused by: javax.naming.NameNotFoundException: Unable to resolve 'jdbc.AppsDataSource'. Resolved 'jdbc'; remaining name 'AppsDataSource'
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:252)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:182)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:214)
         at weblogic.jndi.internal.WLEventContextImpl.lookup(WLEventContextImpl.java:254)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:411)
         at javax.naming.InitialContext.lookup(InitialContext.java:392)
         at oracle.tip.adapter.apps.AppsManagedConnectionFactory.getDataSourceConnection(AppsManagedConnectionFactory.java:426)
         ... 26 more
    <Aug 10, 2011 1:25:44 PM EDT> <Error> <oracle.integration.platform> <SOA-20020> <Deployment of composite "MIS_INB_WorkOrder_AR_Sync" failed: [JCABinding] [MIS_INB_WorkOrder_AR_Sync.consumeARTrgReq/1.0]Unable to complete initialization due to: Endpoint Activation Error.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
    Please correct the reported issue and redeploy the BPEL process.
    : Endpoint Activation Error.
    AdapterFrameworkImpl::endpointActivation - Endpoint Activation Error.
    The Resource Adapter Oracle Applications Adapter was unable to activate the endpoint oracle.tip.adapter.apps.AppsWFBesQueueDequeueActivationSpec:{QueueName=WF_BPEL_Q, DatabaseSchema=APPS, Consumer=ORA_850j4e1g8gsjcc9g6oo36e9h65, MessageSelectorRule=tab.user_data.event_name = 'oracle.apps.mas.soa.workorder2ar.trigger', AppsEventSchema=CUSTOM_SCHEMA} due to the following reason: javax.resource.ResourceException: Unable to find data source null
    Please correct the reported issue and redeploy the BPEL process.

  • Trouble in storing and retrieving RMI object in Weblogic 7 JNDI tree.

    I have created a simple server (BankImpl), implementing a RMI interface
    called Bank. A stub class (BankImpl_Stub.class) is generated from BankImpl
    class using
    "rmic -v1.2". Then I bind an instance of the BankImpl class to the JNDI tree
    in Weblogic
    server 7 under the name of "PeopleBank".
    After the binding, I can see the stub class in the JNDI tree, but with a
    different name: BankImpl_WLStub.class). when a
    client program is trying to lookup the stub associated with "PeopleBank", it
    failed with a puzzling message:
    java.io.NotSerializableException: BankImpl_WLStub
    Why a stub of a RMI object is not serializable? Does Weblogic needs a
    different rmic to generate RMI stubs?
    Thanks,
    Lian

    I have created a simple server (BankImpl), implementing a RMI interface
    called Bank. A stub class (BankImpl_Stub.class) is generated from BankImpl
    class using
    "rmic -v1.2". Then I bind an instance of the BankImpl class to the JNDI tree
    in Weblogic
    server 7 under the name of "PeopleBank".
    After the binding, I can see the stub class in the JNDI tree, but with a
    different name: BankImpl_WLStub.class). when a
    client program is trying to lookup the stub associated with "PeopleBank", it
    failed with a puzzling message:
    java.io.NotSerializableException: BankImpl_WLStub
    Why a stub of a RMI object is not serializable? Does Weblogic needs a
    different rmic to generate RMI stubs?
    Thanks,
    Lian

  • EJB deployed but doesnt show up in JNDI tree on weblogic

    Hi,
    I have a sample EJB deployed on weblogic 10.3 server. My Bean class contains following code.
    ========================================================================
    @Stateless (mappedName = "DemoEJB")
    @TransactionManagement(TransactionManagementType.BEAN)
    public class DemoBean implements SessionBean {
         static final boolean verbose = true;
         private transient SessionContext ctx;
         private transient Properties props;
         @SuppressWarnings("deprecation")
         @Override
         public void setSessionContext(SessionContext ctx) throws EJBException,
                   RemoteException {
              // TODO Auto-generated method stub
              if (verbose)
              System.out.println("setSessionContext called");
              this.ctx = ctx;
              props = ctx.getEnvironment();
         public String demoSelect()
    throws RemoteException
    return("hello world");
    ===========================================================================
    I have created a jar file for the above class using eclipse and deployed it on weblogic. I can see the EJB in the <Deployment> on weblogic but it doesnt appear in <EJB> on JNDI tree view. Therefore i cannot access it from my client code (also written in Eclipse IDE).
    I will appreciate any guidance in this regard.
    Thanks
    Regards,
    Awais

    Hi,
    i have the same problem with yours
    This is my annotation with EJB3.0:
    @Stateless(mappedName="ConSession")
    @Remote(ConBeanRemote.class)
    @Local(ConBean.class)
    and i have a weblogic-ejb-jar.xml to define my jndi name
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-ejb-jar xmlns:wls="http://www.bea.com/ns/weblogic/weblogic-ejb-jar"
              xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
              xsi:schemaLocation="http://java.sun.com/xml/ns/javaee
              http://java.sun.com/xml/ns/javaee/ejb-jar_3_0.xsd
              http://www.bea.com/ns/weblogic/weblogic-ejb-jar
              http://www.bea.com/ns/weblogic/weblogic-ejb-jar/1.0/weblogic-ejb-jar.xsd">
    <weblogic-enterprise-bean>
         <ejb-name>ConSession</ejb-name>
    <stateless-session-descriptor>
         <business-interface-jndi-name-map>
              <business-remote>com.staffware.ConBeanRemote</business-remote>
              <jndi-name>ConSession#com/staffware/ConBeanRemote</jndi-name>
              </business-interface-jndi-name-map>
              </stateless-session-descriptor>
              <local-jndi-name>com/ConfigurationManagerBeanLocal</local-jndi-name>
         </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    [ the most important: I also have specify JNDI in a java file like this
              beanRemoteJNDIs.put("ConBeanRemote","ConSession#com/staffware/ConBeanRemote");
              beanLocalJNDIs.put("ConBean","java:comp/env/com/ConBean");
    and i can find the ConSession#com/staffware/ConBeanRemote in the jndi tree . but it shows like Multilevel directory tree
    and when i login the website and click the button
    .another error comes out :
    13:35:55,046 ERROR [EJBDelegate] Unable to lookup reference java:comp/env/com/ConBean for ConBean!
    javax.naming.LinkException: [Root exception is javax.naming.LinkException:  [Root exception is javax.naming.NameNotFoun
    dException: While trying to look up /app/ejb/CONFIG-ejb-2.0.jar#ConSession/local-home in /app/webapp/CO
    M/18328287.; remaining name '/app/ejb/CONFIG-ejb-2/0/jar#ConfigurationManagerSession/local-home']; Link Remaining Name:
    'java:app/ejb/CONFIG-ejb-2.0.jar#ConSession/local-home']; Link Remaining Name: 'com/ConBean'
    at weblogic.jndi.internal.WLNamingManager.getObjectInstance(WLNamingManager.java:104)
    at weblogic.jndi.internal.BasicNamingNode.resolveObject(BasicNamingNode.java:884)
    at weblogic.jndi.internal.ApplicationNamingNode.resolveObject(ApplicationNamingNode.java:187)
    what should i do ?
    and should i specify the jndi name in the java file . the JNDI name defined in the weblogic is right?
    can you help me ?
    thanks very much in advance!

  • Weblogic Server 9.2 by default allows anonymous modification to JNDI tree

    We found out that Weblogic Server 9.2 by default allows anonymous modification to JNDI tree.
    This is definitely a big security hole. But Oracle support said this is Work By Design conforming to JNDI Specification.
    So we thought this might be overlooked by lots of Weblogic Administrators and would like to share this finding.
    We were told that the solution is to create a policy for jndi.
    We are still checking if there are other resources that are open to anonymous access.
    Hope this will help.
    thanks!

    Yes the only way to secure the JNDI is applying the policies..
    But the catch is, even if your code is executing within the container, it has to pass the credentials..
    Dont knw wether its a good behavior or bad, but that is how it works :)

  • Localhome doesnot appear on the jndi tree on weblogic 8.1 after deployment

    I am upgrading my application from weblogic6.1 to weblogic 8.1 sp3.
    I have a stateless session bean with local interfaces. when I deploy the bean to the weblogic 8.1 server, everything seems to be fine and no error occurs. but when I view the JNDI tree, the localhome is not there and the local interface has just the Bind Name and no stub, no object hash code, no object class and no object to string appears. Trying to test the EJB in the console I get the following error:
    "The EJB MeldePersonDatabaseFacadeBean has not been tested successfully. There was a problem determining the JNDI Name of the given bean."
    what's wrong? why does not local interfaces deploy correctly on weblogic 8.1?
    my descriptors are as follows:
    ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar>
    <display-name>MeldePersonDatabaseEJB</display-name>
    <enterprise-beans>
    <session>
    <display-name>MeldePersonDatabaseFacadeBean</display-name>
    <ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
    <local-home>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeLocalHome</local-home>
    <local>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeLocal</local>
    <ejb-class>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    weblogic-ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN" "http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd">
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
    <local-jndi-name>MeldePersonDatabaseFacadeBeanLocal</local-jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    --------------------

    I believe the console only supports testing of remote ejbs.
    I didn't see anything obviously wrong with your app. I'm guessing that
    it's working fine. I'd just write a Servlet that hits the local ejb.
    That should prove whether it's working or not.
    -- Rob
    Murteza Salemi wrote:
    I am upgrading my application from weblogic6.1 to weblogic 8.1 sp3.
    I have a stateless session bean with local interfaces. when I deploy the bean to the weblogic 8.1 server, everything seems to be fine and no error occurs. but when I view the JNDI tree, the localhome is not there and the local interface has just the Bind Name and no stub, no object hash code, no object class and no object to string appears. Trying to test the EJB in the console I get the following error:
    "The EJB MeldePersonDatabaseFacadeBean has not been tested successfully. There was a problem determining the JNDI Name of the given bean."
    what's wrong? why does not local interfaces deploy correctly on weblogic 8.1?
    my descriptors are as follows:
    ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
    <ejb-jar>
    <display-name>MeldePersonDatabaseEJB</display-name>
    <enterprise-beans>
    <session>
    <display-name>MeldePersonDatabaseFacadeBean</display-name>
    <ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
    <local-home>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeLocalHome</local-home>
    <local>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeLocal</local>
    <ejb-class>aetat.amelding.meldepersondatabase.facade.ejb.MeldePersonDatabaseFacadeBean</ejb-class>
    <session-type>Stateless</session-type>
    <transaction-type>Container</transaction-type>
    </session>
    </enterprise-beans>
    <assembly-descriptor>
    <container-transaction>
    <method>
    <ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
    <method-name>*</method-name>
    </method>
    <trans-attribute>Required</trans-attribute>
    </container-transaction>
    </assembly-descriptor>
    </ejb-jar>
    weblogic-ejb-jar.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE weblogic-ejb-jar PUBLIC "-//BEA Systems, Inc.//DTD WebLogic 8.1.0 EJB//EN" "http://www.bea.com/servers/wls810/dtd/weblogic-ejb-jar.dtd">
    <weblogic-ejb-jar>
    <weblogic-enterprise-bean>
    <ejb-name>MeldePersonDatabaseFacadeBean</ejb-name>
    <local-jndi-name>MeldePersonDatabaseFacadeBeanLocal</local-jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>

  • How to Display Tree structure in Grid Data ?

    Hi Friends.,
                      I am Using tree control to get the data from database dynamically.
                        Now i use to selected (node or folder) will be display in grid in tree structure with using panel.   any Example coding....?
    Any One Help me.....
    With Regards.,
    Lingu..,

    i've posted some examples to Tree structures in a Datagrid in a topic a few below this one
    http://forums.adobe.com/thread/569070?tstart=0

  • Data source JNDI lookup fails in Weblogic 12.1.2

    What  is changed in the Weblogic 12.1.2 JNDI handling?
    My EJB 2.1 application has been working fine with Weblogic versions up to 12.1.1, but with version 12.1.2 it is giving the following error at startup:
    weblogic.application.ModuleException: javax.naming.NameNotFoundException: remaining name: comp/env/jdbc/DataSourceAlias
    where jdbc/DatasourceAlias is the res-ref-name of the actual datasource named jdbc/APP_DATASOURCE which is set through the admin console.
    The discovery of the datasource is performed by this piece of code :
    ds = initialContext.lookup ("java:comp/env/" + refName)
    This is what is failing with Weblogic 12. After some research I found out that in order for the datasource lookup to succeed, I have to :
    1) ignore the subcontext "comp/env" and
    2) use the actual JNDI name "jdbc/APP_DATASOURCE" instead of the reference "jdbc/DataSourceAlias"
    However for the EJBs, nothing is changed, they are found in the comp/env subcontext.
    Hope this helps someone, or let someone tell me how the migration to Weblogic 12.1.2 is supposed to be done.

    Hi,
    If it is war then try to apply following  Patch 13893259.
    Regards,
    Kal

  • Publish, deploy, jndi tree

    Hello,
    I work with Weblogic server 9.2 and Ganymede 3.4.
    Here are some beginner questions:
    Why do I, in Ganymede's server tab, publish on the server node instead of on the EAR node?
    When I publish my EAR I cannot see anything added in the jndi tree of the app-server (via admin console, view jndi tree). What do I miss?
    This my weblogic-ejb-jar:
    <?xml version="1.0" encoding="UTF-8"?>
    <weblogic-ejb-jar xmlns="http://www.bea.com/ns/weblogic/90" xmlns:j2ee="http://java.sun.com/xml/ns/j2ee" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.bea.com/ns/weblogic/90 http://www.bea.com/ns/weblogic/90/weblogic-ejb-jar.xsd">
    <!-- server-version: 9.2 -->
    <weblogic-enterprise-bean>
    <ejb-name>HelloWorld</ejb-name>
    <stateless-session-descriptor>
    </stateless-session-descriptor>
    <jndi-name>ejb.EjbHelloWorldHome</jndi-name>
    </weblogic-enterprise-bean>
    </weblogic-ejb-jar>
    Is there a perspective that displays the weblogic generated stub/skeleton files?
    Is there a difference between publishing an EAR and deploying an EAR, except that deploying refers to a production environment instead of dev environment?
    Thanks for any ideas.

    If you are using OEPE - Oracle Enterprise Pack for Eclipse (or Workshop), then WebLogic EJB's are built (the stubs, etc) with a tool called EJBGen, this link is for 10.3, but I'm pretty sure it's the same for 9.2
    http://download.oracle.com/docs/cd/E12839_01/wls/docs103/ejb/EJBGen_reference.html
    I think that is implemented as a an Eclipse build task, so it's only run when exporting to an archive like an EAR or EJB jar OR when publishing to the server. In either case, those generated classes would not be shown in Eclipse.
    Check your deployments tab of your WLS console to see if you application is deployed an active. If it is, then I would expect to see entries from your application in the JNDI tree.
    The OEPE forum is a better place to ask Eclipse questions:
    Enterprise Pack for Eclipse

  • Error While Viewing JNDI Tree

              Hi
              I'm facing the following problem while viewing the JNDI tree. I had configured
              two servers ejbServer,ejbServer1 both clustered, i can able to start both the
              servers, but in the JNDI tree when i click ejbServer or Replication Manager
              i'm getting the following error please help me out.
              An unexpected error was encountered in processing your request.
              Exception
              javax.naming.NameNotFoundException: Unable to resolve weblogic.transaction.coordinators.ejbServer.
              Resolved: 'weblogic.transaction.coordinators' Unresolved:'ejbServer' ; remaining
              name ''
                   <>
              Current Date
              Mon Aug 27 09:15:19 GMT+08:00 2001
              Console Release Build
              6.0 Service Pack 2
              Console Build
              6.0 Service Pack 2 05/24/2001 11:55:28 #117037
              Server Release Build
              6.0 Service Pack 2
              Server Build
              6.0 Service Pack 2 05/24/2001 11:55:28 #117037
              All Server Product Versions
              WebLogic Server Build:     6.0 Service Pack 2 05/24/2001 11:55:28 #117037
              WebLogic XML Module:     6.0 Service Pack 2 05/24/2001 12:34:27 #117037
              Request Info
              Protocol: HTTP/1.1
              ServerName: 127.0.0.1
              ServerPort: 7001
              Secure: false
              ContextPath: /console
              ServletPath: /common/error.jsp
              QueryString: null
              PathInfo: null
              PathTranslated: null
              RequestURI: /console/common/error.jsp
              AuthType: Basic
              ContentType: null
              CharacterEncoding: null
              Locale: hi
              Method: GET
              Session: weblogic.servlet.internal.session.MemorySessionData@37b6ef
              RequestedSessionId: O4meRts3MSQ1pr2YCfOsUGA3MckiUv6wmiQVYrdcQBy3oYpYTz2Q/console
              RequestedSessionIdFromCookie: true
              RequestedSessionIdFromURL: false
              UserPrincipal: system
              RemoteUser: system
              RemoteAddr: 127.0.0.1
              RemoteHost: localhost
              Parameters
              binding = ejbServer
              context = weblogic.transaction.coordinators
              Attributes
              console.original./console/common/error.jsp.ContextPath = /console
              console.original./console/common/error.jsp.Method = GET
              console.original./console/common/error.jsp.RemoteUser = system
              console.original./console/common/error.jsp.RequestURI = /console/common/error.jsp
              console.original./console/common/error.jsp.ServletPath = /common/error.jsp
              console.original./console/panels/mbean/JNDIBinding.jsp.ContextPath = /console
              console.original./console/panels/mbean/JNDIBinding.jsp.Method = GET
              console.original./console/panels/mbean/JNDIBinding.jsp.QueryString = context=weblogic.transaction.coordinators&binding=ejbServer
              console.original./console/panels/mbean/JNDIBinding.jsp.RemoteUser = system
              console.original./console/panels/mbean/JNDIBinding.jsp.RequestURI = /console/panels/mbean/JNDIBinding.jsp
              console.original./console/panels/mbean/JNDIBinding.jsp.ServletPath = /panels/mbean/JNDIBinding.jsp
              console.preferences.ContextKey = /panels/mbean/JNDIBinding.jsp
              javax.servlet.include.context_path = /console
              javax.servlet.include.request_uri = /console/common/requestinfo.jsp
              javax.servlet.include.servlet_path = /common/requestinfo.jsp
              javax.servlet.jsp.jspException = javax.naming.NameNotFoundException:
              Unable to resolve weblogic.transaction.coordinators.ejbServer. Resolved: 'weblogic.transaction.coordinators'
              Unresolved:'ejbServer' ; remaining name ''
              weblogic.httpd.user = system
              weblogic.management.console.tags.ContentTag = java.lang.Object@397a54
              weblogic.management.console.tags.HeaderTag = java.lang.Object@e4a33
              Headers
              Accept = image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/vnd.ms-excel,
              application/msword, application/vnd.ms-powerpoint, */*
              Accept-Encoding = gzip, deflate
              Accept-Language = hi
              Authorization = Basic c3lzdGVtOm1hbmFnZXIx
              Connection = Keep-Alive
              Cookie = JSESSIONID=O4meRts3MSQ1pr2YCfOsUGA3MckiUv6wmiQVYrdcQBy3oYpYTz2Q!2557472653882942880!-1062729946!7001!7002
              Host = 127.0.0.1:7001
              User-Agent = Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)
              BrowserInfo
              User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 4.0)
              IE: true
              Netscape: false
              Supported: true
              JavscriptHrefs: false
              TableCellClick: true
              DocumentReloadedOnResize: false
              DropdownStretchable: true
              CellSpacingBlank: false
              EmptyCellBlank: false
              ImgOnclickSupported: true
              TableBorderFancy: true
              PartialToWideTables: false
              Server System Properties
              awt.toolkit = sun.awt.windows.WToolkit
              bea.home = d:\Weblogic
              cloudscape.system.home = ./samples/eval/cloudscape/data
              file.encoding = Cp1252
              file.encoding.pkg = sun.io
              file.separator = \
              java.awt.fonts =
              java.awt.graphicsenv = sun.awt.Win32GraphicsEnvironment
              java.awt.printerjob = sun.awt.windows.WPrinterJob
              java.class.path = .;d:\Weblogic\jdk130\lib\tools.jar;d:\Weblogic\wlserver\lib\weblogic_sp.jar;d:\Weblogic\wlserver\lib\weblogic.jar;d:\Weblogic\wlserver\lib\xmlx.jar;d:\Weblogic\wlserver\lib\ejb20.jar;d:\Weblogic\wlserver\samples\eval\cloudscape\lib\cloudscape.jar;;;;d:\Weblogic;d:\Weblogic\wlserver\bin\oci816_8;d:\Oracle_Home\iSuites\jdbc\lib\classes12.zip;d:\Weblogic\wlserver\lib;d:\Oracle_Home\iSuites\lib\xmlparserv2.jar;d:\JDeveloper\lib\xsu12.jar;;
              java.class.version = 47.0
              java.ext.dirs = d:\Weblogic\jdk130\jre\lib\ext
              java.home = d:\Weblogic\jdk130\jre
              java.io.tmpdir = C:\TEMP\
              java.library.path = d:\Weblogic\jdk130\bin;.;C:\WINNT\System32;C:\WINNT;.\bin;D:\Oracle_Home\iSuites\BIN;D:\Oracle_Home\iSuites\Apache\Perl\5.00503\bin\mswin32-x86;C:\Program
              Files\Oracle\jre\1.1.7\bin;C:\WINNT\system32;C:\WINNT;C:\VisualCafeSE\Java2\Bin;C:\Program
              Files\Common Files\WebGain Shared;C:\VisualCafeSE\Bin;
              java.naming.factory.initial = weblogic.jndi.WLInitialContextFactory
              java.naming.factory.url.pkgs = weblogic.jndi.factories
              java.protocol.handler.pkgs = weblogic.utils|weblogic.utils|weblogic.net|weblogic.management|weblogic.net|weblogic.net|weblogic.utils
              java.runtime.name = Java(TM) 2 Runtime Environment, Standard
              Edition
              java.runtime.version = 1.3.0-C
              java.security.policy = =d:\Weblogic\wlserver/lib/weblogic.policy
              java.specification.name = Java Platform API Specification
              java.specification.vendor = Sun Microsystems Inc.
              java.specification.version = 1.3
              java.vendor = Sun Microsystems Inc.
              java.vendor.url = http://java.sun.com/
              java.vendor.url.bug = http://java.sun.com/cgi-bin/bugreport.cgi
              java.version = 1.3.0
              java.vm.info = mixed mode
              java.vm.name = Java HotSpot(TM) Client VM
              java.vm.specification.name = Java Virtual Machine Specification
              java.vm.specification.vendor = Sun Microsystems Inc.
              java.vm.specification.version = 1.0
              java.vm.vendor = Sun Microsystems Inc.
              java.vm.version = 1.3.0-C
              javax.rmi.CORBA.PortableRemoteObjectClass = weblogic.iiop.PortableRemoteObjectDelegateImpl
              javax.rmi.CORBA.UtilClass = weblogic.iiop.UtilDelegateImpl
              javax.xml.parsers.DocumentBuilderFactory = weblogic.xml.jaxp.RegistryDocumentBuilderFactory
              javax.xml.parsers.SAXParserFactory = weblogic.xml.jaxp.RegistrySAXParserFactory
              jmx.implementation.name = JMX RI
              jmx.implementation.vendor = Sun Microsystems
              jmx.implementation.version = 1.0
              jmx.specification.name = Java Management Extensions
              jmx.specification.vendor = Sun Microsystems
              jmx.specification.version = 1.0 Final Release
              line.separator =
              os.arch = x86
              os.name = Windows NT
              os.version = 4.0
              path.separator = ;
              sun.boot.class.path = d:\Weblogic\jdk130\jre\lib\rt.jar;d:\Weblogic\jdk130\jre\lib\i18n.jar;d:\Weblogic\jdk130\jre\lib\sunrsasign.jar;d:\Weblogic\jdk130\jre\classes
              sun.boot.library.path = d:\Weblogic\jdk130\jre\bin
              sun.cpu.endian = little
              sun.cpu.isalist = pentium_pro+mmx pentium_pro pentium+mmx
              pentium i486 i386
              sun.io.unicode.encoding = UnicodeLittle
              user.dir = D:\Weblogic\wlserver
              user.home = C:\WINNT\Profiles\venkata
              user.language = en
              user.name = venkata
              user.region = US
              user.timezone = Asia/Singapore
              weblogic.Domain = DNSdomain
              weblogic.Name = DNSserver
              weblogic.management.discover = true
              weblogic.security.jaas.Configuration = weblogic.security.internal.ServerConfig
              weblogic.security.jaas.Policy = d:/Weblogic/wlserver/lib/Server.policy
              

    [att1.html]
              

  • Tree structure in f4 help

    Hi experts,
    can any one give me sample code for providing tree structure in f4help.  like object part field have in iw21 transaction
    Regards
    reddy

    Hi Muttukundu,
    SAP has provided a lot of sample programs for developing tree structures. Just go to SE38, type BCALVTREE and hit F4. You'll get different sample programs with a range of operations on trees
    Go through the link,
    http://www.sapdevelopment.co.uk/reporting/alv/alvtree.htm
    Slowly check this code..you will get idea of how to develop tree structure.
    REPORT y_hierarchies_in_tables
    NO STANDARD PAGE HEADING.
    PARAMETER: g_group TYPE grpname. " DEFAULT 'Z_GLAB0000'.
    DATA:
    g_setid TYPE setid,
    g_class TYPE setclass.
    DATA: lt_hier TYPE STANDARD TABLE OF sethier,
    lt_val TYPE STANDARD TABLE OF setvalues.
    DATA: hier LIKE sethier OCCURS 0 WITH HEADER LINE,
    val LIKE setvalues OCCURS 0 WITH HEADER LINE,
    setinfo LIKE setinfo OCCURS 0 WITH HEADER LINE.
    DATA: zaccbas(20) TYPE c OCCURS 0 WITH HEADER LINE.
    DATA: miss_val LIKE setvalues-from OCCURS 0 WITH HEADER LINE.
    DATA: table_name TYPE tabname,
    field_name TYPE setfld.
    DATA: ambiguity_flag TYPE c.
    Ambiguity check
    PERFORM ambiguity_check.
    Display Records
    PERFORM display_records.
    *& Form AMBIGUITY_CHECK
    Ambiguity check
    FORM ambiguity_check .
    DATA: it_abaplist LIKE abaplist OCCURS 0 WITH HEADER LINE.
    DATA: BEGIN OF it_ascilist OCCURS 0,
    zeile(256) TYPE c,
    END OF it_ascilist.
    DATA: flag.
    SUBMIT rgsovl00 "VIA SELECTION-SCREEN
    WITH p_shrtn = g_group
    WITH path = 'X'
    EXPORTING LIST TO MEMORY
    AND RETURN.
    CALL FUNCTION 'LIST_FROM_MEMORY'
    TABLES
    listobject = it_abaplist
    EXCEPTIONS
    not_found = 1
    OTHERS = 2.
    CALL FUNCTION 'LIST_TO_ASCI'
    TABLES
    listasci = it_ascilist
    listobject = it_abaplist
    EXCEPTIONS
    empty_list = 1
    list_index_invalid = 2
    OTHERS = 3 .
    LOOP AT it_ascilist.
    IF it_ascilist-zeile = text-001.
    flag = 'X'.
    ENDIF.
    IF flag = 'X' AND
    it_ascilist-zeile = text-002.
    ambiguity_flag = 'X'.
    CLEAR flag.
    ENDIF.
    ENDLOOP.
    FREE MEMORY.
    ENDFORM. " AMBIGUITY_CHECK
    *& Form DISPLAY_RECORDS
    Display the Records
    FORM display_records .
    PERFORM get_records.
    PERFORM header_data.
    PERFORM item_data.
    ENDFORM. " DISPLAY_RECORDS
    *& Form GET_RECORDS
    Get all the Node values
    FORM get_records .
    Get the ID name for the Hierarchy
    CALL FUNCTION 'G_SET_GET_ID_FROM_NAME'
    EXPORTING
    shortname = g_group
    setclass = g_class
    old_setid = g_setid
    IMPORTING
    new_setid = g_setid.
    Get the Table and Field name for the Top Node
    CALL FUNCTION 'G_SET_GET_INFO'
    EXPORTING
    setname = g_setid
    no_set_title = 'X'
    use_table_buffer = 'X'
    IMPORTING
    info = setinfo.
    table_name = setinfo-tabname.
    field_name = setinfo-fld.
    Get all the Nodes for the Hierarchy
    CALL FUNCTION 'G_SET_TREE_IMPORT'
    EXPORTING
    no_descriptions = ' '
    no_rw_info = 'X'
    setid = g_setid
    TABLES
    set_hierarchy = lt_hier
    set_values = lt_val.
    hier[] = lt_hier.
    val[] = lt_val.
    SELECT (field_name) FROM (table_name) INTO TABLE zaccbas.
    LOOP AT zaccbas.
    READ TABLE val WITH KEY FROM = zaccbas.
    IF sy-subrc = 0.
    DELETE zaccbas.
    CLEAR zaccbas.
    DELETE val INDEX sy-tabix.
    CLEAR val.
    ENDIF.
    ENDLOOP.
    ENDFORM. " GET_RECORDS
    *& Form HEADER_DATA
    Header Data
    FORM header_data .
    DATA: desc TYPE settext.
    READ TABLE hier WITH KEY fieldname = field_name
    shortname = g_group.
    IF sy-subrc = 0.
    desc = hier-descript.
    ENDIF.
    SKIP.
    WRITE: 'Node :',g_group.
    WRITE:75 'User name :', sy-uname.
    WRITE:/ 'Description :', desc.
    WRITE:75 'Date:', sy-datum.
    WRITE:/ 'Table Name :' , table_name.
    WRITE:75 'Time:', sy-timlo.
    WRITE:/ 'Field Name :', field_name.
    write:75 'Client:', SY-MANDT.
    skip.
    IF ambiguity_flag = 'X'.
    WRITE:/ 'Ambiguity Check :'. WRITE: 'Success' COLOR 5.
    ELSE.
    WRITE:/ 'Ambiguity Check :'. WRITE: 'Failed' COLOR 6 .
    ENDIF.
    WRITE:/ sy-uline.
    WRITE:/37 'Validation for Hierarchy'.
    WRITE:/ sy-uline.
    ENDFORM. " HEADER_DATA
    *& Form ITEM_DATA
    Output Report for Nodes
    FORM item_data .
    IF NOT zaccbas[] IS INITIAL.
    WRITE:/ 'Missing Records from Hierarchy' COLOR 3.
    LOOP AT zaccbas.
    WRITE:/ zaccbas.
    ENDLOOP.
    ENDIF.
    IF NOT val[] IS INITIAL.
    SKIP 1.
    WRITE:/ 'Additional Records in Hierarchy' COLOR 3.
    LOOP AT val.
    WRITE:/ val-from. ", 28 val-DESCRIPT.
    ENDLOOP.
    ELSEIF ZACCBAS[] IS INITIAL.
    WRITE:/ 'No Missing Records Found' COLOR 3.
    ENDIF.
    ENDFORM. " ITEM_DATA
    Reward if found helpfull,
    Cheers,
    Chaitanya.

Maybe you are looking for