Intigration with Vignette Application Builder

Does anyone have any experience with creating war files with
MX7 and then deploying them on Vignette Application portal
solution? Any information will be greatly appreciated.

Hello Stevi,
You should probably check your VI Properties for window size. First, make sure your front panel is sized exactly how you want it to appear. Then go to File >> VI Properties, and select Window Size from the drop-down box. Click on the "Set to Current Window Size" button. Also select "Maintain Proportions of Window for different monitor resolutions". These two selections should ensure that the VI and/or EXE will run with the desired window settings.
Hope this helps!
Liz Fausak
National Instruments

Similar Messages

Full windowsize with the application builder

Hi,
I creat an executable file with the application builder. The problem is, the window is not as large as when I starte the program in Labview. Now the Frontpanel is cut on the bottom. What is the problem ?
thanks for help
stevi

Hello Stevi,
You should probably check your VI Properties for window size. First, make sure your front panel is sized exactly how you want it to appear. Then go to File >> VI Properties, and select Window Size from the drop-down box. Click on the "Set to Current Window Size" button. Also select "Maintain Proportions of Window for different monitor resolutions". These two selections should ensure that the VI and/or EXE will run with the desired window settings.
Hope this helps!
Liz Fausak
National Instruments

Building a standalone Mac application with an application builder running on Windows?

I created a user interface which communicates with a cRIO System via TCP/IP. The user interface should run on multiple hosts consisting of windows PC's and Mac's. My LabView development system is running on Windows. So my question: is it possible to build a Mac application with an application builder running on Windows?
Thanks for your help!

Only if the Mac is running windows. Otherwise, you need a Mac version of LabVIEW and the app builder for that.
p.s. You spelled LabVIEW incorrectly.

The executible I build with the application builder does not function the same as my VI file.

I am using a USB 6008 device with the newest DAQmx drivers and Labview
8.2 to make analog voltage readings. Within my main VI I first
create a data folder in the same location as the VI using a property
node and then use case statements to call two sub VIs that create a
data file within the data folder and then collects data. When I use the
application builder to create an executible the resulting file does not
operate the same as the origional VI. The program appears to be
reacting to button presses on the GUI, but there is no indication that
the data folder is being created or that any measurements are buing
made. Are there any known issues that may account for this
anomily?
-Mike
Message Edited by TMBurleson on 10-16-2006 03:09 PM

Are you using the VI Path property, using a reference to the current VI?
I could be wrong, but if you're attempting to use a path relative to the current VI, I think that does indeed change in a built application. If your VI used to be C:\somewhere\foo.VI, then after building its path would actually be C:\somewhere\foo.EXE\foo.vi . Thus, if foo.VI used to try to make a folder like C:\somewhere\datafolder, the built application would be trying to make C:\somewhere\foo.EXE\datafolder , which wouldn't work.
This is sort of a shot in the dark, but does this sound like it might be the case?
EDIT: Dennis beat me to it.Message Edited by kehander on 10-16-2006 03:26 PM

How can I use a shared library made with the application builder?

Hi,
I am using LabVIEW 7.1 running on Slackware 10.1 (kernel 2.4.29) and I am trying to call a graph display from a C program that I use for debugging VME access from a VMIVME controler. So using the application builder I built the VI as a shared library (graph.vi -> graph.so) containing a function called "graph". In my main program the call to the dlopen fails with the error: "graph.so: undefined symbol: UninitLVClient". When I examin graph.so with nm I see that UninitLVClient and other LabVIEW functions are indeed undefined and using ldd shows that graph.so has dependencies only on libc.so.* and *linux*.so.* but not on LabVIEW related stuff. Those functions are defined in the liblv.so that's in the cintools directory but I have no idea if the user is supposed to use that.
So I think I am missing an important concept here. Can somebody help or direct me to some documentation (I found lots of information about how to link external code to LabVIEW but nothing about how to link LabVIEW code to an external program)?

Thanks Watermann,
your message has been very useful so now I am linking to the proper library but I still have problems when trying to load dynamically the shared library produced with LabVIEW. It is strange that I could successfully load the lvrt library at loading time but it does not work when I am loading the library at execution time.
I made a small LabVIEW program that prints a hello window and I am calling it from a C program. In the first program main.c I am linking to the lvrt library at loading time and it works but in the second one I am linking dynamically at execution time and it does not work. For my work I need to be able to load code done in LabVIEW at execution time. Any help is appreciated!
Program main.c:
// small program to call a LabVIEW shared library
#include
#include
#include "hello.h" // got this from the LabVIEW builder, i.e. when I made the hello.so
int main(void)
printf("Hello from C!\nLets call LabVIEW now\n");
hello();
printf("Bye ... \n");
return 0;
The command to compile main.c, i.e. linking shared library lvrt when loading main program:
gcc -Wall -I /usr/local/lv71/cintools/ -o main main.c hello.so -l lvrt
The LD_LIBRARY_PATH has been defined and exported:
$ LD_LIBRARY_PATH=$PWD
$ export LD_LIBRARY_PATH
IT WORKS!
Program main2.c:
// small program to call a LabVIEW shared library
#include
#include
#include
int main(void)
void * h_lvrt;
void * h_hello;
void (* hello)(void);
char * error;
printf("Hello from C!\nLets call LabVIEW now\n");
// open LabVIEW RunTime shared library
// in my computer located at /usr/local/lib/liblvrt.so
h_lvrt = dlopen("/usr/local/lib/liblvrt.so", RTLD_NOW);
// check for error
error = dlerror();
if (error) {
printf("error : could not open LabVIEW RunTime library\n");
printf("%s\n", error);
return 1;
// open hello shared library
// in my computer located at /home/darss/lv_call/hello.so
h_hello = dlopen("hello.so", RTLD_NOW);
// check for error
error = dlerror();
if (error) {
// close LabVIEW RunTime shared library
dlclose(h_lvrt);
printf("error : could not open hello library\n");
printf("%s\n", error);
return 1;
// get function hello from library hello.so
hello = dlsym(h_hello, "hello");
// check for error
error = dlerror();
if (error) {
// close hello shared library
dlclose(h_hello);
// close LabVIEW RunTime shared library
dlclose(h_lvrt);
printf("error : could not get the hello function\n");
printf("%s\n", error);
return 1;
// call hello function
hello();
// close hello shared library
dlclose(h_hello);
// close LabVIEW RunTime shared library
dlclose(h_lvrt);
printf("Bye ... \n");
return 0;
The command to compile main2.c, i.e. dynamically linking library lvrt at execution of main2 program:
gcc -Wall -o main2 main2.c -l dl
The LD_LIBRARY_PATH still defined and exported.
IT DOES NOT WORK!
Program output:
Hello from C!
Lets call LabVIEW now
error : could not open hello library
/home/darss/lv_call/hello.so: undefined symbol: WaitLVDLLReady

Can I include raw files into the installer folder with LV application builder?

Hello,
I have created a batch file that will run at the end of the installer, which will copy over some raw configuration files into the source destination so that the configuration files can be customized for each end user without rebuilding the installer with application builder. I also have an autorun.inf so the installer will automatically run when the user installs the CD.
However I would like to have some default configuration files and an autorun.inf file that will be automatically added to the installer "volume" folder using the application builder.
However I don't see a way to include raw files in the "volume" folder. It appears all source files in the application builder are embedded into the binary files.
Please let me know if this is possible with the current application builder.
Regards,
Russell
Engineering Team Leader
G Systems, www.gsystems.com
Certified LabVIEW Architect
Certified Professional Instructor

Russel,
i think this link might give you some good hints....
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

How to include another msi with LV application builder?

I can use LV application builder to create an installer for my application. But my application relies on a 3rd part msi, which should be run after my application is installed. So how to include this msi with LV app builder? Thanks in advance.

I would recommend executing a batch file that launches your other installers after your LabVIEW executable finishes installing. The process of doing this (in addition to other suggestions about including 3rd party installers) can be found in the Knowledgebase linked here.
Kind Regards,
E. Sulzer
Applications Engineer
National Instruments

Problem with iPhone application Build in xcode 4

Hey Developers,
I have an application that has been on the appstore for sometime. I have recently updated it and want to distribute.
I have followed my usual approach by selecting 'release' in the edit scheme options and run a Build.
After the sucessful build, i usually now select the .app file --> show in finder --> compress --> upload the file. But i have a problem. The .app file text is red in colour and when selected, it will not give me the option to show in finder.
I located the .app file builds in the debug and release folders of my project - but these are not showing the updates I have made.
What can i do to solve this problem?
james

Thanks KT,
I hadn't read this - it was really useful.
problem solved.
james

Working with Blueprint Application Builder

Dear BSP Guru's
I want to play with BAB and create my own queries which can be used by all the Portal Users. I want to add A field Status in Advanced search where it would be able to select 2 statuses instead of just 1. How would I go abt?
Any help or document on this would be highly appreciated and appropriately rewarded
Thanks
Prasad

Vivek, get me your email address and will forward you the CRM PC-UI 4.0 Cookbook and I would recommend you to go through the examples and the end of the documentation to get a feel of the concept and how to tackle your questions. Also read the conceptual piece of the blueprint tables and their possibilities. If you have any questions just let us here now and help you gladly. Tiest.
By the way also have a look at my weblog: <a href="/people/tiest.vangool/blog/2005/07/24/pc-ui-and-easy-enhancement-workbench-eew-integration and Easy Enhancement Workbench (EEW) Integration</a> which describes the generic process on how to extend transactions and make them available in PC-UI.
Message was edited by: Tiest van Gool

Problem with Application build in JDeveloper 11.1.5 to WLS 10.3.5

Hi to everyone, I have a problem with a application build in JDeveloper 11.1.5 and deployed to a standalone WLS 10.3.5 ( with the JRF template appliied , to run adf applications )
When I try access to the page : localhost:7001/myApp , it show me :
"Error 403 Fordbbiben ".
but when I put :
localhost:7001/myApp/index.jspx, it show me :
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
and the log is :
<May 8, 2012 9:06:22 PM BOT> <Warning> <oracle.adf.view.rich.component.fragment.UIXRegion> <BEA-000000> <
java.lang.IllegalStateException: The expression "#{bindings.genRegion.regionModel}" (that was specified for the RegionModel "value" attribute of the region component with id "genRegion_dlg") evaluated to null.
This is typically due to an error in the configuration of the objects referenced by this expression.
If it helps, the expression "#{bindings.genRegion}" evaluates to "null".
If it helps, the expression "#{bindings}" evaluates to "null". Now using an empty RegionModel instead.
at oracle.adf.view.rich.component.fragment.UIXRegion.getRegionModel(UIXRegion.java:450)
at oracle.adf.view.rich.component.fragment.UIXRegion._beginInterruptibleRegion(UIXRegion.java:682)
at oracle.adf.view.rich.component.fragment.UIXRegion.processRegion(UIXRegion.java:498)
at oracle.adfinternal.view.faces.taglib.region.RegionTag.doStartTag(RegionTag.java:127)
What can I do to fix the problem ??
Thanks

Analyzing the problem, I created a new ADF application with only a web page (index.jspx) , and deploy it to the WLS, and I access to URL of page and it runs !! ( http:localhost:7001/myApp/faces/index.jspx ).
But, when I ADD A TASK FLOW to the application and deploy to the WLS newly , and try to access to the URL application's ( http:localhost:7001/myApp/faces/index.jspx ) . It show me again :
Error 500--Internal Server Error
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:
10.5.1 500 Internal Server Error
The server encountered an unexpected condition which prevented it from fulfilling the request.
and the log is :
<May 10, 2012 19:02:57 PM BOT> <Warning> <oracle.adf.view.rich.component.fragment.UIXRegion> <BEA-000000> <
java.lang.IllegalStateException: The expression "#{bindings.genRegion.regionModel}" (that was specified for the RegionModel "value" attribute of the region component with id "genRegion_dlg") evaluated to null.
This is typically due to an error in the configuration of the objects referenced by this expression.
If it helps, the expression "#{bindings.genRegion}" evaluates to "null".
If it helps, the expression "#{bindings}" evaluates to "null". Now using an empty RegionModel instead.
at oracle.adf.view.rich.component.fragment.UIXRegion.getRegionModel(UIXRegion.java:450)
at oracle.adf.view.rich.component.fragment.UIXRegion._beginInterruptibleRegion(UIXRegion.java:682)
at oracle.adf.view.rich.component.fragment.UIXRegion.processRegion(UIXRegion.java:498)
at oracle.adfinternal.view.faces.taglib.region.RegionTag.doStartTag(RegionTag.java:127)
Why it show me that error when I ADD a Task Flow to the Application ???
Can Anyone help me please ?? I m varios days with this problem. Thanks

Error message "VI is not executable"! Need help with Application Builder

Hello,
I have a problem with an application, built with the Application Builder. I have read some threads about the problem I have, but I still don't know a solution.
When I run my front panel from LabVIEW, everything is good. So, now I created an application (and an installer) to be able to run it on other PCs as well. This application does not work. Everytime I start it on my PC, I get the error "VI is not executable. ...". I read in several forums solutions for this error, but I cannot fix it! I've changed my properties for the builder, but with no success. Perhaps, anybody has more ideas, what's the problem.
To get a better idea from my project, here a little description of it:
In the block diagram there is a while loop which is continuously runned. In this loop I only set some properties for the layout of the front panel, such as decorations which will be hidden/shown and changes of colours of indicators... For the rest, it waits for a click on the button "Start" in the front panel. After that, a DLL is called to communicate with a USB device. Some measurements are carried out and the DLL is closed. I hope, you can get a global idea from my block diagram...
I use LabVIEW 8.5, the DLL is a third-party DLL, which we wrote on our own. But I think the DLL works properly, if it is called from a C# application it works and it works, too, by calling it from LabVIEW when I am in development mode.
It's a project for university and I'm just a beginner in LabVIEW, so I don't have so much experiences in it, but I think i improved my knowlegde about LabVIEW very well in the last weeks!
So, i hope to get an answer soon (the deadline for the project is not soooo far away )
If you need more information, please let it know...
I would be very grateful if there is someone with a working solution...
Kind regards from the Netherlands,
Sebastian

Sebastian,
Your architecture makes it very difficult to debug this and other problems. Does the error message mention which VI is causing the problem? It is very important to wire your error clusters everywhere. In LabVIEW, when a node throws an error (Error.Status = T), future nodes do not execute. At the end, place an error cluster indicator that you can see on your front panel. When an error posts, you can right click the indicator (even in a compiled application) and select "Explain Error".
This is a start, but you really need to push this into a queued-state machine before this gets any more complicated. As it were, if anything in your loop hangs, your whole application hangs. See attached for a queued-message handler (not advisable for actual applications, but you get the point. You would want to have a type defined enum in lieu of strings, and shared data between states differently, etc.)
-Jason
Message Edited by LabBEAN on 01-20-2009 08:36 AM
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs
Attachments:
State Machine.vi ‏18 KB

Using dynamic VI referencing in combination with Application Builder

Hi.
In this thread (http://forums.ni.com/t5/LabVIEW/How-to-access-a-known-control-in-a-VI-reference/td-p/1255244) I attempted to modify our under development test system, so that we didn't have to change the same main VI for every test that we are adding, since we are several persons who'll be adding tests (i.e. conflicts would arise, that we would have to iron out manually every time). The solution in the thread above works very well, by opening a reference to the test sub VI and calling the reference. I then can pass data to the sub VI, and can get the test results from the sub VI. Great!
The problem came when running the program through the Application Builder. The test system starts up fine, but the above method fails miserably, since the sub VI files are no longer there. It seems that the sub VI's are not a part of the exe binary file coming from the Application Builder.
So I'm drawing a blank here. Does anyone have a suggestion on how to to this? I'm only seeing the two options. Either adding the sub VI's in the same main VI file, but then we have to be very careful on not getting conflicts (or fix the conflicts manually when they arise). Or use the dynamic VI referencing, but then the system doesn't work with the Application Builder (which means that this method is out). Is there a third method of doing this?

Hi Mike.
I use LabVIEW 2009.
Well, I actually *can* use the dynamic call solution now. The problem was that (1) the files weren't included in the exe file (fixed by adjusting the Application Builder settings), and (2) the Check if File or Folder Exist VI doesn't work if I try to check if the sub VI is present inside the exe file. The solution here was basically to ommit the whole Check if File or Folder Exist VI, and just do an error check on the Open VI Reference VI. The Open VI Reference VI will fail if trying to open a reference to a file that doesn't exist, so I just wired that to a case loop around the Call By Reference VI.

Autonomy with application builder?

Hello.
I have tried to compile an application with the "application builder" I find in the menu. (see picture below).
My problem is that the .exe file created needs labview to run.
Is it because the version of Labview I have (V 7.1) doesn't include the real "application builder" or because the .exe built with this application builder aren't autonomous but needs Labview to run?
(I want to run the program built on a computer without Labview).
regards.
Vincent.
Attachments:
application_builder.jpg ‏48 KB
labview_menu.jpg ‏39 KB

The resulting exe does not need the complete LabView installed: it is satisified with the LabView run-time engine.
There is an option to include it in the distribution if you create an installer (see the Advanced button).
Otherwise, you can download the Runtime Engine Installer from ni.com:
http://digital.ni.com/softlib.nsf/webcategories/85256410006C055586256BBB002C130D?opendocument&node=1...
Paolo
Paolo
LV 7.0, 7.1, 8.0.1, 2011

Installer built with Application Builder gives error "Cannot install, higher version already installed"

I am having an issue with an installer which I created with the Application Builder. I have a project that I have successfully deployed. Subsequently I created another project (and vi) which is based on a copy of the originals, both with new file names. In the renamed project file, I changed all file names, paths, and all resources, to reflect the new names. I also changed the installer’s destination and install folders, of course. I reset the executable’s version number (in the Build Specification properties) to 1.0 (the original was 1.3). I then successfully built an executable and the application installer. However, when I run the installer (setup.exe), it gives a dialog (after the license screen) that it “Cannot install” because a “higher version already installed”.
I’ve done exactly the same thing with other vi’s and projects of mine, and never had this issue. The installer correctly installs the newly created (and renamed) version where it is told to in the project file. Also, I’ve never had a problem deploying (installing) on my development PC either.
I have carefully checked and rechecked to make sure there is no reference to the original executable or paths. What could be causing this behavior? I want to keep the two projects completely separate, so simply changing the version to higher than 1.3 is not an acceptable solution.
Thanks to anyone in advance for any help and suggestions.
Ed

Yes, LV 8.5 does NOT give me control over the GUID. In the project file there are three such strings:
"App_applicationGUID"
"App_INI_aliasGUID"
"App_INI_GUID"
They all have different numbers and none of them match the GUID or PackageGUID in setup.ini. I don't know if they are related or not, but usually it's not a good idea to mess with (manually edit) files like these (project, ini, etc.) unless you know what you are doing. (For example, I do edit the setup.ini file to change some of the [Dialogs] parameters, but that is based on direction from NI support.)
Anyway, like I said, I've made copies of projects before and never ran into this problem. At least I have a solution, however laborious, in creating a new project file from scratch.
Let me know if anyone has more thoughts on this.
Ed

Application Builder does not work with Eurotherm 24XX-Driver

Hi,
I have to programm the software for a new teststation including some Eurotherm 2216 and a Keithley 2700-instrument in Labview 8.0.
Labview offers drivers for the Keithley 2700 instrument and a driver for the Eurotherm 24XX-series that works well with the Eurotherm 2216.
But if I try to build an application with the application builder, I receive an error message:
The following files include incorrect links to help files. Open the files and correct the links:
C:\Programme\National Instruments\LabVIEW 8.0\instr.lib\ET24XX\_ET24XX.llb\ET24XX Utility Multiple Write To Registers - Floating Point.vi
I checked this file - there are no links to help files included.
I receive a similar error message for the Keithley-Driver.
I attached the file making the problem.
Would be fine, if someone could help me.
Attachments:
Eurotherm testen ohne Messwerterfassung.vi ‏10 KB

Hi,
I had the same error with my application after I transferred it from LV7 to LV8. I used some external files for documentation of the VI's. LV8 does not find these files anymore (old and new location) Open the VI and add the help file again.
Hope this helps.

Intigration with Vignette Application Builder

Similar Messages

Maybe you are looking for