Create a DataSource with ant

Hello every body,
I want to create an ANT target that aims to create a Data Source on the Server.
Thanks.

gday tootyhorn -- it works a treat using the Ant tasks we supply with 10.1.3.1 and onwards.
I have a worked example of creating/testing/removing datasources and connection pools directly from Ant using the tasks -- it's not on OTN yet, but if you send me your email address, I'll shoot it to you.
I'm steve dot button at oracle dot com.
-steve-

Similar Messages

Cannot create a DataSource with MySql...

Hi all,
I'm trying to create a DataSource with WLS 9.1.
The DataBase I'm using is MySql 4.1.
I have copied the mysql-connector.jar in the "lib" folder of my domain, but when I try to target the DataSource to the Server I get an error that Mysql Driver class is not found.
Should I insert the driver somewhere else ? or should I add manually the file to the server classpath ?
Thanks
Francesco

Francesco Marchioni wrote:
Hi all,
I'm trying to create a DataSource with WLS 9.1.
The DataBase I'm using is MySql 4.1.
I have copied the mysql-connector.jar in the "lib" folder of my domain, but when I try to target the DataSource to the Server I get an error that Mysql Driver class is not found.
Should I insert the driver somewhere else ? or should I add manually the file to the server classpath ?
Thanks
Francescoedit the script that starts WebLogic. You will see a CLASSPATH definition
is constructed and applied to the WebLogic call. Add your jar to that
CLASSPATH.
Joe

Creating a datasource that sits on a table

Hello All,
I have to create a datasource that sits on a table and reads certain fields. I have found the relevant table via the data browser "RSPCLOGCHAIN". I am now in transaction sbiw - please advise further.
Thank you and kind regards,
Keith

Hi Keith,
The steps would be as follows:
1. Goto to RSO2.
2. Create a datasource with a technical name and assign it to a Application Component.
3. Choose the Extraction from view section and enter you table name.
4. Save it.
5. It would list all the fields of that table. You can hide the ones that you do not want. Save again.
Bye
Dinesh

Problem to create data source with OCI type of driver

Hi Experts
We are creating an XA datasource with OCI type of driver using an enterprise application with data-sources.xml, the xml is like this:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE data-sources SYSTEM "data-sources.dtd" >
<data-sources>
     <data-source>
          <data-source-name>OCI_DS_XA</data-source-name>
          <driver-name>ORACLE_DRIVER</driver-name>
          <init-connections>1</init-connections>
          <max-connections>25</max-connections>
          <max-time-to-wait-connection>120</max-time-to-wait-connection>
          <expiration-control>
               <connection-lifetime>60</connection-lifetime>
               <run-cleanup-thread>300</run-cleanup-thread>
          </expiration-control>
          <sql-engine>Vendor_SQL</sql-engine>
          <jdbc-2.0>
               <xads-class-name>
                    oracle.jdbc.xa.client.OracleXADataSource
               </xads-class-name>
               <object-factory>
                    oracle.jdbc.pool.OracleDataSourceFactory
               </object-factory>
               <properties>
                    <property>
                         <property-name>serverName</property-name>
                         <property-value><SERVER_NAME></property-value>
                    </property>
                    <property>
                         <property-name>serverPort</property-name>
                         <property-value>1521</property-value>
                    </property>
                    <property>
                         <property-name>databaseName</property-name>
                         <property-value>ORCL</property-value>
                    </property>
                    <property>
                         <property-name>driverType</property-name>
                         <property-value>oci</property-value>
                    </property>
                    <property>
                         <property-name>user</property-name>
                         <property-value>username</property-value>
                    </property>
                    <property>
                         <property-name>password</property-name>
                         <property-value>password</property-value>
                    </property>
               </properties>
          </jdbc-2.0>
          </data-source>
</data-sources>
We have installed oracle client in server M/C and configured all the environment variables. While we are deploying the application from CE developer studio IDE to the CE 7.1 AS, we are getting the following error:
Description:
          1. Exception has been returned while the 'sap.com/DS_TEST_EAR' was starting. Warning/Exception :
[ERROR CODE DPL.DS.6193] Error while ; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: [ERROR CODE DPL.DS.5030] Clusterwide exception: server ID 7653550:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot create DataSource "OCI_DS_XA".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1467)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:468)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:219)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:179)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:419)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:495)
     at com.sap.engine.services.deploy.server.application.StartTransaction.makeAllPhasesImpl(StartTransaction.java:554)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:248)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:389)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3387)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3373)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3276)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:3249)
     at com.sap.engine.services.dc.lcm.impl.J2EELCMProcessor.doStart(J2EELCMProcessor.java:99)
     at com.sap.engine.services.dc.lcm.impl.LifeCycleManagerImpl.start(LifeCycleManagerImpl.java:62)
     at com.sap.engine.services.dc.cm.deploy.impl.LifeCycleManagerStartVisitor.visit(LifeCycleManagerStartVisitor.java:34)
     at com.sap.engine.services.dc.cm.deploy.impl.DeploymentItemImpl.accept(DeploymentItemImpl.java:83)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcessLCMDeplItem(DefaultDeployPostProcessor.java:80)
     at com.sap.engine.services.dc.cm.deploy.impl.DefaultDeployPostProcessor.postProcess(DefaultDeployPostProcessor.java:56)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doPostProcessing(DeployerImpl.java:741)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.performDeploy(DeployerImpl.java:732)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.doDeploy(DeployerImpl.java:576)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:270)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImpl.deploy(DeployerImpl.java:192)
     at com.sap.engine.services.dc.cm.deploy.impl.DeployerImplp4_Skel.dispatch(DeployerImplp4_Skel.java:875)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:351)
     at com.sap.engine.services.rmi_p4.server.ServerDispatchImpl.run(ServerDispatchImpl.java:70)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:62)
     at com.sap.engine.services.rmi_p4.P4Message.execute(P4Message.java:37)
     at com.sap.engine.services.cross.fca.FCAConnectorImpl.executeRequest(FCAConnectorImpl.java:872)
     at com.sap.engine.services.rmi_p4.P4Message.process(P4Message.java:53)
     at com.sap.engine.services.cross.fca.MessageReader.run(MessageReader.java:58)
     at com.sap.engine.core.thread.execution.Executable.run(Executable.java:108)
     at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:304)
Caused by: com.sap.engine.frame.core.database.DatabaseException: Exception of type java.sql.SQLException occurred: Closed Connection.
     at com.sap.engine.core.database.impl.DataSourceAdministratorImpl.createDataSource(DataSourceAdministratorImpl.java:49)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1400)
     ... 33 more
Caused by: java.sql.SQLException: Closed Connection
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:162)
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:227)
     at oracle.jdbc.driver.GetCharSetError.processError(T2CConnection.java:3082)
     at oracle.jdbc.driver.T2CConnection.getCharSetIds(T2CConnection.java:2811)
     at oracle.jdbc.driver.T2CConnection.logon(T2CConnection.java:300)
     at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:344)
     at oracle.jdbc.driver.T2CConnection.<init>(T2CConnection.java:136)
     at oracle.jdbc.driver.T2CDriverExtension.getConnection(T2CDriverExtension.java:79)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:545)
     at oracle.jdbc.pool.OracleDataSource.getConnection(OracleDataSource.java:194)
     at oracle.jdbc.pool.OracleConnectionPoolDataSource.getPhysicalConnection(OracleConnectionPoolDataSource.java:121)
     at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:333)
     at oracle.jdbc.xa.client.OracleXADataSource.getXAConnection(OracleXADataSource.java:84)
     at com.sap.sql.connect.factory.XADSPooledConnectionFactory.getPooledConnection(XADSPooledConnectionFactory.java:27)
     at com.sap.sql.connect.datasource.DBDataSourceImpl.createPooledConnection(DBDataSourceImpl.java:677)
     at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.initConnections(DBDataSourcePoolImpl.java:1099)
     at com.sap.sql.connect.datasource.DBDataSourcePoolImpl.<init>(DBDataSourcePoolImpl.java:49)
     at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:507)
     at com.sap.sql.connect.datasource.DataSourceManager.createDataSource(DataSourceManager.java:136)
     at com.sap.sql.manager.OpenSQLManager.createDataSource(OpenSQLManager.java:141)
     at com.sap.engine.core.database.impl.DataSourceAdministratorImpl.createDataSource(DataSourceAdministratorImpl.java:42)
     ... 34 more
But when we are creating the datasource with thin type of driver, it is working fine. We have already created a driver with name ORACLE_DRIVER in server using the ojdbc14.jar using Netweaver administrator consol.
Same this is happening when we are creating the OCI type of datasource by using Netweaver administrator consol by specifying all the parameter as above and also the initial connection pool size is more than zero.
Same thing is happening for normal (JDBC 1x) datasource creation with OCI type driver.

Hello,
I ran a search on SDN, related to your error code, i found the following:
UnsupportedClassVersionError in NWDS CE
DeploymentWarning-WebService-Collection
Maybe its useful to you
Regards,
Siddhesh

Can't create a Datasource

Hi, i'm trying to create a Datasource with the Visual Administrator and I'm getting this error:
java.rmi.RemoteException: Error occurred while starting application in whole cluster and wait.; nested exception is:
     com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 2178150:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "MS_SQL_DS_II".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1549)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1825)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:370)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:318)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:299)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:110)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:212)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4605)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:656)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:640)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:562)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:261)
     at sun.reflect.GeneratedMethodAccessor278.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:255)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: javax.resource.ResourceException: java.lang.NullPointerException
     at com.sap.engine.services.dbpool.spi.CPManagedConnectionFactoryImpl.createManagedConnection(CPManagedConnectionFactoryImpl.java:145)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.init(ConnectionHashSet.java:151)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.<init>(ConnectionHashSet.java:120)
     at com.sap.engine.services.connector.jca.AdapterCache.open(AdapterCache.java:207)
     at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:290)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1825)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:370)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:318)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:299)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:110)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:212)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4605)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:656)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:640)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:562)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:261)
     at sun.reflect.GeneratedMethodAccessor278.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:255)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.init(ConnectionHashSet.java:162)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.<init>(ConnectionHashSet.java:120)
     at com.sap.engine.services.connector.jca.AdapterCache.open(AdapterCache.java:207)
     at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:290)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
     ... 41 more
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:658)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:640)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:562)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:261)
     at sun.reflect.GeneratedMethodAccessor278.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:255)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: com.sap.engine.services.deploy.exceptions.ServerDeploymentException: Clusterwide exception: server ID 2178150:com.sap.engine.services.dbpool.exceptions.BaseDeploymentException: Cannot start DataSource "MS_SQL_DS_II".
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1549)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1825)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:370)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:318)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:299)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:110)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:212)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4605)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:656)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:640)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:562)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:261)
     at sun.reflect.GeneratedMethodAccessor278.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:255)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
Caused by: javax.resource.ResourceException: java.lang.NullPointerException
     at com.sap.engine.services.dbpool.spi.CPManagedConnectionFactoryImpl.createManagedConnection(CPManagedConnectionFactoryImpl.java:145)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.init(ConnectionHashSet.java:151)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.<init>(ConnectionHashSet.java:120)
     at com.sap.engine.services.connector.jca.AdapterCache.open(AdapterCache.java:207)
     at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:290)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSources(ContainerImpl.java:1825)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.prepareStart(ContainerImpl.java:489)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepareCommon(StartTransaction.java:370)
     at com.sap.engine.services.deploy.server.application.StartTransaction.prepare(StartTransaction.java:318)
     at com.sap.engine.services.deploy.server.application.ApplicationTransaction.makeAllPhasesOnOneServer(ApplicationTransaction.java:299)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesImpl(ParallelAdapter.java:301)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:110)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:212)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4605)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:656)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:640)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.startApplication(DataSourceManagerImpl.java:562)
     at com.sap.engine.services.dbpool.deploy.DataSourceManagerImpl.deploy(DataSourceManagerImpl.java:261)
     at sun.reflect.GeneratedMethodAccessor278.invoke(Unknown Source)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.pj.jmx.introspect.DefaultMBeanInvoker.invoke(DefaultMBeanInvoker.java:58)
     at com.sap.pj.jmx.mbeaninfo.AdditionalInfoProviderMBean.invoke(AdditionalInfoProviderMBean.java:289)
     at com.sap.pj.jmx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:944)
     at com.sap.pj.jmx.server.interceptor.MBeanServerWrapperInterceptor.invoke(MBeanServerWrapperInterceptor.java:288)
     at com.sap.engine.services.jmx.CompletionInterceptor.invoke(CompletionInterceptor.java:400)
     at com.sap.pj.jmx.server.interceptor.BasicMBeanServerInterceptor.invoke(BasicMBeanServerInterceptor.java:277)
     at com.sap.jmx.provider.ProviderInterceptor.invoke(ProviderInterceptor.java:255)
     at com.sap.engine.services.jmx.RedirectInterceptor.invoke(RedirectInterceptor.java:340)
     at com.sap.pj.jmx.server.interceptor.MBeanServerInterceptorChain.invoke(MBeanServerInterceptorChain.java:330)
     at com.sap.engine.services.jmx.MBeanServerSecurityWrapper.invoke(MBeanServerSecurityWrapper.java:287)
     at com.sap.engine.services.jmx.MBeanServerInvoker.invokeMbs(MBeanServerInvoker.java:157)
     at com.sap.engine.services.jmx.ClusterInterceptor.invokeMbs(ClusterInterceptor.java:220)
     at com.sap.engine.services.jmx.ClusterInterceptor.invoke(ClusterInterceptor.java:803)
     at com.sap.engine.services.jmx.MBeanServerInterceptorInvoker.invokeMbs(MBeanServerInterceptorInvoker.java:102)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImpl.invokeMbs(P4ConnectorServerImpl.java:61)
     at com.sap.engine.services.jmx.connector.p4.P4ConnectorServerImplp4_Skel.dispatch(P4ConnectorServerImplp4_Skel.java:64)
     at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:294)
     at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:183)
     at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:119)
     at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:37)
     at com.sap.engine.core.cluster.impl6.session.UnorderedChannel$MessageRunner.run(UnorderedChannel.java:71)
     at com.sap.engine.core.thread.impl3.ActionObject.run(ActionObject.java:37)
     at java.security.AccessController.doPrivileged(Native Method)
     at com.sap.engine.core.thread.impl3.SingleThread.execute(SingleThread.java:94)
     at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:162)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.init(ConnectionHashSet.java:162)
     at com.sap.engine.services.connector.jca.ConnectionHashSet.<init>(ConnectionHashSet.java:120)
     at com.sap.engine.services.connector.jca.AdapterCache.open(AdapterCache.java:207)
     at com.sap.engine.services.connector.ResourceObjectFactory.startConnectionFactory(ResourceObjectFactory.java:290)
     at com.sap.engine.services.dbpool.deploy.ContainerImpl.startDataSource(ContainerImpl.java:1540)
     ... 41 more
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.sleepClientThread(ParallelAdapter.java:230)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.runInTheSameThread(ParallelAdapter.java:111)
     at com.sap.engine.services.deploy.server.application.ParallelAdapter.makeAllPhasesAndWait(ParallelAdapter.java:212)
     at com.sap.engine.services.deploy.server.DeployServiceImpl.startApplicationAndWait(DeployServiceImpl.java:4605)
     at com.sap.engine.services.deploy.server.DeployCommunicatorImpl.startApplicationAndWait(DeployCommunicatorImpl.java:656)
     ... 31 more
Here is an export of the dataSource:
<?xml version='1.0' encoding='UTF-8'?>
<!DOCTYPE data-sources SYSTEM 'data-sources.dtd'>
<data-sources>
<application-name>myJarProject</application-name>
<data-source>
    <data-source-name>MS_SQL_DS_II</data-source-name>
    <driver-name>MSSQL</driver-name>
    <init-connections>1</init-connections>
    <max-connections>10</max-connections>
    <max-time-to-wait-connection>120</max-time-to-wait-connection>
    <expiration-control>
      <connection-lifetime>600</connection-lifetime>
      <run-cleanup-thread>300</run-cleanup-thread>
    </expiration-control>
    <sql-engine>vendor_sql</sql-engine>
    <jdbc-2.0>
      <cpds-class-name>org.apache.commons.dbcp.BasicDataSource</cpds-class-name>
      <object-factory>org.apache.commons.dbcp.BasicDataSourceFactory</object-factory>
      <properties>
        <property>
          <property-name>user</property-name>
          <property-value>juan</property-value>
        </property>
        <property>
          <property-name>password</property-name>
          <property-value>******</property-value>
        </property>
        <property>
          <property-name>portNumber</property-name>
          <property-value>1433</property-value>
        </property>
        <property>
          <property-name>database</property-name>
          <property-value>examples</property-value>
        </property>
        <property>
          <property-name>serverName</property-name>
          <property-value>p4p800d-6</property-value>
        </property>
        <property>
          <property-name>driverClassName</property-name>
          <property-value>com.jnetdirect.jsql.JSQLDriver</property-value>
        </property>
        <property>
          <property-name>username</property-name>
          <property-value>juan</property-value>
        </property>
        <property>
          <property-name>url</property-name>
          <property-value>jdbc:JSQLConnect://p4p800d-6:1433/database=examples</property-value>
        </property>
      </properties>
    </jdbc-2.0>
</data-source>
</data-sources>
Regards,
Juan Manuel

Mauricio,
you have 2 options...
     1. Try to add Reference field in the view if you can add WAERS.
      2. If you can't able to add WAERS, delete NETWR from View. Create your datasource on View (Z*). Enhance your Datasource for NETWR(use different Data Element which you can add). Populate Data using User Exit for NETWR)
all the best.
Regards,
Nagesh Ganisetti.

Advices about creating a datasource from an infoset query

Hi all,
i have to create a datasource with extraction from an infoset query in R3, i have many questions:
1- i have heard about the bad performance using a Datasource from an Infoset query, how can i improve this?
2- The infoset query doesnt exist in R3 Develop, but this exist in R3 Prod, what do i must to do? create a false infosetquery in R3 D, with just the same name of the info set query in R3 Prod? or what else?,
3- some material to improve this development about create datasources from an infoset query.
thanks guys!

Hi,
You can verywell use infoset query if you are doing following things
Join using Keyfields to retreive data from tables
If not using keyfields create index for those table fields in those fields which will improve in accessing database
Try to use minimum of tables of small size dont try to join big tables like GLPCA and all.
Try to load small set of data like a period or month. Dont try for a year or so.
if your performance is good for aperiod you can go for a year.
If you are good in function module you can try function module in which you will have the option of specifying no of records to be selected usign package size.
Hope this helps for you.
Thanks,
Arun

Error while trying to use Ant and creating Jdbc Datasource

I was following the documentation to auto-create my datasource in my weblogic server. I get an error while it is trying to link the datasource to the server. Does anybody have any ideas,it is almost like the query to get the server isn't working.
Here is my ant task:
<target name="setupJdbcDatasource">
     <wlconfig url="t3://localhost:7001" username="weblogic" password="weblogic">
     <query domain="MyDomain" type="Server" name="AdminServer" property="adminserver"/>
     <create type="JDBCConnectionPool" name="TestDatasource" property="DatasourceTest">
          <set attribute="CapacityIncrement" value="1"/>
          <set attribute="DriverName" value="weblogic.jdbcx.oracle.OracleDataSource"/>
          <set attribute="InitialCapacity" value="1"/>
          <set attribute="MaxCapacity" value="10"/>
          <set attribute="Password" value="cmuser"/>
          <set attribute="Properties" value="user=cmuser SID=ORCH serverName=10.13.5.144 portNumber=1521"/>
          <set attribute="RefreshMinutes" value="0"/>
          <set attribute="ShrinkPeriodMinutes" value="15"/>
          <set attribute="ShrinkingEnabled" value="true"/>
          <set attribute="TestConnectionsOnRelease" value="false"/>
          <set attribute="TestConnectionsOnReserve" value="false"/>
          <set attribute="URL" value="jdbc:bea:oracle://10.13.5.144:1521"/>
          <set attribute="Targets" value="${adminserver}"/>
     </create>
     </wlconfig>
</target>
My Domain is MyDomain, and server is AdminServer. The error I get is:
[wlconfig] weblogic.management.DistributedManagementException : Distributed Management [1 exceptions]
BUILD FAILED
X:\ibutt_PCView\src\CM\build.xml:285: Error invoking MBean
command: javax.management.MBeanException
And in my server log:
jdbcDataSourceBean=[MBeanServerInvocationHandler]com.bea:Name=CP-ConfigManagemen
tTest,Type=weblogic.j2ee.descriptor.wl.JDBCDataSourceBean,Parent=[MyDomain]/JDBC
SystemResources[CP-ConfigManagementTest],Path=JDBCResource
<May 21, 2006 3:50:57 PM EDT> <Warning> <JDBC> <BEA-001129> <Received exception
while creating connection for pool "ConfigManagementTest": [BEA][Oracle JDBC Dri
ver]Missing connection information: no serverName specified.>
<May 21, 2006 3:50:58 PM EDT> <Error> <Deployer> <BEA-149265> <Failure occured i
n the execution of deployment request with ID '1148241051441' for task 'weblogic
.deploy.configChangeTask.2'. Error is: 'weblogic.application.ModuleException: '
weblogic.application.ModuleException:

Hi. This seems like an XML parsing problem.
Could you please try changing the driver
properties from:
<set attribute="Properties" value="user=cmuser SID=ORCH serverName=10.13.5.144 portNumber=1521"/>
to:
<set attribute="Properties" value="user=cmuser SID=ORCH"/>
The server and port are already in the URL
thanks,
Joe

Problem in creating a generic datasource with infoset

Dear Expert,
I have to create a generic datasource with infoset. I linked the infoset with a test program below. In the program, I have one selection option, which is s_order. After creating an infoset and a datasource, this selection option 'SELECT_S_ORDER' is added to my extract structure. However, after try filtering with this SELECT_S_ORDER, it doesn't filter data at all. Why? I want to filter data with my s_order.
REPORT ZBI_DS_TEST.
tables: vbak.
* DATA
field-symbols: <vbak> type vbak.
data:   t_vbak      type table of vbak,
            w_vbak     type vbak,
            t_vbak2    type table of vbak,
            w_vbak2    type vbak.
* SELECT-OPTIONS
selection-screen begin of block b1 with frame title text-001.
    select-options: s_order   for vbak-vbeln.
selection-screen end of block b1.
    start-of-selection.
* <Query_head>
   perform sub_select_data.
   loop at t_vbak into w_vbak2.
     move-corresponding w_vbak2 to vbak.
* <Query_body>
   endloop.
*&      Form sub_select_data
*      Select data
FORM sub_select_data .
    select *
    into    table t_vbak
    from   vbak
    where vtweg = 'IP'.
ENDFORM.                    " sub_select_data

What do you mean by linking program with infoset?
Do you get the field in your RSA3 Tcode?

Create datasource with quant / curr fields

Hi,
I've created a view on EKET with all fields of EKET.
Now I want to create a datasource of the view of the EKET but I can't because of the QUANT fields ....
Can I solve this ?
Thanks !

It's OK, I found it myself.
Thanks,

Generic Datasource with Fuction Module with delta on Created Date

Hi Experts,
I have created a generic datasource using Function Module RSAX_BIW_GET_DATA. I have copied this function module and created a my own Function Module. I want to load delta using this. But I don't know how to handle delta in the code.
my code is working for full load but not for delta. I have seen that in ROOSOURCE tabel the Delta field is showing the AIE instead of D and extraction method is showing as F2. I have searched a lot of forums and articles but didn't get how to handle this.
Please advice.

Hi Amit,
Go through the link as suggested by AKhan which lets you understand the concept of offsets and the last extraction status.
In case of Table or View based GDS, the system takes care of the deltas based on the selections you make in the "Generic Delta" screen whereas in case of FM based DS, it is your responsibility to handle this part. Within your code, capture if the load is a Delta load (I_UPDMODE = D). Since your delta is on Created Date, maintain a Z table with name of the DS as the Key and a field representing the current value of the Delta field(created date in this case). When you first load the delta, there will be no record for your DS in this table. Create an entry with the current day. Next time when you load a delta, take this value, compare it with sy-datum and get all the records falling within these days. This has to be done in the Select stmt. Once selection happens, replace the value in the Z table with sy-datum. This way you can simulate the delta. The Z table can be used for other FM based Datasources also as it has DS as the key.
It would be easy if the exact SAP table where RSA7 delta field status is stored is known. Otherwise, the above method can be used.
Revert for any further queries.

Create a datasource at deploy time

Hello. I'm new to EJB3.
I've developed an application with a datasource (JAVADB) running on netbeans 5.5.1 and sun application server 9. It works well.
Next y try to deploy the .ear file into another application server and get the error "can't find jndi datasource". That's Ok, because this datasource doesn't exist on the second application server. How can i create a new database and datasource while deploy the .ear file?
Thanks.

Hi, thanks for your help!
I'll try to explain my problem again.
I have netbeans 5.5.1 and i've already configured a datasource so my application can use it.
The problem comes when i try to deploy the ear file into another app server that have not already configured the datasource that my application use. And i cant create it manually because it is on in my client's pc.
At this point, what i really need is create a datasource while my .ear file is deployed. The current solution that i've found is to use ant. Is there another?
Thanks a lot!

Error while creating a datasource for XMLfile in DataFederator

Hi,
I am trying to create a datasource in Data federator for XML file, when I tried to click on Generate Elements and Attributes button
Data Federator gives me error "Java.lang.reflect.InnovationTargetException".
Thanx In Advance.
Yogesh
Edited by: mahayog74 on Dec 2, 2011 11:09 AM

It looks like more of an issue with connecting to essbase, usually "java.lang.UnsatisfiedLinkError: no HspEssbaseEnv in java.library.path" means planning has not been installed or deployed correctly, what OS is it running on?
Cheers
John
http://john-goodwin.blogspot.com/

How to create a report with survey data

Hi All,
I need to create a report with survey data in below format. Can anyone help me how to display the summary in this format.
Swapna

Hi Swapna,
According to your description, you want to create a report with survey data and display the summary.
Reporting Services is used for rendering the report with data retrieved from datasource. In Reporting Services, we can retrieve data from the datasource then design a report, after the report processed, data is fixed on the report. So it’s not supported
to have the end users selection and do summary. For your requirement, it’s can’t be achieved currently.
If you have any question, please feel free to ask.
Best regards,
Qiuyun Yu
Qiuyun Yu
TechNet Community Support

Getting Error while creating Genric Datasource

Hi,
I was try to create genric extracter where i was getting error
While creating view genric extracter where i am getting error "Entry A ZV_ZFRT does not exist in DD02L - check your entry".
My requirement is need to create extracter which is getting populated from three modules like SD,MM,FI/CO.From these three module i am using several tables and some of the tables don't have relation btween these tables as like foreign key and refrence key.
Which extracter i need to create as given scenario?
Does view will fullfill with my requirement or any other extracter.
Please some one can help me in this scenario.
Answer would be great appreciate.

Hi,
Rather than writing a program write a function module. Create a structure and include all the necessary fields in the structure. Then in the function module write the logic to extract the values for those fields. While creating the datasource specify the function module and structure name.
Refer this link:
/people/siegfried.szameitat/blog/2005/09/29/generic-extraction-via-function-module
Hope this helps.
PB

Invalid Extract Structure error while creating "Generic DataSource" on a view...

Dear All,
I have created a view on following tables MARA, AFKO and MSEG. The Table/Join condition is as follow:
AFKO--AUFNR = MSEG--AUFNR
AFKO--PLNBEZ = MARA--MATNR
I have included all the fields from MSEG and other all fields from MARA and AFKO. The view is created successfully and contents/records are also being fetched/displayed from this view.
See screen shot as well:
But when I go to RSO2 to create a "Generic DataSource" on this view. I get a series of warning messages and then error message "Invalid Extract Structure" and therefore I'm unable to create my DataSource on this view. See below screen shots of warning and error messages.
Other warning messages are as follow:
Field GAMNG with reference field MEINS: Reference table MARA is replaced by ZOXPRD0150
Field PLSVB with reference field PLNME: Reference table PLKO is replaced by ZOXPRD0150
Field PLSVN with reference field PLNME: Reference table PLKO is replaced by ZOXPRD0150
Field LODIV with reference field MEINS: Reference table MARA is replaced by ZOXPRD0150
Following is the screen shot of error message:
1. How can I get rid of this error message and be able to create my "Generic DataSource" on top of this "View"?
2. What should I do to resolve the above warning and error messages?
I will appreciate your reply.
Many thanks!
Tariq Ashraf

Hi Vipul,
as you can find in CKIS table, the reference feild for value feild "WERTN" is missing.
As per the table the reference feild is HWAER. This should have been used in place of FWAER.
Try mentioning this in your view and this should work.
Also I am a little enthusiastic to know, what are you trying to get from the datasource.
If you are trying to get the cost estimate of multi level BOM, not (just one child level), then this approach may not work.
There is a BAPI that gives such itemization split. Just FYI, in case you are looking for multi level explosion.
"BAPI_COSTESTIMATE_ITEMIZATION".
Hope this helps.
Naveen.A

Create a DataSource with ant

Similar Messages

Maybe you are looking for