Managing SessionID with DI Server

I am building a webshop and I want people to be able to browse the shop anonymously or logged in. I wanted to use some sort of ticket mechanism. If you're logged in, you're assigned a GUID, if you're anonymous (default) you get GUID.Empty (0000-0000-0000000000-0000). In a database I look up the SAP sessionID and include that sessionID in my SOAP message. Works like a charm for one person.
Now I'm testing and when I create the '0-ticket', a sessionID is generated for my request (like it has always done). So far so good. When a collegue does something anonymously while I'm testing, he gets a 'Invalid SessionID' error. The conclusion we come to is this: A sessionID includes some information about a PC (IP, MAC-address or whatever) and can only be used by one single PC/person.
An alternative is to create a new sessionID for every request, but when you do that, the connection pool will be empty at some point and you'll have to wait for the older sessionID's to timeout and turn invalid, which is obviously not an option.
I'm looking for a good way to manage and reuse sessionID's. One solution could be to store something unique in the database as well, so I can retrieve the proper ticket for a person when I query on that unique field/value. Do you guys have an idea how to do this? Perhaps you have created a mechanism that could be useful in this scenario?!
Thanks a lot for your time!
Vincent

Vincent,
Im doing it with sesions (when user isnt logged, the session is blank, when is logged, the session contains the code if logged user) or in combination with cookies on client pc. Disadvantage of session is, that youll have set on iis big time for keeping sessions active (I have 4 hours) - this you can eliminate with some auto refresh part of pages for each one minnute - the session will keep active.
Disadvantage of cookies is, that user should have enabled working with cookies on pc.
Hope its you are asking for

Similar Messages

Syclo : Error in connecting Work Manager Client with Agentry Server

Hi,
Can somebody please shed some light on work manager client-server connections? I have downloaded the "SAP_WORK_MANAGER_BY_SYCLO_5.2" package from market place and set up the Work Manager server. It can successfully connect to the SAP back-end. Environment variables are correctly set too. However, I'm failing to connect to the Work Manager server from the Work Manager clients. I have tried from the Win32 & Android clients both.
For Win32 client, the error I'm getting is:
For Android, I can't even see the server instance, although it's running (it shows up while attempting to connect from Win32). Error:
When I attempt to connect from Work Manager client to the server, it asks for username/password and for Android client it asks for Agentry user id and password. Aren't these username/password of the server where my Work Manager (Agentry) server is installed?
Also, the "Agentry Development Server" which has been set to run as a service runs with Administrative privileges.
I followed this: http://wiki.scn.sap.com/wiki/display/SAPMOB/Agentry+error+Client+Receiving+RFC+ERROR+LOGON+FAILURE+incomplete+logon+Data+when+connecting+to+server
It didn't help. Please let me know where I'm going wrong?
Tags edited by: Michael Appleby

Hi Michael,
I can login to SAP backend using the credentials mentioned in JavaBE.ini file.
Please take a look at the JavaBE.ini:
[HOST]
server=<SAP server host name>
; mobile application name configured in sap like SMART_WORK_MANAGER_51, SMART_CUSTOMER_SERVICE_10, SMART_ISU_WORK_MANAGER_10...etc
APPNAME=SMART_WORK_MANAGER_52
[CONFIG]
; Used to get the SAP Configutaions from SAP if source=SAP or from JavaBE ini file
; SAP Configurations are [ENABLE_TABLE], [TABLE_CHECK], [TABLE_REFRESH], [BAPI_WRAPPER],
; [SAPOBJECT], [CT_SAPOBJECT], [CT_BAPI_WRAPPER], [CT_RETURN_TABLE], [CT_DELETE_TABLE].....etc
source=SAP
[TEST_LOGON]
UID=
UPASSWORD=
UGUID=
SERVERSERIALNUM=
; Service login user is used to get the SAP Configutaions from SAP if source=SAP
; Set ENABLED=true if source=SAP or ENABLED=false if source=INI
; If ENABLED=true, set the UID, UPASSWORD and SERVERSERIALNUM
; SERVERSERIALNUM is the Agentry server serial number
[SERVICE_LOGON]
ENABLED=true
UID=<SAP backend username>
UPASSWORD=<SAP backend password>
UPASSWORDENCODED=false
SERVERSERIALNUM=AVKNN@NILKGGBTLD
[PUSH_LOGON]
ENABLED=false
UID=
UPASSWORD=
UPASSWORDENCODED=false
SHAREDCONNECTION=10
[CLIENT_NUM]
CLIENT=720
;CLIENT=010
[SYSTEM_NUM]
;SYSNUM=33
SYSNUM=00
[LANGUAGE]
LANG=EN
[LOGGING]
;1=Fatal, 2=Error, 3=Warning, 4=Info, 5=debug, 6=trace
Level=4
[LOGON_METHOD]
; USER_AUTH if standard UID/Password authentication is used
; USER_AUTH_GLOBAL if pooled connections using single UID/Password is used
; USER_AUTH_GROUP if UID/Password authentication with SAP Message Server
; (load balancing) is used
LOGON_METHOD=USER_AUTH
[GLOBAL_LOGON]
; referenced when LOGON_METHOD=USER_AUTH_GLOBAL
; uses a pool of connections to the SAP backend all utilizing a single
; UID/password
UID=
UPASSWORD=
SHAREDCONNECTION=100
[GROUP_LOGON]
; referenced when LOGON_METHOD=USER_AUTH_GROUP
; individual user authentication using an SAP Message Server which distributes
; client connections among a "group" of SAP application servers based on load
; balancing criteria
; host name or IP address of SAP Message Server
MESSAGE_SERVER=
GROUP_NAME=
SYSTEM_ID=
CLIENT=
[REQUIRED_BAPI_WRAPPER]
com.syclo.sap.bapi.LoginCheckBAPI=/SYCLO/CORE_SUSR_LOGIN_CHECK
com.syclo.sap.bapi.RemoteUserCreateBAPI=/SYCLO/CORE_MDW_SESSION1_CRT
com.syclo.sap.bapi.RemoteParameterGetBAPI=/SYCLO/CORE_MDW_PARAMETER_GET
com.syclo.sap.bapi.SystemInfoBAPI=/SYCLO/CORE_SYSTINFO_GET
com.syclo.sap.bapi.ChangePasswordBAPI=/SYCLO/CORE_SUSR_CHANGE_PASSWD
com.syclo.sap.bapi.CTConfirmationBAPI=/SYCLO/CORE_OUTB_MSG_STAT_UPD
com.syclo.sap.bapi.DTBAPI=/SYCLO/CORE_DT_GET
com.syclo.sap.bapi.GetEmployeeDataBAPI=/SYCLO/HR_EMPLOYEE_DATA_GET
com.syclo.sap.bapi.GetUserDetailBAPI=/SYCLO/CORE_USER_GET_DETAIL
com.syclo.sap.bapi.GetUserProfileDataBAPI=/SYCLO/CORE_USER_PROFILE_GET
com.syclo.sap.bapi.PushStatusUpdateBAPI=/SYCLO/CORE_PUSH_STAT_UPD
com.syclo.sap.bapi.RemoteObjectCreateBAPI=/SYCLO/CORE_MDW_USR_OBJ_CRT
com.syclo.sap.bapi.RemoteObjectDeleteBAPI=/SYCLO/CORE_MDW_USR_OBJ_DEL
com.syclo.sap.bapi.RemoteObjectGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
com.syclo.sap.bapi.RemoteObjectUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.RemoteReferenceCreateBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_CRT
com.syclo.sap.bapi.RemoteReferenceDeleteBAPI=/SYCLO/CORE_MDW_USR_KEYMAP_DEL
com.syclo.sap.bapi.RemoteReferenceGetBAPI=/SYCLO/CORE_MDW_SESSION_GET
com.syclo.sap.bapi.RemoteReferenceUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.RemoteSessionDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
com.syclo.sap.bapi.RemoteUserDeleteBAPI=/SYCLO/CORE_MDW_SESSION1_DEL
com.syclo.sap.bapi.RemoteUserUpdateBAPI=/SYCLO/CORE_MDW_SESSION_UPD
com.syclo.sap.bapi.TransactionCommitBAPI=WFD_TRANSACTION_COMMIT
com.syclo.sap.bapi.SignatureCaptureBAPI=/SYCLO/CS_DOBDSDOCUMENT_CRT
I haven't yet installed ATE and tested out any application. I just want my connections to be perfect, first.
I have a question. Are the credentials used to connect Work Manager client to the server, same as the SAP backend credentials or are they the credentials of the host on which the Work Manager server is installed?
I have tried logging in using the SAP credentials also. But that results in error too.
These credentials are valid for SAP backend and successfully logs onto it and also responds correctly to connectTest.bat. However, I think this error is logical because these are the credentials for SAP backend and not the server where Work Manager server is hosted.

Hyper-V host fails with "RPC Server unavailable" error when I try to promote Windows Server in virtual machine to a domain controller

Host: Windows Server 2012 R2 with Hyper-V and RRAS (for Internet over NAT)
VM: Windows Server 2012 R2 with installed Active Directory Domain Services
When I open AD DS configuration window (“promote this server to a domain controller”) many services and programs on my host (include Hyper-V, RRAS & Server Manager) fails with RPC Server unavailable error.

Hello Aleksandr,
There wasn't any configuration information, ipconfig /all, network setup, etc. So it's difficult to tell.
More importantly, are you trying to promote the host server? If yes, that is not advised, for one, because it's a Hyper-V server, (not suggested at all), and two, RRAS is installed. RRAS is problematic with any domain controller because it turns it into
a multihomed domain controller.
Active Directory communication fails on multihomed domain controllers
http://support.microsoft.com/kb/272294/
Multihomed DCs (with more than one unteamed NIC or multiple IPs) with DNS, RRAS, iSCSI, Clustering interfaces, management interfaces, backup interfaces, and/or PPPoE adapters - A multihomed DC is not a recommended configuration, however there are ways to
configure a DC with registry mods:
http://blogs.msmvps.com/acefekay/2009/08/17/multihomed-dcs-with-dns-rras-and-or-pppoe-adapters/
7 Reasons not to Make Hyper-V a Domain Controller
http://www.altaro.com/hyper-v/reasons-not-to-make-hyper-v-a-domain-controller/
Domain Controller as Hyper-V host
https://social.technet.microsoft.com/Forums/windowsserver/en-US/4ff14bec-a815-473b-8d2a-33e91e17197b/domain-controller-as-hyperv-host?forum=winserverhyperv
Networking?
I don't know how your networking is setup, whether there are multiple NICs on the host server, if they are teamed, if you have the host interface set to allow the operating system to share administration, or if there are separate interfaces for each. Can
the host OS ping/communicate with the DC virtual machine?
If there are more than one NIC, you have the choice to team the NICs and share the Teamed NICs for the Hyper-V OS and the VMs, or keep them separate where one is devoted for the Hyper-V OS, and one for the VMs.
Hyper-V Server VLAN Network Configuration
https://social.technet.microsoft.com/Forums/windowsserver/en-US/0aa71d2a-ebf9-4a3e-bbf5-94db55339fa2/hyperv-server-vlan-network-configuration?forum=winserverhyperv
Recommendation:
Why not just create another VM DC?
Ace Fekay
MVP, MCT, MCSE 2012, MCITP EA & MCTS Windows 2008/R2, Exchange 2013, 2010 EA & 2007, MCSE & MCSA 2003/2000, MCSA Messaging 2003
Microsoft Certified Trainer
Microsoft MVP - Directory Services
Complete List of Technical Blogs: http://www.delawarecountycomputerconsulting.com/technicalblogs.php
This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Error in communicating with DCR server (Operations Manager 8.5)

Hi,
I just installed Operations Manager 8.5 on a new server. And, although I'm able to login to the OM, I'm unable to add any devices to the DCR. When attempting to add the device the following error is returned:
"Error in communicating with DCR Server
DCR Server may be down. Please start DCR server and then refresh the page. "
The same error is returned when an attempt is made toaccess the screen to change the mode (standalone/master/slave.) However, according to pdshow output DCRServer is up and running:
Process= DCRServer
State = Running normally
Pid    = 9220
RC     = 0
Signo = 0
Start = 7/29/2011 2:46:33 PM
Stop   = Not applicable
Core   = Not applicable
Info   = DCRServer is up and running
I've browsed the site and tried all suggestions for LMS since I didn't see any for OM. No success.
Any/all suggestions are much appreciated.
Kind regards,
Bart

It appears the answer is rather simple. According to a trusted source who works for a Cisco training partner, one must wait before even attempting a login into OM.
Apparently, it takes about 25 to 30 minutes for all the services to start. Any attempt to login to the OM may corrupt the database. This is based on CiscoWorks. When command "net stop crmdmgtd" is issued it takes about 5 minutes to stop the service and a confirmaiton that the service was stopped is displayed. However, when starting the service with "net start crmdmgtd" there is no confirmation that it started successfully. One may look into ":\ program Files\CSCOpx\objects\dmgt\ready" directory for a _lock file." As long as the lock file is present one shouldn't use the browser to login. However, I was advised the best approach is to restart the service and give it 30 minutes.
It worked for me
Kind regards,
Bart.

Deployment Manager Error with Oracle Weblogic Server 10.3.1

I have installed Identity Manager 9.1.0.2 (patch upgraded from 9.1.0.1) on OEL 5.3 64bit and Weblogic 10.3.1
Database:Oracle 11gR2 (remote machine).
**I am aware that IM 9.1.0.2 is not certified on Weblogic 10.3.1 (it is only certified on 10.3),
The installation was successful and OIManager is up and running. Able to create Users, Resources etc. as well.
As part of configuring OIM Connectors tried to Import .xml file using Import option from Deployment Management section as below and the following error was displayed.
"Either your session timed out or you are trying to access a page without logging in".
Did all workarounds like enabling java, changing browsers, restarting machine etc as per the below discussion but in vain.
Deployment Manager Error with Oracle Weblogic Server
Can any one suggest any workaround or solution for this problem.
Or atleast can any one confirm there is no Identity manager available on this date which is compatible with 10.3.1? and cannot be continued further.
Thanks in Advance
Sudheer
Edited by: SudheerPrabhala on Oct 20, 2009 1:26 AM

You are facing this issue because you're using a non certified combination.
Other folks who tried to use OIM in 10.3.1 ended up in the same problem you're facing.

HT4814 Is it possible to manage the mac mini server with server app before set up?

The article says using the server app I need to enter the IP address, then the Administrator name and password, but obviously on the first boot these are not configured yet. The article does not mention if this is possible or the server.app can only manage the server after its initial configuration using a monitor connected.

From dim memory... Load Server.app on the client box or use Server.app on some other handy server, and either configure DHCP with the server's MAC address (usually listed on the shipping box) and your intended static IP address and then boot the new target server box, or just boot the new target server box and use Bonjour Browser or the command-line dns-sd tool to find the IP address that the new server box has acquired from DHCP, and then in either case, connect to the new target server via Connect To Server in Server.app via its IP address, specify the root user and use the system serial number (again, usually listed on the shipping box) as the password.

For server the Node Manager associated with machine is not reachable

Hello all,
I am getting this error, when i start my Managed Server which is in shutdown state
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
The configuration details are
i am using weblogic 9.2 MP3 version in windows 2k3 server.
It has a machine vm-bea-dev, a cluster cluster-saa-dev, to which both the managed servers saa-dev-1 and saa-dev-2 are assigned. There are 3 applications deployed onto managed Server 1 and 1 for managed Server 2.
Managed Server 1 is in shutdown state, and when i start the server, it gives the error specified below
For server SAA-Dev-1, the Node Manager associated with machine vm-bea-dev is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager. No action will be performed.
The same for Managed Server 2 too, and this server is in Admin State, i dont know how it went into that state.
Can somebody please help me reslove it.
Thanks in advance

Actually the cert is coming from your Dev machine but it is sending the Prod cert.
What cert is used by your admin server ? It should match the host name.
So your Dev machine is apparently using a copy of the prod cert / keystore rather than using its own DEV cert. It's not clear from your post whether this is the nodemanager using the wrong cert, or the managed server. So both should be checked.
The managed servers need to be using a cert that matches their host name. If you have a managed server on VM-BEA-DEV, then the cert needs to be CN=VM-BEA-DEV. You can also use a load-balancer CN name in the cert if you have the cluster's HTTP values set to match.
In your nodemanager.properties, are you explicitly accessing keystores, such as with:
KeyStores=CustomIdentityAndJavaStandardTrust
CustomIdentityAlias=some_alias
CustomIdentityKeyStoreFileName=some_path_to_keystore
CustomIdentityKeyStorePassPhrase={3DES}...
CustomIdentityKeyStoreType=jks
CustomIdentityPrivateKeyPassPhrase={3DES}
In my multi-machine clusters, I have multiple certificates such as:
admin machine1:
has a cert for use by the admin server and NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers
all other machines:
has a cert for use by NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers

MQSeries as a Transactional Resource Manager with Weblogic Server

          I am trying to setup the example given in the BEA white paper:
          Using MQSeries as a Transactional Resource Manager with Weblogic Server.
          Version 1.
          October 25, 2001.
          I followed the instructions given in the documents, but when i run client program
          >java MQClient t3://localhost:7001 "MQSeries test"
          I received the following exception below. Does anyone how what is the reason for
          this exception(s) and how i can solve the problem? My MQSeries Server and Weblogic
          6.1 sp2 are installed on seperate NT machines. I installed the MQSeries classes
          for java and the MQSeries classes for Java Message Service on the weblogic
          server machine.
          sending: "MQSEries test"
          Exception in thread "main" java.rmi.ServerError: A error occurred the server; ne
          sted exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.rmi.ServerError: A error occurred the server; nested exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          ; nested exception is:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          at java.lang.System.loadLibrary(System.java:820)
          at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          at java.security.AccessController.doPrivileged(Native Method)
          at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
          at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
          at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
          at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
          at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
          at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          <<no stack trace available>>
          --------------- nested within: ------------------
          weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
          [java.rmi.ServerError: A error occurred the server; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.rmi.ServerError: A error occurred the server; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                  at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                  at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                  at java.lang.System.loadLibrary(System.java:820)
                  at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                  at java.security.AccessController.doPrivileged(Native Method)
                  at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                  at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                  at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                  at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                  at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
                  at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
                  at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
                  at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                  at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                  at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                  at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                  at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                  at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                  at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
                  at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                  at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                  at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                  at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                  at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                  at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
                  at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                  at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          ; nested exception is:
                  java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          Start server side stack trace:
          java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
                  at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
                  at java.lang.Runtime.loadLibrary0(Runtime.java:749)
                  at java.lang.System.loadLibrary(System.java:820)
                  at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
                  at java.security.AccessController.doPrivileged(Native Method)
                  at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
                  at com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
                  at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
                  at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          149)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          tion(MQBindingsManagedConnectionFactoryJ11.java:139)
                  at com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          ion(MQBindingsManagedConnectionFactoryJ11.java:157)
                  at com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          a:80)
                  at com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          ctionManager.java:150)
                  at com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          a:666)
                  at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
                  at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
                  at com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
                  at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
                  at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
                  at com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
                  at com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
                  at com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          AQueueConnectionFactory.java:53)
                  at weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
                  at MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
                  at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
                  at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
                  at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
                  at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          a:267)
                  at weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          .java:22)
                  at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
                  at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          End server side stack trace
          at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
          at $Proxy1.bridgeWLS2MQS(Unknown Source)
          at MQClient.main(MQClient.java:54)


The point is that over TCPIP the MQ XA connection factory is not available.
          The MQ shared memory/JNI driver is required to access it, which limits
          access to those processes that are on the same box as the MQ q manager.
          This is an MQ series limitation.
          Douglas WF Acheson wrote:
          > Hello,
          >
          > If memory server me correct, default connection to MQ Series is through
          > JNI calls and shared memory. You have to change the protocol to TCPIP when
          > connection to the queue manager on another box (do not know much about XA
          > with MQ Series); that is when you connect to MQ Series vi JMS on another
          > box you must do something like the following:
          >
          > qcf = new MQQueueConnectionFactory() ;
          > qcf.setHostName(hostName) ;
          > qcf.setPort(port) ;
          > qcf.setTransportType(JMSC.MQJMS_TP_CLIENT_MQ_TCPIP) ;
          > qcf.setQueueManager(qManagerName) ;
          >
          > Then when you create you queues, sesions etc. you are point at the correct Q
          > manager.
          >
          > Hope this helps ...
          >
          > Douglas WF Acheson
          >
          > "Raja Mukherjee" <[email protected]> wrote in message
          > news:[email protected]...
          > > On a closer look at the original post (sorry for missing that, it was
          > early
          > > in the morning), you would not be able to use XA if your QM and WLS are in
          > > different boxes. Check on this newsgroup, there are several posts on this
          > > subject. The whitepaper, if I recall correctly, installs both MQ and WLS
          > on
          > > the sames box. This is a MQSeries limitation not WLS.
          > >
          > > .raja
          > >
          > >
          > > "ibrahim Nehme" <[email protected]> wrote in message
          > > news:[email protected]...
          > > >
          > > > I am trying to setup the example given in the BEA white paper:
          > > > Using MQSeries as a Transactional Resource Manager with Weblogic Server.
          > > > Version 1.
          > > > October 25, 2001.
          > > > I followed the instructions given in the documents, but when i run
          > client
          > > program
          > > >
          > > > >java MQClient t3://localhost:7001 "MQSeries test"
          > > > I received the following exception below. Does anyone how what is the
          > > reason for
          > > >
          > > > this exception(s) and how i can solve the problem? My MQSeries Server
          > and
          > > Weblogic
          > > > 6.1 sp2 are installed on seperate NT machines. I installed the MQSeries
          > > classes
          > > > for java and the MQSeries classes for Java Message Service on the
          > weblogic
          > > > server machine.
          > > > ---------------------------------------
          > > > sending: "MQSEries test"
          > > > Exception in thread "main" java.rmi.ServerError: A error occurred the
          > > server; ne
          > > > sted exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.rmi.ServerError: A error occurred the server; nested exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ; nested exception is:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > >
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > > at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > > at java.lang.System.loadLibrary(System.java:820)
          > > > at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > > at java.security.AccessController.doPrivileged(Native Method)
          > > > at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > > at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > > at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > > at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > > at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > > at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > > at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > > at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > > at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > > at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > > at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > > at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > > at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > > at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > > at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > > at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > > at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > > at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > > at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > > at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > > at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > > at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > > at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > >
          > > > <<no stack trace available>>
          > > > --------------- nested within: ------------------
          > > > weblogic.rmi.extensions.RemoteRuntimeException - with nested exception:
          > > > [java.rmi.ServerError: A error occurred the server; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.rmi.ServerError: A error occurred the server; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > >         at java.lang.System.loadLibrary(System.java:820)
          > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > >         at java.security.AccessController.doPrivileged(Native Method)
          > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > >         at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > >         at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > >         at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > >         at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > >         at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > >         at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > >         at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > >         at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > >         at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ; nested exception is:
          > > >         java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >
          > > > Start server side stack trace:
          > > > java.lang.UnsatisfiedLinkError: no mqjbnd04 in java.library.path
          > > >         at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1312)
          > > >         at java.lang.Runtime.loadLibrary0(Runtime.java:749)
          > > >         at java.lang.System.loadLibrary(System.java:820)
          > > >         at com.ibm.mq.server.MQSESSION$1.run(MQSESSION.java:179)
          > > >         at java.security.AccessController.doPrivileged(Native Method)
          > > >         at com.ibm.mq.server.MQSESSION.<clinit>(MQSESSION.java:175)
          > > >         at
          > > com.ibm.mq.MQSESSIONServer.getMQSESSION(MQSESSIONServer.java:67)
          > > >         at com.ibm.mq.MQSESSION.getSession(MQSESSION.java:329)
          > > >         at
          > > com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:
          > > > 149)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11._createManagedConnec
          > > > tion(MQBindingsManagedConnectionFactoryJ11.java:139)
          > > >         at
          > > com.ibm.mq.MQBindingsManagedConnectionFactoryJ11.createManagedConnect
          > > > ion(MQBindingsManagedConnectionFactoryJ11.java:157)
          > > >         at
          > > com.ibm.mq.StoredManagedConnection.<init>(StoredManagedConnection.jav
          > > > a:80)
          > > >         at
          > > com.ibm.mq.MQSimpleConnectionManager.allocateConnection(MQSimpleConne
          > > > ctionManager.java:150)
          > > >         at
          > > com.ibm.mq.MQQueueManager.obtainBaseMQQueueManager(MQQueueManager.jav
          > > > a:666)
          > > >         at com.ibm.mq.MQQueueManager.construct(MQQueueManager.java:615)
          > > >         at com.ibm.mq.MQQueueManager.<init>(MQQueueManager.java:436)
          > > >         at
          > com.ibm.mq.MQSPIQueueManager.<init>(MQSPIQueueManager.java:52)
          > > >         at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1067)
          > > >         at com.ibm.mq.jms.MQConnection.createQMXA(MQConnection.java:757)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:209)
          > > >         at
          > > com.ibm.mq.jms.MQQueueConnection.<init>(MQQueueConnection.java:78)
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnection.<init>(MQXAQueueConnection.java:46
          > > > )
          > > >         at
          > > com.ibm.mq.jms.MQXAQueueConnectionFactory.createXAQueueConnection(MQX
          > > > AQueueConnectionFactory.java:53)
          > > >         at
          > > weblogic.jms.foreign.mqseries.WrapMQXAQueueConnectionFactory.createXA
          > > > QueueConnection(WrapMQXAQueueConnectionFactory.java:29)
          > > >         at
          > > MQSeriesHelperImpl$JMSObject.<init>(MQSeriesHelperImpl.java:237)
          > > >         at MQSeriesHelperImpl.bridgeWLS2MQS(MQSeriesHelperImpl.java:125)
          > > >         at MQSeriesHelperImpl_WLSkel.invoke(Unknown Source)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:298)
          > > >         at
          > > weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.jav
          > > > a:267)
          > > >         at
          > > weblogic.rmi.internal.BasicExecuteRequest.execute(BasicExecuteRequest
          > > > java:22)
          > > >         at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:139)
          > > >         at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          > > > End server side stack trace
          > > > ]
          > > > at weblogic.rmi.internal.ProxyStub.invoke(ProxyStub.java:60)
          > > > at $Proxy1.bridgeWLS2MQS(Unknown Source)
          > > > at MQClient.main(MQClient.java:54)
          > >
          > >

For server Eagle-PROD-Instance, the Node Manager associated with machine

I have a wlst script that creates a domain and a managed server. I associate the server with a machine that's attached to a node manager. It creates the managed server fine but when I try and start it I get this error
For server Eagle-PROD-Instance, the Node Manager associated with machine Eagle-Machine is not reachable.
All of the servers selected are currently in a state which is incompatible with this operation or are not associated with a running Node Manager or you are not authorized to perform the action requested. No action will be performed.
The machine is associated with the Node Manager and the NM is running. I can start the managed server from the command line, but not from the admin console
This is the script, am I missing something?
Thanks
name: createManagedServer.py
description: This script create the weblogic domain, and executes each weblogic queue module
subfile. it reads a property file : weblogic_wlst.properties for server domain information
author     : mike reynolds - edifecs 2011
created     : April 8th 2011
import sys
from java.lang import System
from java.util import Properties
from java.io import FileInputStream
from java.io import File
from weblogic.management.security.authentication import UserEditorMBean
from weblogic.management.security.authentication import GroupEditorMBean
from weblogic.management.security.authentication import UserPasswordEditorMBean
# Loads the contents a properties file into a java.util.Properties
# configPropFile = "weblogic_wlst.properties"
def loadPropertiesFromFile(configPropFile):
     configProps = Properties()
     propInputStream = FileInputStream(configPropFile)
     configProps.load(propInputStream)
     propInputStream.close()
     return configProps
def getProperties():
     importConfigFile = sys.argv[1]
     print importConfigFile
     domainProps = loadPropertiesFromFile(importConfigFile)
     properties = Properties()
     input = FileInputStream(importConfigFile)
     properties.load(input)
     input.close()
     return properties
def create_users(username, password, description):
# create admin user
cmo.getFileRealms()
try:
userObject=cmo.getSecurityConfiguration().getDefaultRealm().lookupAuthenticationProvider("DefaultAuthenticator")
userObject.createUser(username,password,description)
print "Created user " + username + "successfully"
except:
print "check to see if user " + username + " exists "
def add_user_to_group(username):
print "Adding a user to group ..."
cmo.getFileRealms()
try:
userObject2 = cmo.getSecurityConfiguration().getDefaultRealm().lookupAuthenticationProvider("DefaultAuthenticator")
userObject2.addMemberToGroup('Administrators',username)
print "Done adding user " + username
except:
print "check to see if user " + username + " is already in group "
def connect_server(user,pw,url):
          connect(user,pw,url)
def create_machine():
try:
print 'Creating machine' + machine
# cd('/')
# create(machine, 'Machine')
mach = cmo.createUnixMachine(machine)
mach.setPostBindUIDEnabled(true)
mach.setPostBindUID('oracle')
mach.setPostBindGIDEnabled(true)
mach.setPostBindGID('oracle')
mach.getNodeManager().setNMType('ssl')
except:
     print "machine exists"
def build_domain():
### Read Basic Template
WL_HOME = "C:/Oracle/Middleware/wlserver_10.3"
readTemplate(WL_HOME+"/common/templates/domains/wls.jar")
template=WL_HOME+"/common/templates/domains/wls.jar"
cd('Servers/AdminServer')
set('ListenAddress', adminServerAddress)
set('ListenPort', int(adminServerPort))
cd('/')
cd('/Security/base_domain/User/weblogic')
cmo.setPassword('w3bl0g1c')
### Write Domain
setOption('OverwriteDomain', 'true')
print "writing domain " + domainDir + domainName
writeDomain(domainDir+'/'+domainName)
closeTemplate()
create_machine()
arg = "Arguments=\" -server -Xms256m -Xmx768m -XX:MaxPermSize=256m -da\""
prps = makePropertiesObject (arg)
domain = domainDir + domainName
try:
     #startNodeManager()
#nmConnect('weblogic', 'w3bl0g1c', host, 5556, 'AdminServer', domain, 'ssl')
# nmStart('AdminServer')
startServer('AdminServer', domainName, url, adminUser, adminPassword, domainDir, 'true')
except:
print "could not connect to Node Manager"
def create_server():
# get server instance properties
name = properties.getProperty("serverName")
domain = properties.getProperty("domainName")
port = properties.getProperty("listenPort")
address = properties.getProperty("listenAddress")
servermb=getMBean("Servers/" + name)
machine = properties.getProperty("machineName")
nodePort = properties.getProperty("nodeManagerPort")
domainDir = properties.getProperty("domainDir")
if servermb is None:
          startEdit()
          cd('/')
          cmo.createServer(name)
          cd('/Servers/'+ name)
          cmo.setListenAddress(address)
          cmo.setListenPort(int(port))
          cd('/')
          cmo.createMachine(machine)
          cd('/Machines/' + machine + '/NodeManager/' + machine )
          cmo.setNMType('Plain')
          cmo.setListenAddress(address)
          cmo.setListenPort(int(nodePort))
          cmo.setDebugEnabled(false)
          cd('/Servers/' + name)
          cmo.setListenPortEnabled(true)
          cmo.setJavaCompiler('javac')
          cmo.setClientCertProxyEnabled(false)
          cmo.setMachine(getMBean('/Machines/' + machine ))
          cmo.setCluster(None)
          cd('/Servers/' + name + '/SSL/' + name)
          cd('/Servers/' + name + '/ServerDiagnosticConfig/' + name)
          cmo.setWLDFDiagnosticVolume('Low')
          cd('/Servers/' + name)
          cmo.setCluster(None)
          cd('/Servers/' + name + '/SSL/' + name)
          cmo.setEnabled(false)
### Executable Script
### CreateDomain.py
### Define constants
WL_HOME = "C:/Oracle/Middleware/wlserver_10.3"
print "Starting the script ..."
print "Getting properties ... "
properties = getProperties()
adminServerAddress = properties.getProperty("adminServerAddress")
adminServerPort = properties.getProperty("adminServerPort")
adminUser = properties.getProperty("adminUser")
adminPassword = properties.getProperty("adminPassword")
edifecsUser = properties.getProperty("edifecsUser")
edifecsPassword = properties.getProperty("edifecsPassword")
host = properties.getProperty("host")
domainDir = properties.getProperty("domainDir")
domainName = properties.getProperty("domainName")
user = properties.getProperty("username")
pw = properties.getProperty("passwd")
url = properties.getProperty("adminURL")
machine = properties.getProperty("machineName")
print "Building the domain..."
build_domain()
print "Connecting to server"
connect_server(adminUser, adminPassword, url)
edit()
startEdit()
# create managed server
# create_machine()
create_server()
print "Creating users"
# starting configuration tree
serverConfig()
create_users(adminUser, adminPassword, "Administrator")
add_user_to_group(adminUser)
create_users(edifecsUser, edifecsPassword,"Administrator")
add_user_to_group(edifecsUser)
# have to restart edit to save config
edit()
startEdit()
# nmKill('AdminServer')
print "saving configuration"
try:
     save()
     activate(block="true")
     print "script returns SUCCESS"
     print "admin server is running"
     print "starting server " + name
     startServer(domainName, name ,url,adminUser, adminPassword, domainDir,'true')
except:
     print "failed to save server"
     dumpStack()

Actually the cert is coming from your Dev machine but it is sending the Prod cert.
What cert is used by your admin server ? It should match the host name.
So your Dev machine is apparently using a copy of the prod cert / keystore rather than using its own DEV cert. It's not clear from your post whether this is the nodemanager using the wrong cert, or the managed server. So both should be checked.
The managed servers need to be using a cert that matches their host name. If you have a managed server on VM-BEA-DEV, then the cert needs to be CN=VM-BEA-DEV. You can also use a load-balancer CN name in the cert if you have the cluster's HTTP values set to match.
In your nodemanager.properties, are you explicitly accessing keystores, such as with:
KeyStores=CustomIdentityAndJavaStandardTrust
CustomIdentityAlias=some_alias
CustomIdentityKeyStoreFileName=some_path_to_keystore
CustomIdentityKeyStorePassPhrase={3DES}...
CustomIdentityKeyStoreType=jks
CustomIdentityPrivateKeyPassPhrase={3DES}
In my multi-machine clusters, I have multiple certificates such as:
admin machine1:
has a cert for use by the admin server and NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers
all other machines:
has a cert for use by NM that matches the host name ( with node manager.properties entries such as the above )
has a 2nd cert that matches the load-balancer name for the cluster - used by the managed servers

OVM Manager 2.2.2: server pool error with file system type

I'm just getting started with OVM. I've installed OVM on one machine and the manager on another.
I created a server pool, which seemed to work OK but shows "Error" in the table under the "Server Pools" tab in the manager interface
When I edit it I see
Error: OVM-1011 OVM Manager communication with NNN.NNN.NN.NNN for operation Pre-check cluster root for Server Pool failed: <Exception: SR '/dev/sda3' not supported: type 'ocfs2.local' not in ['nfs', 'ocfs2.cluster']>
Can anyone explain this? Does this mean I can't use a local file system in OVM 2.2.2? I understood this was the case with OVM 3, which is why I went with 2.2.2.
Thanks.

Roger Ford wrote:
Error: OVM-1011 OVM Manager communication with NNN.NNN.NN.NNN for operation Pre-check cluster root for Server Pool failed: <Exception: SR '/dev/sda3' not supported: type 'ocfs2.local' not in ['nfs', 'ocfs2.cluster']>
Can anyone explain this? Does this mean I can't use a local file system in OVM 2.2.2? I understood this was the case with OVM 3, which is why I went with 2.2.2.You can't created a clustered pool with a local filesystem. You need to format the filesystem with ocfs2 in clustered mode.

Open (.sdf) file with SQL server 2005 Management Studio

In VS2005, I have created a SQL Mobile database, (.sdf).
Copied that (.sdf) file to Desktop, and when I try to open with SQL Server 2005 management studio, its showing error "make sure the application for the file type (.sdf) is installed."
How can I open this file with SQL server?
Regards
Abinash

You must install SP2 if using Management Studio Express (http://www.microsoft.com/downloads/details.aspx?familyid=6053C6F8-82C8-479C-B25B-9ACA13141C9E&displaylang=en)Erik Ejlskov Jensen, MCTS: WM App, MCITP: SQL 2008 Dev - http://erikej.blogspot.com
Please mark as answer, if this was it.

Managing users, groups and shares with Mavervicks server

I recently upgraded from Snow Leopard Server to Mavericks.
In Snow Leopard, WorkGroup manager was the primary way to create shares, users and groups. Now it would seem that it is optional and in fact, I do not even see how to create a share in WorkGroup except for perhaps a group share which I'm not quite sure how to do.
For my setup, I have setup Open Directory and create a few Local Network users. DHCP is managed via my airport and the DNS is on but only for server and points to my Airport IP address.
QUESTIONS:
Should I be managing users with WorkGroup manager or server app, Whats the advantage?
I don't have user profiles (files) stored on the server they are local. That being the case, why does each user have a network folder on the server?
Thanks!

Workgroup Manager and MCX are deprecated. These technologies should only be used if you can not accomplish your tasks with Server.app and Profile Manager. If you have specific requirements that can not be satisfied in Server.app and Profile Manager you should send feedback to Apple.
So to your questions:
Should I be managing users with WorkGroup manager or server app, Whats the advantage?
I don't have user profiles (files) stored on the server they are local. That being the case, why does each user have a network folder on the server?
1: Ideally, no. Unless... You are supporting machines prior to 10.8.5 or can not find an equivalent function in Server.app and Profile Manager. There is no advantage to using it. Apple will eventually stop distributing it. It is available now for legacy support only. If you have a need for MCX management then WGM remains viable. But, ideally, you should be looking to Profile Manager.
2: This is because you created your accounts using Local Home Folder template instead of None - Services Only. The Local Home Folder template has the unfortunate side-effect of creating a user home folder on the server. I too dislike this. If you only want to use the accounts for services, then you should create the accounts using None - Services Only. By the way, it is safe to delete these home folders if you would like.
Reid
Apple Consultants Network
Apple Professional Services
Author "Mavericks Server – Foundation Services" :: Exclusively available in Apple's iBooks Store

Use hyper-v manager to Hyper-V server with public IP

Hello,
I have recently purchased a dedicated server online, and a fresh copy of hyper-v has been installed. This is the free version, and not what's included with Windows Server 2012 R2. I have a quick question. I can RDP into my server, which is located on the
Internet. When I try to connect an MMC snapin, like Hyper-V manager, it is inaccessible. Is there a way to manage hyper-v servers found on the Internet? And, if so, is this a good idea?
Thanks to all that reply,
Mike

Thanks for the replies,
All of these tools seem to work for computers on the same network. I am trying to connect to a hyper-v server on the Internet using hyper-v manager.
Mike
Mike,
Put your thinking cap on buddy :)
You say you can RDP to your Hyper-V host. I say do NOT do that for common daily tasks. Not a best practice.
You say you want to manage Hyper-V on your remote Hyper-V host. I say do it from a Win8.1 VM on the host.
You say I have no VMs on my new remote Hyper-V host. I say build your first VM via Powershell. Once it's done, RDP to the VM not the host, and manage the host from the VM.
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) _________________________________________________________________________________
Powershell: Learn it before it's an emergency http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx

How to Manage Pcs with a mac server mini?

one of my missions is to manage Pcs with a mac server. But since my searches are not fruitful. It is the reason why I would like to obtain from the help. Very cordially to you..

See Meraki MDM, has administration for many platforms including PC.
https://meraki.cisco.com/products/systems-manager

How to use quota on a desktop folder for all users with File Server Resource Manager.

Hi there,
I'd like to know if there is a posibility to use variables in the path with File Server Resource Manager if you want to set the quota.
The path I'd like to use is d:\home\%username%\desktop.
Like to hear from you all if there is a solution or workaround for this one :)
Thanks for your time.
Ben.
Ben van der Meer

That's a question about Automator, so I'd pop that one here
http://discussions.apple.com/forum.jspa?forumID=1339
Regards
TD

Managing SessionID with DI Server

Similar Messages

Maybe you are looking for