Einstellpa​rameter

Hallo zusammen,
wir haben Diadem10.1 als Netzwerlizenz im Einsatz und somit unterschiedliche Anmeldprofile.
Wie kann ich meine kompletten Einstellungen an andere Benutzer übergeben?
auch die Einstellunegn in "MyDataFinder" uind wenn es geht auch die Zuordnung meiner VBS Sequenzen zu den Funktionstasten!
vorab besten Dank für euere Unterstützung
Schreiner

Hallo,
die Einstellungen werden unter
C:\Dokumente und Einstellungen\<Benutzername>\Lokale Einstellungen\Anwendungsdaten\National Instruments
gespeichert. Im Ordner Shared werden die Einstellungen zum DataFinder gespeichert, im Ordner DIAdem\<Versionsnummer> die weiteren Einstellungen. Insbesondere die Datei Desktop.DDD ist für die Speicherung der Einstellungen wichtig.
Für die Übergabe der Einstellungen an andere Benutzer sollten Sie daher die Ordner "Shared" und "DIAdem" übergeben.
National Instruments
District Sales Manager

Similar Messages

  • IMac won't start with Thunderbolt Display connected after firmware update

    After updating my thunderbolt display firmware to version 1.2 this morning via the App Store, my mid-2014 iMac won't start up with the external display connected.  I can get the iMac to start up only by disconnecting the display's thunderbolt connector. After the iMac comes up, I can reconnect the display and everything appears to function normally.  I've tried several restarts and the iMac won't start up with the display connected.  Anyone else experience this?

    Hello rameta,
    It may help to reset your Mac's SMC and PRAM.
    Intel-based Macs: Resetting the System Management Controller (SMC)
    http://support.apple.com/kb/HT3964
    Reset your computer’s PRAM
    http://support.apple.com/kb/HT1379
    Cheers,
    Allen

  • Fuego.papi.ProcessNotAvailableException

    Hi guys,
    I use the ALBPM 5.7 enterprise and I want to use PAPI.
    So, I got this code from my friend. He said that this code is correct.
    But it's not working now.
    I don't know what's wrong.
    "/Process" is started on the workspace portal and its version is really 2.0.
    "mih" user has the right authority to start the process.
    This code can make a session but after then the error appears.
    Thanks.
    my source code==========================================================
    package com.bpm.ucity;
    import java.util.Properties;
    import fuego.papi.Arguments;
    import fuego.papi.InstanceInfo;
    import fuego.papi.ProcessService;
    import fuego.papi.ProcessServiceSession;
    public class StartProcess {
         public StartProcess() {
              // TODO Auto-generated constructor stub
         * @param args
         public static void main(String[] args) {
              // TODO Auto-generated method stub
              String strProcessID          = "/Process";
              String strUserName          = "mih";
              String strPassword          = "1";
              ProcessService procServ = null;
              ProcessServiceSession procServSession = null;
              InstanceInfo instInfo = null;
              try {
                   Properties prop      = new Properties();
                   prop.setProperty(ProcessService.DIRECTORY_ID, "default");
                   prop.setProperty(ProcessService.DIRECTORY_PROPERTIES_FILE, "C:/bea/albpm5.7/j2eewl/conf/directory.properties");
                   prop.setProperty(ProcessService.WORKING_FOLDER, "C:/tmp");
                   prop.setProperty("java.naming.factory.initial","weblogic.jndi.WLInitialContextFactory");
                   prop.setProperty("java.naming.provider.url","t3://localhost:7001");     
                   procServ = ProcessService.create(prop);
                   // create session
                   procServSession = procServ.createSession(strUserName, strPassword, "localhost");
                   System.out.println ("procServSession => [" + procServSession + "]" );
                   // create process instance
                   Arguments arguments = Arguments.create();
                   System.out.println ("Arguments1111111111111111=======" + arguments);
                   System.out.println ("Here I am!!!!!!" );          
                   instInfo = procServSession.createProcessInstance(strProcessID, arguments);
                   System.out.println ("instInfo => [" + instInfo + "]" );
                   String strInstanceID = instInfo.getId();
                   System.out.println ("strInstanceID => [" + strInstanceID + "]" );
              } catch (Exception e) {
                   e.printStackTrace();
              } finally {
                   procServSession.close();
    error=================================================================
    procServSession => [abstract class fuego.papi.ProcessServiceSesion]
    Arguments1111111111111111=======fuego.papi.Arguments@8ceeea
    Here I am!!!!!!
    fuego.papi.ProcessNotAvailableException: cannot use process '/Process#Default-2.0'
    at fuego.papi.impl.ProcessServiceImpl.createProcess(ProcessServiceImpl.java:1756)
    at fuego.papi.impl.ProcessServiceImpl.access$2500(ProcessServiceImpl.java:142)
    at fuego.papi.impl.ProcessServiceImpl$SessionProcessLoader.load(ProcessServiceImpl.java:3822)
    at fuego.papi.impl.ProcessManager.get(ProcessManager.java:631)
    at fuego.papi.impl.ProcessServiceImpl.getProcess(ProcessServiceImpl.java:1138)
    at fuego.papi.impl.ProcessServiceNESessionImpl.getProcess(ProcessServiceNESessionImpl.java:1069)
    at fuego.papi.impl.ProcessServiceNESessionImpl.checkBeginPermissions(ProcessServiceNESessionImpl.java:2434)
    at fuego.papi.impl.ProcessServiceNESessionImpl.createProcessInstance(ProcessServiceNESessionImpl.java:1441)
    at fuego.papi.impl.ProcessServiceNESessionImpl.createProcessInstance(ProcessServiceNESessionImpl.java:1434)
    at com.bpm.ucity.StartProcess.main(StartProcess.java:55)
    Caused by: fuego.papi.impl.EngineNotAvailableException: cannot find 'BEA_WL_Engine' EJB in 'engines/BEA_WL_Engine'
    reason: Need to specify class name in environment or system property, or as an applet parameter, or in an application resource file: check java.naming.factory.initial
    project EAR application program to be setted up and to be started
    at fuego.papi.impl.EngineNotAvailableException.cannotFindEJB(EngineNotAvailableException.java:83)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getEngineHome(J2EEEngineAccessImpl.java:286)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getSecureEngineInterface(J2EEEngineAccessImpl.java:348)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createSecureEngine(J2EEEngineAccessImpl.java:158)
    at fuego.papi.impl.ProcessServiceImpl.createSecureEngine(ProcessServiceImpl.java:1280)
    at fuego.papi.impl.ProcessServiceNESessionImpl$2.run(ProcessServiceNESessionImpl.java:2140)
    at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1578)
    at fuego.papi.impl.ProcessServiceNESessionImpl.getSecureEngine(ProcessServiceNESessionImpl.java:2148)
    at fuego.papi.impl.ProcessServiceImpl.createProcess(ProcessServiceImpl.java:1709)
    ... 9 more
    Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as a
    n applet parameter, or in an application resource file: java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
    at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.lookup(Unknown Source)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.getEngineHome(J2EEEngineAccessImpl.java:276)
    ... 16 more
    서버 동기화 정보에 대한 JMS Topic 연결이 일시적으로 중단되었습니다. 자세한 정보:주제 연결 팩토리 'XATopicConnectionFacto
    ry'을(를) 찾는 동안 오류가 발생했습니다.
    세부 사항:
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet pa
    rameter, or in an application resource file: java.naming.factory.initial
    원인: Need to specify class name in environment or system property, or as an applet parameter, or in an application reso
    urce file: java.naming.factory.initial
    fuego.papi.impl.j2ee.JMSTopicLookUpException: 주제 연결 팩토리 'XATopicConnectionFactory'을(를) 찾는 동안 오류가 발생했습니다.
    Detail:
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet pa
    rameter, or in an application resource file: java.naming.factory.initial
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:649)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.run(J2EEEngineAccessImpl.java:540)
    Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as a
    n applet parameter, or in an application resource file: java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
    at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.lookup(Unknown Source)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:640)
    ... 1 more
    서버 동기화 정보에 대한 JMS Topic 연결이 일시적으로 중단되었습니다. 자세한 정보:주제 연결 팩토리 'XATopicConnectionFacto
    ry'을(를) 찾는 동안 오류가 발생했습니다.
    세부 사항:
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet pa
    rameter, or in an application resource file: java.naming.factory.initial
    원인: Need to specify class name in environment or system property, or as an applet parameter, or in an application reso
    urce file: java.naming.factory.initial
    fuego.papi.impl.j2ee.JMSTopicLookUpException: 주제 연결 팩토리 'XATopicConnectionFactory'을(를) 찾는 동안 오류가 발생했
    습니다.
    Detail:
    javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as an applet pa
    rameter, or in an application resource file: java.naming.factory.initial
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:649)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.run(J2EEEngineAccessImpl.java:540)
    Caused by: javax.naming.NoInitialContextException: Need to specify class name in environment or system property, or as a
    n applet parameter, or in an application resource file: java.naming.factory.initial
    at javax.naming.spi.NamingManager.getInitialContext(Unknown Source)
    at javax.naming.InitialContext.getDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.getURLOrDefaultInitCtx(Unknown Source)
    at javax.naming.InitialContext.lookup(Unknown Source)
    at fuego.papi.impl.j2ee.J2EEEngineAccessImpl$TopicSubscriberImpl.lookupTopic(J2EEEngineAccessImpl.java:640)
    ... 1 more

    Hi Ariel,
    You are right. I've got an error in my code using some wrong codes.
    I change my code like this.
    ================================================================
    package com.bpm.ucity;
    import java.util.Properties;
    import fuego.papi.Arguments;
    import fuego.papi.InstanceInfo;
    import fuego.papi.ProcessService;
    import fuego.papi.ProcessServiceSession;
    public class StartProcess {
         public StartProcess() {
              // TODO Auto-generated constructor stub
         * @param args
         public static void main(String[] args) {
              // TODO Auto-generated method stub
              String strProcessID          = "/Process";
              String strUserName          = "mih";
              String strPassword          = "1";
    //changed this part     
         Properties systemProperties = System.getProperties();
         systemProperties.setProperty ("java.naming.factory.initial", "weblogic.jndi.WLInitialContextFactory");
         systemProperties.setProperty("java.naming.provider.url", "t3://localhost:7001");
              ProcessService procServ = null;
              ProcessServiceSession procServSession = null;
              InstanceInfo instInfo = null;
              try {     
                   Properties prop      = new Properties();
                   prop.setProperty(ProcessService.DIRECTORY_PROPERTIES_FILE, "C:/bea/albpm5.7/j2eewl/conf/directory.properties");
                   procServ = ProcessService.create(prop);
                   // create session
                   procServSession = procServ.createSession(strUserName, strPassword, "localhost");
                   System.out.println ("procServSession => [" + procServSession + "]" );
                   // create process instance
                   Arguments arguments = Arguments.create();
                   instInfo = procServSession.createProcessInstance(strProcessID, arguments);
                   System.out.println ("instInfo => [" + instInfo + "]" );
                   String strInstanceID = instInfo.getId();
                   System.out.println ("strInstanceID => [" + strInstanceID + "]" );
              } catch (Exception e) {
                   e.printStackTrace();
              } finally {
                   procServSession.close();
    ================================================================
    and I put weblogic.jar path into the classpath.
    After that, I can get a new process instance, but I've got some errors up to now.
    I think the error is not caused by the code.
    How do you think about it?
    error====================================================
    JMS Topic 엔진에 가입하는 동안 오류가 발생했습니다. reason:'While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved ''
    cause by: While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved ''
    javax.naming.NameNotFoundException: While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved '' [Root exception is javax.naming.NameNotFoundException: While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved '']; remaining name 'java:comp/UserTransaction'
         at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:215)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:338)
         at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:252)
         at weblogic.jndi.internal.ServerNamingNode_923_WLStub.lookup(Unknown Source)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:379)
         at weblogic.jndi.internal.WLContextImpl.lookup(WLContextImpl.java:367)
         at javax.naming.InitialContext.lookup(InitialContext.java:351)
         at fuego.connector.impl.UserTransactionProvider.createForServlets(UserTransactionProvider.java:50)
         at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.createTopicSubcriber(J2EEEngineAccessImpl.java:381)
         at fuego.papi.impl.j2ee.J2EEEngineAccessImpl.<init>(J2EEEngineAccessImpl.java:80)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
         at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:39)
         at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:27)
         at java.lang.reflect.Constructor.newInstance(Constructor.java:494)
         at fuego.prefs.engine.EngineType.createObject(EngineType.java:218)
         at fuego.prefs.engine.EngineType.createEngineAccess(EngineType.java:211)
         at fuego.papi.impl.EngineAccess.getEngineAccess(EngineAccess.java:176)
         at fuego.papi.impl.EngineAccess.getEngineAccess(EngineAccess.java:96)
         at fuego.papi.impl.ProcessServiceImpl.getEngineAccess(ProcessServiceImpl.java:983)
         at fuego.papi.impl.ProcessServiceImpl.createSecureEngine(ProcessServiceImpl.java:1280)
         at fuego.papi.impl.ProcessServiceNESessionImpl$2.run(ProcessServiceNESessionImpl.java:2140)
         at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1578)
         at fuego.papi.impl.ProcessServiceNESessionImpl.getSecureEngine(ProcessServiceNESessionImpl.java:2148)
         at fuego.papi.impl.ProcessServiceImpl.createProcessControl(ProcessServiceImpl.java:1266)
         at fuego.papi.impl.ProcessServiceNESessionImpl$1.run(ProcessServiceNESessionImpl.java:1104)
         at fuego.papi.impl.ProcessServiceImpl.executeEngineOp(ProcessServiceImpl.java:1578)
         at fuego.papi.impl.ProcessServiceNESessionImpl.getProcessControl(ProcessServiceNESessionImpl.java:1109)
         at fuego.papi.impl.InstanceCache.getInstancesByFilter(InstanceCache.java:496)
         at fuego.papi.impl.InstanceCache.getInstancesByFilter(InstanceCache.java:247)
         at fuego.papi.impl.ProcessServiceImpl.getInstancesByFilter(ProcessServiceImpl.java:1087)
         at fuego.papi.impl.ProcessServiceNESessionImpl.getInstancesByFilter(ProcessServiceNESessionImpl.java:755)
         at fuego.papi.impl.ProcessServiceNESessionImpl.getSortedInstancesByFilter(ProcessServiceNESessionImpl.java:2293)
         at fuego.papi.impl.ProcessServiceNESessionImpl.getInstancesByView(ProcessServiceNESessionImpl.java:810)
         at com.bpm.ucity.Inbox.main(Inbox.java:44)
    Caused by: javax.naming.NameNotFoundException: While trying to lookup 'java:comp.UserTransaction' didn't find subcontext 'java:comp'. Resolved ''
         at weblogic.jndi.internal.BasicNamingNode.newNameNotFoundException(BasicNamingNode.java:1139)
         at weblogic.jndi.internal.BasicNamingNode.lookupHere(BasicNamingNode.java:247)
         at weblogic.jndi.internal.ServerNamingNode.lookupHere(ServerNamingNode.java:171)
         at weblogic.jndi.internal.BasicNamingNode.lookup(BasicNamingNode.java:206)
         at weblogic.jndi.internal.RootNamingNode_WLSkel.invoke(Unknown Source)
         at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:553)
         at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
         at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:443)
         at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
         at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
         at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:439)
         at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:61)
         at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:983)
         at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
         at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

  • What is oracle.adf.view.faces.CHECK_FILE_MODIFICATION message ?

    Can anyone say what causes the message? and how can i prevent this message from been generated ?
    2006-08-04 16:13:26.131 NOTIFICATION ADF Faces is running with time-stamp checking enabled. This should not be used in a production environment. See the oracle.adf.view.faces.CHECK_FILE_MODIFICATION property in WEB-INF/web.xml
    Thanks.

    Hi,
    It's message appear because the parameter oracle.adf.view.faces.CHECK_FILE_MODIFICATION is true, so it's only a warning message. To prevent this change this property to false on web.xml
    See the follow link to explain all options on web.xml related to ADF Faces.
    http://www.oracle.com/technology/products/jdev/htdocs/partners/addins/exchange/jsf/doc/devguide/configuration.html
    ------- This is a explanation to its specific point-------
    oracle.adf.view.faces.CHECK_FILE_MODIFICATION
    If this pa rameter is enabled by setting to "true", ADF Faces will automatically check the modification date of your JSPs, and discard saved state when they change; this makes development easier, but adds overhead that should be avoided when your application is deployed.
    Bye

  • XML Publisher "before report trigger"

    I would like to create a new XML Publisher report for Oracle EBS, whereby I can explode a BOM definition before the report fires, but I'm not sure how to go about this in the sql portion of the XML data definition file. Any direction on where to gain this info would be greatly appreciated. Thanks.

    Actually, I just found the following in the 11.5 XDO UG, which I believe answers my own question:
    <dataTrigger name="beforeReport" source="employee.beforeReport()"
    />
    <dataTrigger name="beforeReport" source="employee.beforeReport(:Pa
    rameter)"/>

Maybe you are looking for