Datasource Definition in J2EE Admin?

Hi guys
Here is a newbie question... What is the use of defining a Datasource in the J2EE Admin gui.
When creating a communication Channel in the Integ.Builder you allways specify jdbc connect string info anyway?
Has anyone here configured XI 3.0 JDBC adapter to communicate with an Microsoft SQL Server?
Please provide information to share

Hi Tobbe,
Another example of using the datasource configured in the J2EE Admin is when you want to do a lookup of a SQL table during transformation in the mapping program (Message Mapping, XSLT or Java), you will not need to manage the connection in your mapping program (just obtain the connection object from J2EE).
By using the connection pool defined in the J2EE Admin, the JDBC connections are shared, therefore, more efficient, and also it simplfies the development.
Below are the basic configurations for MS SQLServer:
JDBC Driver:
com.microsoft.jdbc.sqlserver.SQLServerDriver
Connection:
jdbc:microsoft:sqlserver://server:port;DatabaseName=database_name
Note:  The SQLServer JDBC drivers must already been installed on the J2EE engine.
Regards,
Bill

Similar Messages

  • Advantages of using NWA over Visual J2EE Admin Tool

    Hello,
    can you please tell me What are the advantages of using NWA over Visual J2EE Admin Tool ?
    Thanks,
    Teja

    Hi
    Other then the previous reply,In simplest word we can say --now we have two way to admin the content in the landscape.
    1.If we want to do it off-line the we can do form Visual admin( works well because after modification we start the server for changes takes place)
    2. Form NWA we can do all administration with indicative navigation (quite frustrating in visual tool ) and no need to start /restart the surver
    Best Regards
    Satish Kumar

  • J2EE Admin Tool

    Hi all1 i'm working with J2EE Engine version 6.30 but its installed on a remote server, and i want to acces with the J2EE admin tool from mi pc, i have the J2EE admin 6.40 and when i'm trying to connect to the J2EE Engine 1rs gives a wraning: 'Warning: J2EE Engine kernel version is older than the version of Visual Administrator' then it continues with the logon and gives me the following error:
    'Error while connecting
    com.sap.engine.services.rmi_p4.P4RuntimeException: Unexpected exception.Nested exception is:
         java.io.InvalidClassException: com.sap.engine.services.adminadapter.descriptor.ClusterDescriptor; local class incompatible: stream classdesc serialVersionUID = -1045741131628563809, local class serialVersionUID = -7364664042028052650'
    I guess it happens because of the version, i dont know.
    If so, i wanna know if i can download the J2EE Admin Tool or if somebody can give it to me.
    thx
    rgds.
    Gregory

    Hi Ivaylo! thx.
    I did just what u are saying to me, and when i'm trying to connect from my local pc to the remote server the logon stops in 99% and in the task running appears the following message:
    'Login to Sapcfd.spo.com
    Host : Sapcfd.spo.com
    User name : G.MAYORGA
    Port : 56004
    Layer : None
    Successful !
    I hope u can help me.
    thx n rgds.
    Gregory

  • SAP J2EE Admin Port 50011, 99% it stops

    Hi,
    We have installed EP6 SP2, we tried to apply the patch for that we tried to connect to SAP J2EE Admin through port 50011, it goes till 99% and stays there. We are not able to apply the patch because of this.
    Any thoughts on this or suggestions will help us.
    Thanks
    Senthil

    Login is : "Administrator"
    Password :
    Hostname : Specify the proper host name out here
    Port number :50004 
    Refer Victor's note on how the port is calculated.  This assumes that your portal is installed on 50000, http://hostname:50000/irj should give you the portal home page. Are you able to login here?  On what basis did you choose 50011?
    Again there is no need for a password.  If you are still not able to login, check your installation.

  • J2EE admin is locked every time the application is Deployed.

    J2EE admin is locked every time the application is Deployed.
    So, the admin should be unlocked after every deployment
    Please give me why this is happning? It's very very urgent

    Hi Krishnaveni,
       Can you check for this property "No password change required" - in your visual Admin?
    For this one please follow below steps.
        Open "Visual Administrator" in that "Cluster> Server>Services-->Security Provider"
        Goto "Runtime" - tab and then "User Management". Search for the user "J2EE_Admin" and double click on the user name to get the user management property sheet. There you can find "No password change required". If it is not checked, please check that one. then that password wont expire for every deployment.
    Regards,
    Sridhar

  • J2EE\admin Location on Distributed SOLMAN/NW Install?

    I have a three server distributed install for SOLMAN - NW 7.0 EHP1 on Windows 2008.  I can't seem to locate teh path for the Java admin for the visual admin or the config tool normally located at : <Drive>:\usr\sap\<SAPSID>\<Instance_Name>\j2ee\admin\go.bat.
    I am able to launch the NW web client and admin console, but can't log in with installed users at this point, and I can't find the location mentioned above.  Can anyone advise where this path should be between the SCS, DI & CI servers? 
    thanks

    Hi Edward,
    These tools should exist on the server where you have installed the Central Instance (CI).
    Please check on the Central instance server.
    Cheers......,
    Raghu

  • Managed System Setup Wizard: which J2EE-Admin-User

    Hello,
    I'm running the managed system setup wizard in the diagnostic.
    In the setup of the parameters, I have to enter the J2EE-Admin-User. But which one?
    I tried:
    SMD_AGT_ADM (Dialog user with admin roles on both stacks)
    SMD_AGT_ADM (Communications user with admin roles on both stacks)
    The user was created by me before the setup. But regardless of the user settings, I get the following error:
    A logon failure occured on frces4139/SM7/00 (192.168.1.139).
    System Setup aborted, to prevent locking the User Account.
    Please check error details, specify a valid User/Password if necessary, and start Setup again
    Any ideas? Which user or user settings have to be maintained?
    Thanks,
    Jan

    Hello,
    I think the user you need to enter here is the j2ee_admin user or another user with SAP_J2EE_ADMIN role.
    Regards,
    Benjamin Rouger

  • XML datasource definition J2EE?

    Is there a way to define a datasource with XML?
    My admin is not working on a linux (FC5) with Sun Appserver 9
    but I am getting page translation.
    ... Cold Fusion without datasourses is like a peanut butter
    and jelly sandwich without bread .... messy

    http://www.adobe.com/cfusion/webforums/forum/messageview.cfm?catid=6&threadid=1132184&high light_key=y&keyword1=data%20source
    This is close ... it might work but I would like something
    longer lasting

  • J2ee Admin User locked on SDM Deployment - BI 7.0 and EP 7.0

    Hi,
    We had a recent issue on BI iview publishing from the BEX WAD 7.0 in our Production Portal server.
    The BEX WAD had the error " Java communication error"
    " An Error occured during communication with the BI Components of the J2ee engine"
    We traced down to identify that the current stack NW 7.0 SP14 BI Components had issues and had to patch to the next level
    However, during deployment of the patch using SDM, the components (all) failed posting the following error. The SDM deployment got struck and the J2ee Engine user j2ee_admin was locked.
    Only a restart of the j2ee engine is allowing us to get the Visual Admin connected. But the SDM deployment again is failing and admin user gets locked. Is there any tested solution to solve this.
    Kindly help asap.
    Trace:
    SDM:
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxxx] with user name: [j2ee_admin]check your login information.
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]          
    J2ee Engine:
    Error while connecting
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception while trying to get InitialContext. [Root exception is java.lang.SecurityException: com.sap.engine.services.security.exceptions.BaseSecurityException: This call must be performed from a system thread.
         at com.sap.engine.services.security.login.SecuritySession.setExpirationPeriod(SecuritySession.java:479)
         at com.sap.engine.services.security.login.TicketGenerator.getSecuritySession(TicketGenerator.java:180)
         at com.sap.engine.services.security.login.SecurityContext.load(SecurityContext.java:313)
         at com.sap.engine.services.rmi_p4.Message.loadContextObject(Message.java:345)
         at com.sap.engine.services.rmi_p4.Message.parseMessage(Message.java:239)
         at com.sap.engine.services.rmi_p4.Message.getByteArrayInputStream(Message.java:314)
         at com.sap.engine.services.rmi_p4.DispatchImpl._runInternal(DispatchImpl.java:212)
         at com.sap.engine.services.rmi_p4.DispatchImpl._run(DispatchImpl.java:200)
         at com.sap.engine.services.rmi_p4.server.P4SessionProcessor.request(P4SessionProcessor.java:136)
         at com.sap.engine.core.service630.context.cluster.session.ApplicationSessionMessageListener.process(ApplicationSessionMessageListener.java:33)
         at com.sap.engine.core.cluster.impl6.session.MessageRunner.run(MessageRunner.java:41)
         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:102)
         at com.sap.engine.core.thread.impl3.SingleThread.run(SingleThread.java:172)

    Hi Anup,
    The restart unlocks the j2ee engine admin user and i am able to login to Visual admin and SDM and not otherwise (SDM is hanged and doesnot allow another session and hence only restart helps me to get into SDM again)
    Admin Pwds reset etc from config tool secure store and all possible solutions have been tried before restart.
    However, after restart, when we try to deploy again, the deploy fails saying the same msg
    Caught exception while checking the login credentials for SAP J2EE Engine. Check whether the SAP J2EE Engine is up and running.com.sap.engine.deploy.manager.DeployManagerException: ERROR: Cannot connect to Host: [xxx] with user name: [j2ee_admin]check your login information.
    com.sap.engine.services.jndi.persistent.exceptions.NamingException: Exception during getInitialContext operation. No server is running. [Root exception is com.sap.engine.services.security.exceptions.BaseLoginException: Exception in creating new RemoteLoginContext instance.]
    Any clues ?
    Regards
    Venkat.

  • Dependency between a datasource and a J2EE application, possible?

    We have a J2EE application which makes use of a datasource. The application on startup does some database related activities using this datasource. As a result we need to make sure that the datasource should be started before our application starts. Is there some kind of dependency that we can add, through which we can tell NW to start the datasource first and then the application? We are using NW 04s SP11.

    Just to bring this topic to a logical end  - we were able to successfully deploy the application with the data-sources.xml file within the META-INF folder. The dependency is now taken care off.
    Thanks.

  • New installation question  (J2EE admin

    I just isntalled SAP WAS with the new version
    I tried successfully to get to the J@EE Engine Visual Administration GUI
    I cant connect in.  It does not come complete with connection properties like the old one did, and I dont know howto configure it.
    Could someone tell me how to connect?  How to configure the connection screen ?

    I was able to get the the J2EE engine visual Admin tool using a UID of admin, and a PW of admin.
    Not sure if this will work when I connect thre a remote client.
    Anyone have any info ?

  • J2EE Admin connection error

    I have the following scenario:
    The EP6(SP10) user admin was J2EE_ADMIN after the installation. When I changed the autentication to a LDAP Service, this user stopped working. It is ok! I went to the SAP J2EE Visual Admin with the emergency user and added another user as Administrator and it's working fine.
    All EP administration funcitions are working, but in the trace files the error described below persists.
    I think there is a place to replace this user, but I don't know where.
    How and where I can change the J2EE_ADMIN to fix this?
    Best regards,
    Adriano
    #1.5#001143594D25005E000012F0000016D40003FC424001F38F#1121786402039#com.sap.jms#sap.com/irj#com.sap.jms.server.sessioncontainer.InboundBus instance=default#v_seg-nix#0####81b28d70f86811d9b031001143594d25#Thread[Thread-55,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Plain###com.sap.jms.server.exception.JMSServerSecurityException: Cannot create connection with user J2EE_ADMIN.
    at com.sap.jms.server.service.impl.SecurityServiceImpl.checkAuthentication(SecurityServiceImpl.java:424)
    at com.sap.jms.server.sessioncontainer.handler.ConnectionHandler.onCreateRequest(ConnectionHandler.java:120)
    at com.sap.jms.server.sessioncontainer.handler.ConnectionHandler.process(ConnectionHandler.java:69)
    at com.sap.jms.server.sessioncontainer.InboundBus.process(InboundBus.java:143)
    at com.sap.jms.server.sessioncontainer.InboundBus.enqueue(InboundBus.java:116)
    at com.sap.jms.server.sessioncontainer.SessionContainer.receiveFromDispatcher(SessionContainer.java:63)
    at com.sap.jms.server.routingcontainer.RoutingContainer.receiveFromDispatcher(RoutingContainer.java:332)
    at com.sap.jms.server.JMSServerContainer.createConnection(JMSServerContainer.java:428)
    at com.sap.jms.server.ServerClientAdapter.sendAndWait(ServerClientAdapter.java:87)
    at com.sap.jms.client.connection.ConnectionFactory.sendConnectionCreateRequest(ConnectionFactory.java:375)
    at com.sap.jms.client.connection.ConnectionFactory.createConnection(ConnectionFactory.java:319)
    at com.sap.jms.client.connection.ConnectionFactory.createConnection(ConnectionFactory.java:244)
    at com.sap.jms.client.connection.QueueConnectionFactory.createQueueConnection(QueueConnectionFactory.java:70)
    at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.startRunning(RTMFMessaging.java:1095)
    at com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging$JMSPolling.run(RTMFMessaging.java:1037)
    at java.lang.Thread.run(Thread.java:534)
    Caused by: com.sap.security.core.server.userstore.UserstoreException: Could not get user J2EE_ADMIN
    at com.sap.security.core.server.userstore.UserContextUME.engineGetUserInfo(UserContextUME.java:187)
    at com.sap.engine.services.security.userstore.context.UserContext.getUserInfo(UserContext.java:87)
    at com.sap.jms.server.service.impl.SecurityServiceImpl.checkAuthentication(SecurityServiceImpl.java:418)
    ... 15 more
    Caused by: com.sap.security.api.NoSuchUserAccountException: USER_AUTH_FAILED: User account for logonid "J2EE_ADMIN" not found!
    at com.sap.security.core.imp.AbstractUserAccount.<init>(AbstractUserAccount.java:334)
    at com.sap.security.core.imp.DBTextFileUserAccount.<init>(DBTextFileUserAccount.java:56)
    at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:339)
    at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:277)
    at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:371)
    at com.sap.security.core.imp.UserAccountFactory.getUserAccountByLogonId(UserAccountFactory.java:366)
    at com.sap.security.core.server.userstore.UserContextUME.engineGetUserInfo(UserContextUME.java:183)
    ... 17 more
    #1.5#001143594D25005E000012F1000016D40003FC424001F8D8#1121786402039#com.sap.jms.client.connection.ConnectionFactory#sap.com/irj#com.sap.jms.client.connection.ConnectionFactory.checkForException#v_seg-nix#0####81b28d70f86811d9b031001143594d25#Thread[Thread-55,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Fatal#1#/Applcations/JMS#Plain###Failed to create connection! Reason: Cannot create connection with user J2EE_ADMIN.#
    #1.5#001143594D25005E000012F2000016D40003FC424001F98D#1121786402039#com.sap.ip.collaboration.rtc#sap.com/irj#com.sap.ip.collaboration.rtc.class com.sap.ip.collaboration.core.api.rtmf.core.RTMFMessaging.JMSPolling.startRunning()#v_seg-nix#0####81b28d70f86811d9b031001143594d25#Thread[Thread-55,5,SAPEngine_Application_Thread[impl:3]_Group]##0#0#Error##Java###Exception in method: javax.jms.JMSSecurityException: Cannot create connection with user J2EE_ADMIN.##

    Hi Christoph,
    If you want to make the connection using the message server HTTP port, I don't think there is a solution to the problem.  The SolMan's J2EE message server will reply to the agent with the P4 connection information for a specific app server (e.g. load balancing across several J2EE instances on your SolMan if you have them), and then the agent will attempt to connect to the instance using the P4 protocol.  
    If it's just a name resolution issue, and you really want the agent to connect to an instance using a virtual hostname, then Purnachand's suggested workaround to connect directly to the P4 port (rather than to the message server) should have worked.  You should run smdsetup and provide the virtual hostname and the P4 port.  The connection will not be load-balanced -- the agent will always connect to the instance corresponding to the virtual hostname. This technique requires avoiding the automated connection wizard and using the smdsetup script exclusively (since the automated connection wizard does not yet support direct P4 connections last time I checked).
    You also say "there is the p4-port locked" --- if you mean, firewalls prevent P4 connections regardless of the hostname (physical or virtual), you will need to take a different approach.  Your best bet would be to tunnel your diagnostics agents through a saprouter.  In this case the agents would connect to the saprouter on port 3299, and the saprouter would complete the p4 connection to the physical instance.  As far as I know this is the only supported way for diagnostics agents to traverse a firewall.
    I hope this helps and good luck!

  • Unable to see tables or views in DataSource definition

    Hello,
    I have configured and tested my Gateway.    I am able to create a data source to the AdventureWorksDW2012 sample database and store the credentials.   However I can't see any tables or views to select.   I checked the data
    types and table restrictions and they don't not appear to be the culprit.   Will you help me be able to see the tables/views?   I have tried with both SQL Server native and OLEDB protocols.  I am using a sql server database account
    over HTTP.
    I followed these guides to get to this point.
    http://office.microsoft.com/en-us/create-a-data-source-and-enable-odata-feed-in-the-power-bi-admin-center-HA104079172.aspx
    http://office.microsoft.com/en-us/install-configure-and-register-data-management-gateway-HA104093659.aspx
    Picture of where I need to see some available tables/views.

    could you please try:
    1. re-store the credential
    if 1. does not help, please go to the gateway machine, and check the event log under
    Application and Services Logs\Data Management Gateway, see if there is any helpful message.
    if you still have problem, feel free to send an email to huyua[at]microsoft.com with following infomation:
    1. your tenant domain name, something like yourdomain.onmicrosoft.com
    2. your data source name

  • Error: SQR configuration and the BRB datasource definition..

    <p>Hello,</p><p> </p><p>I've had Hyperion installed on my computer for about 6 months. Ihave two existing connections to seperate servers with DB2databases. I use existing ODBC drivers for the connection. I wastrying to install a third connection to a server/database and madesome changes to perhaps the driver. When I try to run a report nowI seem to connect and get an error : Failed to produce HTML outputfile. Most likely causes include: SQR configuration and the BRBdatasource definition used for this report. I get this error forall the connections now. I've tried unistalling and reinstallingthe software. I've checked the SQRDIR and BRIO_HOME and they seemedgood. I have the server installed on my computer.</p><p> </p><p>Are there  any suggestions as to what I might have done tocreate this error?</p><p> </p><p>Thank you,</p><p> </p><p>Sheila</p>

    What is the content of the file %PS_HOME%/sqr/opsys.sqc ? What version of Windows ?
    How many processes are running simultaneously ?
    Did you try to run it manually ?
    Nicolas.

  • J2EE Admin not running

    Hi,
    Unable to start J2EE Visual Administrator.
    I see the following error in the log file.
    <b>Caller J2EE_ADMIN not authorized, only role administrators is allowed to access JMX#</b>
    Any inputs are greatly appreciated.
    Regards,
    Saahil

    Hi,
    Go to tcode :SU01 in ABAP Stack and check the USER: J2EE_ADMIN has Role assigned or not.If not assign the below Role.
      Role Name : SAP_J2EE_ADMIN with green colour.
    Regards,
    Venugopal.

Maybe you are looking for