Finding/updating users in End User Interface

Hi all,
I have a requirement of searching users, reading their resource accounts and updating some attributes from the end user interface.
But I never really work (customize) the end user interface.
I found information and did:
     - Hide tabs in end user interface
     - Add a link in "Launch" subtab (Request tab)
     - Try to create a process launched by clicking on the link.
But, I don't really know how to display a "find user form" (search by accountId), then display the "result form", then display the "User form" by clicking on a result and finally provision resource accounts if update is necessary.
I really need assistance.
Thank you in advance and best regards,

Anyone?

Similar Messages

User interface elements

in the 'configure virtual form for table' part in the tutorial entitled performing inserts, updates and deletes, it's wriiten 'select the user interface elements in the table component, right click and choose Configure Virtual Forms'. but i can't find any 'user interface elements'. can anyone tell me how to get this out so that i can configure the virtual forms. thanx.

Hi,
The "user interface elements" refer to the components namely textField1, dropDown1, textField2 and textField3. Select all of these components either in the designer view or in the Outline window. Once selected right click on one of the components and you will get the option Configure Virtual Forms.
Hope this helps
Cheers
Girish

Find Task usage for end user

I want to use find task functionality on enduser interface. I configured a link for findtask.jsp on end user page. But on selecting the link; it redirect to admin user interface and prompts for login. Any idea why it's redirecting there and what can be done so that it works on the end user inteface only. The idea is to give this functionality to end user so that he is able to search any workflow task in IDM.
Let me know if anybody has provided similar solution or used this feature on end user interface.

Thank you for your posting. These forums are specific to the
Acrobat.com website and it's set of hosted services, and do not
cover the Acrobat family of desktop products. Please visit the
following forums for any questions related to the Acrobat family of
desktop products:
http://www.adobeforums.com/cgi-bin/webx/.3bbeda8b/
Note: Once Reader enabled certain functions like editing a
PDF,inserting or deleting the pages will be restricted at end user
part.Apart from this "Calculate" function will support both Acrobat
as well as Reader application.

Using SPML to create a custom end user interface?

We are trying to create a custom end user interface which uses SPML to communicate with our IDM server. The issue we have is whether there is a way to login to IDM from this end user interface as the end user, or at least run the end user functionality such as password changes and authentication question setup as the end user without giving all end users SPML capabilities. Right now we have created a special SPML user account and we have given that user broad capabilities. We are able to change passwords and set questions but the auditing just shows the SPML user as the subject for all these actions.
Thanks,

It looks like you are absolutely right.
I also cannot find that zlman option.
So it looks like you are the first that needs it.
We use zlman to create bundles and add packages when we build them in our rpm build environment, but at that time that are always new packages that need top be uploaded. So the bundle-add-package is what we use, but that doesn't help with packages in the repository.
So I would write a enhancement request for it ...
http://www.novell.com/rms
As a workaround, not a nice one of course, you can search for the package in the repository and upload it once again. It should recognize that and create just the package links to the bundle. Not nice, but it seems to be the only option for now.
Rainer

How to display the updated data from db to user interface in sruts framewor

A beginner in this area, I have been able to read a record from a
MySQL database and populate in jsp form . Now, my goal is to
allow the user to edit the contents of the form and then update the
record in MySQL and then display the same in jsp. page
The scenario in detail
1)the data is fetched from db and displayed in non-editable format
2)Next button is clicked
3)Now in the same jsp page I view the same data from db in editable format
4)The user is allowed to change the information
5)Now update button is clicked
6)the records are updated in the db -Finished doing till this step
7)But the updated info in non - editable format to be displayed in jsp page is left pending.
Here is my code for jsp,i want know how to write an action for this,tried doing the same in java and I'm successful.but what I need is how to fetch the updated information in the user interface.
I've made both editable as well as non editable info in the same page with different actions.
pl help me,I'm a newbie
<%@ taglib uri="/WEB-INF/struts-bean" prefix="bean" %>
<%@ taglib uri="/WEB-INF/struts-html" prefix="html" %>
<%@ taglib uri="/WEB-INF/struts-logic" prefix="logic" %>
<%@ page language="java" %>
<%@ page import="java.util.ArrayList,java.util.Iterator" %>
<%@ page import="com.finocus.common.container.CustomerDetailsTest;" %>
<html:html>
<head>
 <title>CUSTOMER DISPLAY</title>
</head>
<body>
 <table width="100%" bgcolor="darkkhaki">
 <tr>
 <td><table width="100%" bgcolor="indigo">
 <tr>
 <td>Display</td>
 <td>Update</td>
 <td>Verify</td>
 <td>Confirm</td>
 </tr>
 </table>
 </td>
 </tr>
<%
 //Container for holding data
 ArrayList list = (ArrayList)session.getAttribute("CUSTOMERDETAILS");
 Iterator itr=list.iterator();
 while(itr.hasNext())
 CustomerDetailsTest cust = (CustomerDetailsTest) itr.next();
 System.out.println("testGetCustomerDetails()-successed. retrieved CustomerDetailsTest="+cust.toString());
%>
<%
 //Session for checking whether edit or non-edit mode
 String pageMode = (String)session.getAttribute("CUSTOMER_PAGE_MODE");
 session.removeAttribute("CUSTOMER_PAGE_MODE");
 if(null==pageMode)
 pageMode = "EDIT";
 if(pageMode.equals("EDIT"))
 //display data in the form
 System.out.println("Editable mode");
%>
 <html:form action="/nonedit">
 <tr>
 <td><table width="100%" bgcolor="darkkhaki">
 <tr>
 <td><bean:message key="label.id"/></td>
 <td><%=cust.getCusId()%></td>
 </tr> 
 <td>
 
 <bean:message key="label.Company"/>
 </td> 
 <tr>
 <td><bean:message key="label.cname"/></td>
 <td><html:text property="name" value="<%=cust.getCname()%>"/></td>
 <td><bean:message key="label.cphone"/></td>
 <td><html:text property="phone" value="<%=cust.getCphone()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.caddr1"/></td>
 <td><html:text property="address1" value="<%=cust.getCaddress1()%>"/></td>
 <td><bean:message key="label.cemail"/></td>
 <td><html:text property="email" value="<%=cust.getCemail()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.caddr2"/></td>
 <td><html:text property="address2" value="<%=cust.getCaddress2()%>"/></td>
 <td><bean:message key="label.cfax"/></td>
 <td><html:text property="fax" value="<%=cust.getCfax()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.ccity"/></td>
 <td><html:text property="city" value="<%=cust.getCcity()%>"/></td>
 <td><bean:message key="label.czip"/></td>
 <td><html:text property="zip" value="<%=cust.getZip()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.cstate"/></td>
 <td><html:text property="state" value="<%=cust.getCstate()%>"/></td>
 </tr> 
 <td>
 
 <bean:message key="label.Admin"/>
 </td> 
 <tr>
 <td><bean:message key="label.AAname"/></td>
 <td><html:text property="adminname" value="<%=cust.getAname()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.AAemail"/></td>
 <td><html:text property="adminemail" value="<%=cust.getAemail()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.AAphone"/></td>
 <td><html:text property="adminphone" value="<%=cust.getAphone()%>"/></td>
 </tr> 
 <td>
 
 <bean:message key="label.User"/>
 </td> 
 <tr>
 <td><bean:message key="label.AUname"/></td>
 <td><html:text property="adminusername" value="<%=cust.getUname()%>"/></td>
 </tr> 
 <tr>
 <td><bean:message key="label.AUemail"/></td>
 <td><html:text property="adminuseremail" value="<%=cust.getUemail()%>"/></td>
 </tr> 
 <tr align="center">
 <td><html:cancel value="Cancel"/>
 <html:submit value="Next"/></td>
 </tr>
 </html:form>
<%
 }else
 //display data in the text
 System.out.println("Non-Editable mode");
%>
 <html:form action="/edit">
 <tr>
 <td><table width="100%" bgcolor="darkkhaki">
 <tr>
 <td><bean:message key="label.id"/></td>
 <td><%=cust.getCusId()%></td>
 <td><bean:message key="label.status"/></td>
 <td><%=cust.getStatus() %></td>
 </tr> 
 <td>
 
 <bean:message key="label.Company"/>
 </td> 
 <tr>
 <td><bean:message key="label.cname"/></td>
 <td><%=cust.getCname()%></td>
 <td><bean:message key="label.cphone"/></td>
 <td><%=cust.getCphone()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.caddr1"/></td>
 <td><%=cust.getCaddress1()%></td>
 <td><bean:message key="label.cemail"/></td>
 <td><%=cust.getCemail()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.caddr2"/></td>
 <td><%=cust.getCaddress2()%></td>
 <td><bean:message key="label.cfax"/></td>
 <td><%=cust.getCfax()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.ccity"/></td>
 <td><%=cust.getCcity()%></td>
 <td><bean:message key="label.czip"/></td>
 <td><%=cust.getZip()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.cstate"/></td>
 <td><%=cust.getCstate()%></td>
 </tr> 
 <td>
 
 <bean:message key="label.Admin"/>
 </td> 
 <tr>
 <td><bean:message key="label.AAname"/></td>
 <td><%=cust.getAname()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.AAemail"/></td>
 <td><%=cust.getAemail()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.AAphone"/></td>
 <td><%=cust.getAphone()%></td>
 </tr> 
 <td>
 
 <bean:message key="label.User"/>
 </td> 
 <tr>
 <td><bean:message key="label.AUname"/></td>
 <td><%=cust.getUname()%></td>
 </tr> 
 <tr>
 <td><bean:message key="label.AUemail"/></td>
 <td><%=cust.getUemail()%></td>
 </tr> 
 <tr align="center">
 <td><html:submit value="Update"/></td>
 </tr>
 </html:form>
<%
%>
<%
%>
 </table>
 </td>
 </tr>
 </table>
</body>
</html:html>

u r using action classes. so after calling the insert method in Action Class to a dao... the next statement should be retrieve statement. so at the time of updating first it will get updated.. the next statement it will execute is retrieve and then set these details in VO or FORM and show it on JSP
Message was edited by:
leo_michael

Freeze problem in user interface initiatilisation after all NVDIA update and 8.0.1

I just received Pre 8 and installed it
When starting the various modules
- Organiser works more or less fine (it crash when it looks at my folders with 28000 pictures), but it works when doing import folder by folder
- but when I am starting a new project
I never get to the user interface of the software
I get a small red dot and when clicking problem with your driver
I have already looked at the forum
updated at NVidia site
I am running a
Dell Inspiron 1720
Windows 7 , 64 bits, French
4 GB RAM
NVIDIA 8600 M GT
latest NVIDIA driver from July 2010 (version 258.96)
Installed PrE 8 French from the DVD
upgraded to 8.0.1 from the Adobe website
I can not use any of the software function as the screen is fully black and I only see the top level menus
theoptions are availalbe but non of them is working
and the message atbottowlefttays at user interface initialisation
Thanks

I've never set Portuguese, so I really don't know what to tell you. It would be my presumption, though, that this sort of feature would be handled in the World-Ready Composers, but clearly there is either a bug or I'm mistaken, or both.
I would suggest you file a bug report at Adobe - Feature Request/Bug Report Form, though I doubt there will be a fix.

User interface for updating/adding attributes in OID

Hello,
I have not done the develop work in OAS10g (web, oid, +) though I have years experiences as DBA in OAS and Oracle database servers.
I need to develop a user interface for users to add or update the user's attributes such as sn, manager etc.
The IDM system is working in prod: OAS 10g r2, installed (upgraded to) with infrastructure and oid 10.1.4.3.
OID: user attributes have been loaded with: CN, UID, mail and etc.
The requirement
User interface: an app based Ohttp web 10g
I'd like the interface works like:
The user accessing the web interface, is prompted with UID and mail. if the user correctly fills the fields, then will be prompted with the attributes which user can add or update.
Because I have Not done any development in OAS (web, oid), I need know what skills I need to aquire. ANd how should I proceed?
I may know the skills would be Ohttp development and OID API (LDAP), but I need these be specific as much as possible.
Can any point the direction with examples and docs?
TIA
GA

ajaybabu007 wrote:
For managing the user related activities (create,update,lock,unlock,delete and so on) through an Web UI interface can be administrated with the Oracle Identity Management Self Service Console (http://infra_host_name:7777/oiddas) which is an inbuild component of OID/OSSO. Please provide orcladmin/<password> credentials for accessing this Web UI.
---ABP thanks.
1) the app for user to add/update the attributes. we cannot give orcladmin to them
2) though the users as their own can access the oiddas, there are only limit of user info could be updated, which cannot serve the attributes we customized and loaded in OID.

Weather not displaying in notification center after iOS 5 update not to mention the entire user interface is much more sluggish.

Weather not displaying in notification center after iOS 5 update not to mention the entire user interface is much more sluggish.

Okay, mine now works here is what I did.
plug in the iPhone, iPad etc
in iTunes select the phone or iPad
Under Summary uncheck "Sync with this....."
Under "Music" uncheck the "Sync Music"
Let it remove all the songs, dont worry it will come back no problems.
Once that is all done all the music on the phone or ipad should be gone.
Now check them both back on and everything should copy back onto it.
Working now !!!!!

Update Station Globals from LAbWindows/CVI user interface

Hi,
I am having a requirement such that i need to update a station global variable to true or false based on the click on a button present in User Interface.
My Setup:
Labwindows/CVI 8.5
TestStand 4.2.1
Please advice me.
Solved!
Go to Solution.

Hi,
first thing, why have you posted this query twice, http://forums.ni.com/t5/NI-TestStand/Update-Station-Globals-from-CVI-UI/m-p/1317023
to be able to update a StationGlobal, you first need to get a reference to the Engine, this can be done using ApplicationMgr.GetEngine()
Once you have that reference you can then get a reference to the StationGlobals by the use of Engine.Globals(). this returns a PropertyObject.
So now you can use the SetVal methods to set your boolean, eg PropertyObject.SetValBoolean("MyBoolean", 0, True)
hope this helps
Regards
Ray Farmer

Muse 2014.3 update has an over-sized user interface.

The Adobe UI Scaling bug has reared its head again, this time with Muse (like with previous versions of PS, AI and ID before it). See screen grab that makes my 22" HD look like an old 12" monitor (see pasted at half resolution below).
I don't see anyone else with this issue posting, but I'm sure it's just a matter of time. Any suggestions? Do I have to go back to the Windows Environment settings again? I set it to =1 to fix one of the other applications a while back.

Sounds like your Win machine is set to run at 125% scaling (or thereabouts), is that right? Or do you have multiple monitors with different native resolutions, and the "one resolution to rule them all" setting engaged?
Previous versions of Muse would ignore the 125% scale factor and run at 100%.
The new release of Muse (2014.3) also does not support running at 125%, but can run at 150% and 200% scale factors. Muse 2014.3 chooses to run at 150% in this case. For many people with vision impairment or eye strain issues 150% is a better choice than staying at 100%, but we understand it may not be best for everyone. At 150% the cursors will be oversized as you describe (using 2x cursor artwork), but everything else will be drawn crisply at 150% scale.
In the short term, we can add support for an environment variable override similar to what InDesign and Illustrator used (see Application user interface too large | Windows). Would that address the problem for you?
One question, would it be better for you if Muse, InDesign and Illustrator all obeyed the same environment variable override, or would it be better if Muse used a different one? Now that ID and AI have exposed a user preference setting for UI Scaling (see InDesign's below), it might be better if Muse used a different environment variable so as not to override the user preference in AI and ID.
We will aim to add a similar Win-only user preference for the next release of Muse.
DaveB

Mavericks user interface hangs - any known solutions?

I have a 27" late 2012 iMac with an up-to-date copy of Mavericks (10.9.4.)
Occasionally (as in every couple of weeks) the user interface hangs completely.
The mouse cursor moves, but clicks do not have an effect, and the keyboard is ignored.
Applications continue to update the screen. Today, for example, I was running Windows RDC 8 through a VPN to a customer server. After the hang started, I could see the progress updates on an SQL server restore as it continued to run. Activity Monitor was updating in the background too.
Connecting from my (17" MacBook Pro) laptop (: I love that machine!) using Screen Sharing worked but I could not update.
I took the dog for a walk for an hour or so, and when I returned there was a login screen on the iMac. To my great delight, I typed in my password and logged back in. To my greater disappointment, the UI was still hung and my only recourse was to crash it by holding in the power button until it stopped, then reboot.
The machine has 24GB of RAM and 1.92TB of free disk space. I doubt it is running out of resources. It has no additional displays connected.
The only weirdness is Teleport - which allows me to share the iMac keyboard with the laptop. It is entirely possible Teleport is the culprit, but I am hoping it is not.

These instructions must be carried out as an administrator. If you have only one user account, you are the administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
For this step, the title of the Console window should be All Messages. If it isn't, select
          SYSTEM LOG QUERIES ▹ All Messages
from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar at the top of the screen.
In the top right corner of the Console window, there's a search box labeled Filter. Initially the words "String Matching" are shown in that box. Enter "BOOT_TIME" (without the quotes.)
Each message in the log begins with the date and time when it was entered. Note the timestamps of the BOOT_TIME log messages, which refer to the times when the system was started. Now clear the search box and scroll back in the log to the last boot time when you had the problem. Select the messages logged before the boot, during the time something abnormal was happening. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message by pressing command-V.
For example, if the system was unresponsive or was failing to shut down for three minutes before you forced a restart, post the messages timestamped within three minutes before the boot time, not after. Please include the BOOT_TIME message at the end of the log extract—not at the beginning.
If there are long runs of repeated messages, please post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. A few dozen lines are almost always more than enough.
Some private information, such as your name, may appear in the log. Anonymize before posting.
Please don't indiscriminately dump thousands of lines from the log into this discussion.
Please don't post screenshots of log messages—post the text.
Step 2
In the Console window, select
          DIAGNOSTIC AND USAGE INFORMATION ▹ System Diagnostic Reports
(not Diagnostic and Usage Messages) from the log list on the left. If you don't see that list, select
          View ▹ Show Log List
from the menu bar.
There is a disclosure triangle to the left of the list item. If the triangle is pointing to the right, click it so that it points down. You'll see a list of reports. A crash report has a name that begins with the name of the crashed process and ends in ".crash". A panic report has a name that begins with "Kernel" and ends in ".panic". A shutdown stall report has a name that ends in ".shutdownstall". Select the most recent of each, if any. The contents of the report will appear on the right. Use copy and paste to post the entire contents—the text, not a screenshot. It's possible that none of these reports exists.
I know the report is long, maybe several hundred lines. Please post all of it anyway.
If you don't see any reports listed, but you know there was a crash or panic, you may have chosen Diagnostic and Usage Messages from the log list. Choose DIAGNOSTIC AND USAGE INFORMATION instead.
In the interest of privacy, I suggest that, before posting, you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if it’s present (it may not be.)
Please don’t post other kinds of diagnostic report—they're very long and rarely helpful.

Error in report builder wizard user interface

I am getting error 'REP-31954: Error in the Report Builder Chart Wizard user interface'.
The help subsystem states that I should make sure that the Chart Builder Wizard libraries are properly installed.
I am sure they are because all other wizards work fine, along with the Forms, Reports, etc.
I searched using Google and found two messages that indicate this is a bug in the program and not library installation related.
Does anyone know if this is indeed a bug that has not been resolved, or do I need to troubleshoot more on my end.
I re-linked Oracle graphics and checked the env variables, but nothing gets the Chart Wizard to work within Reports or Forms.
Any help/advice would be greatly appreciated.
Thank you.

Hi.
I am running developer 6i on my home machine (with Oracle 8i, v 8.1.7). I am at work at the moment, and I can't recall what the Reports version is. The same error occurs with Forms.
The filename that I downloaded is called 'd2k6irelease2.tar'.
I downloaded the version that is currently on Oracle OTN's download site, so I presume that is the latest version that should contain all patches, updates, etc.
Thank you for responding!

Why do I get -18001 Errors using Customised TestStand User Interface

Hi all
I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
If anyone
has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
Thanks
Dave

David,
I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
LabVIEW : VI is not executable.
An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
2) The same error will occur when
a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
Building The Operator Interface
The following are steps if you are using a LabVIEW operator interface.
1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
Creating a LabVIEW Run-time Server
If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
3) In LabVIEW Select Tools>>Build Application or Shared Library
4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
5) In the builder click Build.
6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
Assembling the Test VIs for Run-Time Distribution
This distribution process uses one of the shipping TS examples that calls LV VIs.
1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
3) Confirm that the sequence runs without problem.
4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
6) Set the target directory to be something distinct like C:\temp\AssblVIs.
7) If you are using TestStand 2.0 skip adding Dynamic VIs
8) Save with or without diagrams. Its your choice.
Change Search Directories
Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
1) In the sequence editor select Configure>>Search Directories.
2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
3) Close the Edit Search Directories dialog box.
4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
1) In the sequence editor select Configure>>Adpaters.
2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
Distributing Components
-To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
-To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
-You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
Hope this helps.
Regards,
Kitt
=========================================
Title:
Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
Components that need to be distributed:
TS engine
Operator interface
LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
LabVIEW run-time engine
LabVIEW test VIs
Test sequence files
Actions before distributing:
It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
Assemble the test VIs for distribution.
Update the TestStand search directories so that the sequences reference the assembled VIs.
Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
Test the distribution components on the development machine.
Enter section headings, separating each section with a line break:
TS Engine Component
Operator Interface Component
LabVIEW ActiveX Server
Configuring the LabVIEW Standard Prototype Adapter
LabVIEW Run-time Engine Component
Assembling your Test VIs for Distribution
Note
TS Engine Component
With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
Operator Interface Component
You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
LabVIEW ActiveX Server
You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
Configuring the LabVIEW Standard Prototype Adapter
When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
LabVIEW Run-time Engine Component
If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
Assembling your Test VIs for Distribution
After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
Links: See Distributing LabVIEW Test VIs below
Note
Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
==============================================

What is the best way to get data to a user interface?

Hi,
I'm using labview 6i. I have an application with a handful of "core" vi's that actually run my application, doing the data acquisition, analysis, and control. I am currently using these same vi's for my user interface. I also have a number of vi's that contain menu's for configuring the "core" vi's. My questions is, what is the best way to seperate the "core" vi's from the user interface vi's. Global's, data socket, control references, others?
Thanks for the help.

Hi Sal,
I have been a strong advocate of control refnums ever since LV 6i hit the streets. I recomend you look into using them to provide this conectivity.
You could accomplish this by using a variation on the following.
In your UI, create refnums for each of the controls or indicators that must be monitored or updated. Pass the appropriate refnums to each of the "core.i's" at program init time. Inside each of the core.vi's, use property nodes to read the control's values when appropriate and similarly for display purposes. (Note: Not all boolean mechanical actions are compatible with this technique. In those case you will have to explicitly write false values after find the control to be true or vise versa).
By using this technique, you can keep the UI diagrams clea
n. Depending on your app. the UI diagram could consist of the init's I mentioned above, and a while loop that watches if it's time to exit.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

No Plug-In specified and not allowed to bring up user interface

Hello,
We have several users here getting an error when trying to sign a pdf with Adobe's digital signature. When they click in the field box to sign the document they are getting the following error,"No plug-in specified and not allowed to bring up user interface for selection." We are using Adobe acrobat 9 standard with the latest updates. I have done a total uninstall and reinstall and recreated the digital signature and still the error persists. I have gone as far as renaming the windows profile and nothing seems to work. Any thoughts?
Aaron

A signature field may have associated so-called "seed values" that specify certain signature properties and restrictions. The document's author can associate "seed values" with an unsigned signature field. One of the "seed values" specifies which external signature plug-in must be used to sign this signature field. If you do not have the required plug-in in the Acrobat installation then you cannot sign this signature field. This is the most likely reason that you get this error message. In some environments this is done to restrict the signing to only signing credentials that reside on hardware modules or signing pads. There might be other reason why the document's author chose to put in this restriction.
Contact the author of the document you are trying to sign and find out whether this is the case and if it is then which plug-in you need and where you get it from.

Finding/updating users in End User Interface

Similar Messages

Maybe you are looking for