Array to cluster with adjustable cluster size
Hi all
Here I have a dynamic 1D array and I need to convert it into cluster. So I use Array to Cluster function. But I notice that the cluster size is a fix value. How can I adjust the cluster size according to the 1D array size?
Anyone pls give advise..
Thanks....
I won't disagree with any of the previous posters, but would point out a conversion technique I just recently tried and found to work well for my own particular purposes. I've given the method a pretty good workout and not found any obvious flaws yet, but can't 100% guarantee the behavior in all settings.
Anyhow, I've got a fairly good sized project that includes quite a few similar but distinct clusters of booleans. Each has been turned into a typedef, complete with logical names for each cluster element. For some of the data processing I do, I need to iterate over each boolean element in a cluster, do some evaluations, and generate an output boolean cluster. I first structured the code to use the "Cluster to Array" primitive, then auto-index over the resulting array of booleans, perform the evaluations and auto-index an output array-of-booleans, then finally convert back using the "Array to Cluster" primitive. I, too, was kinda bothered by having to hardcode cluster sizes in there...
I found I could instead use the "Typecast" primitive to convert the output array back to my cluster. I simply fed the input cluster into the middle terminal to defin! the datatype. Then the output cluster is automatically the right size and right datatype.
This still is NOT an adjustable cluster size, but it had the following benefits:
1. If the size of my typedef'ed cluster changes during development by adding or removing boolean elements, none of the code breaks! I don't have to go searching through my code for all the "Array to Cluster" primitives, identifying the ones I need to inspect, and then manually changing the cluster size on them one at a time!
2. Some of my processing functions were quite similar to one another. This method allowed me to largely reuse code. I merely had to replace the input and output clusters with the appropriate new typedef. Again, no hardcoded cluster sizes hidden in "Array to Cluster" primitives, and no broken code.
Dunno if your situation is similar, but it gave me something similar to auto-sizing at programming time. (You should test the behavior when you feed arrays of the wrong size into the "Typecast" primitive. It worked for my app's needs, but you should make sure it's right for yours.)
-Kevin P.
Similar Messages
-
Having issue with start weblogic cluster with tangosol cluster
Hi,
Oracle Coherence Version 3.3.1/389p1
Grid Edition: Development mode
We are using Weblogic 8.1.5 with Tangosol 3.3.1 on Linux servers.
And we added the initializing logic in the servlet's init() method to get all NamedCaches and put into the ServletContext.
When we start weblogic cluster, the first weblogic member will startup successfully with following messages :
<Nov 7, 2007 10:12:30 AM EST> <Info> <HTTP> <BEA-101047> <[2007-11-07 10ServletContext(id=259640596,name=clusterqa,context-path=)] initObjects: init>:12:31.565 Oracle Coherence 3.3.1/389p1 <Info> (thread=Main Thread, member=n/a): Loaded operational configuration from resource "zip:/home/server/clusterqa/wls81/DOCVIEW/docqa1/.wlnotdelete/extract/docqa1_DOC_clusterqa/jarfiles/WEB-INF/lib/coherence.jar!/tangosol-coherence.xml"
2007-11-07 10:12:31.598 Oracle Coherence 3.3.1/389p1 <Info> (thread=Main Thread, member=n/a): Loaded operational overrides from file "/home/www/WEB-INF/lib/tangosol-coherence-override.xml"
Oracle Coherence Version 3.3.1/389p1
Grid Edition: Development mode
Copyright (c) 2000-2007 Oracle. All rights reserved.
2007-11-07 10:12:31.938 Oracle Coherence GE 3.3.1/389p1 <Info> (thread=Main Thread, member=n/a): Loaded cache configuration from file "/home/www/WEB-INF/lib/pub-search-cache-config.xml"
2007-11-07 10:12:31.983 Oracle Coherence GE 3.3.1/389p1 <Info> (thread=Main Thread, member=n/a): sun.misc.AtomicLong is not supported on this JVM; using a synchronized counter. Though safe to ignore, you may upgrade to BEA's 1.5 JVM to fix this issue.
2007-11-07 10:12:33.267 Oracle Coherence GE 3.3.1/389p1 <Warning> (thread=Main Thread, member=n/a): UnicastUdpSocket failed to set receive buffer size to 1428 packets (2096304 bytes); actual size is 89 packets (131071 bytes). Consult your OS documentation regarding increasing the maximum socket buffer size. Proceeding with the actual value may cause sub-optimal performance.
2007-11-07 10:12:34.118 Oracle Coherence GE 3.3.1/389p1 <D5> (thread=Cluster, member=n/a): Service Cluster joined the cluster with senior service member n/a
2007-11-07 10:12:37.508 Oracle Coherence GE 3.3.1/389p1 <Info> (thread=Cluster, member=n/a): Created a new cluster with Member(Id=1, Timestamp=2007-11-07 10:12:33.323, Address=10.5.176.86:8088, MachineId=48982, Edition=Grid Edition, Mode=Development, CpuCount=4, SocketCount=2) UID=0x0A05B056000001161AAB782BBF561F98
2007-11-07 10:12:37.736 Oracle Coherence GE 3.3.1/389p1 <D5> (thread=Invocation:Management, member=1): Service Management joined the cluster with senior service member 1
2007-11-07 10:12:38.168 Oracle Coherence GE 3.3.1/389p1 <D5> (thread=DistributedCache, member=1): Service DistributedCache joined the cluster with senior service member 1
<Nov 7, 2007 10:12:38 AM EST> <Info> <HTTP> <BEA-101047> <[ServletContext(id=259640596,name=clusterqa,context-path=)] xslProcessor: init>
But trying to start the second weblogic member server, the startup process is stucked after tangosol cache initialization and the second weblogic member server never up running. Please see following messages :
<Nov 7, 2007 9:49:38 AM EST> <Info> <HTTP> <BEA-101047> <[ServletContext(id=153019550,name=clusterqa,context-path=)] initDSNames: init>
<Nov 7, 2007 9:49:42 AM EST> <Info> <HTTP> <BEA-101047> <[ServletContext(id=153019550,name=clusterqa,context-path=)] initObjects: init>
2007-11-07 09:49:43.156 Oracle Coherence 3.3.1/389p1 <Info> (thread=Main Thread, member=n/a): Loaded operational configuration from resource "zip:/home/server/clusterqa/wls81/DOCVIEW/docqa2/.wlnotdelete/extract/docqa2_DOC_clusterqa/jarfiles/WEB-INF/lib/coherence.jar!/tangosol-coherence.xml"
2007-11-07 09:49:43.188 Oracle Coherence 3.3.1/389p1 <Info> (thread=Main Thread, member=n/a): Loaded operational overrides from file "/home/www/WEB-INF/lib/tangosol-coherence-override.xml"
Oracle Coherence Version 3.3.1/389p1
Grid Edition: Development mode
Copyright (c) 2000-2007 Oracle. All rights reserved.
2007-11-07 09:49:43.528 Oracle Coherence GE 3.3.1/389p1 <Info> (thread=Main Thread, member=n/a): Loaded cache configuration from file "/home/www/WEB-INF/lib/pub-search-cache-config.xml"
2007-11-07 09:49:43.571 Oracle Coherence GE 3.3.1/389p1 <Info> (thread=Main Thread, member=n/a): sun.misc.AtomicLong is not supported on this JVM; using a synchronized counter. Though safe to ignore, you may upgrade to BEA's 1.5 JVM to fix this issue.
2007-11-07 09:49:44.829 Oracle Coherence GE 3.3.1/389p1 <Warning> (thread=Main Thread, member=n/a): UnicastUdpSocket failed to set receive buffer size to 1428 packets (2096304 bytes); actual size is 89 packets (131071 bytes). Consult your OS documentation regarding increasing the maximum socket buffer size. Proceeding with the actual value may cause sub-optimal performance.
2007-11-07 09:49:45.419 Oracle Coherence GE 3.3.1/389p1 <D5> (thread=Cluster, member=n/a): Service Cluster joined the cluster with senior service member n/a
2007-11-07 09:49:45.555 Oracle Coherence GE 3.3.1/389p1 <Info> (thread=Cluster, member=n/a): Failed to satisfy the variance: allowed=16, actual=47
2007-11-07 09:49:45.555 Oracle Coherence GE 3.3.1/389p1 <Info> (thread=Cluster, member=n/a): Increasing allowable variance to 19
2007-11-07 09:49:46.040 Oracle Coherence GE 3.3.1/389p1 <Info> (thread=Cluster, member=n/a): This Member(Id=2, Timestamp=2007-11-07 09:49:45.69, Address=10.5.176.85:8088, MachineId=48981, Edition=Grid Edition, Mode=Development, CpuCount=4, SocketCount=2) joined cluster with senior Member(Id=1, Timestamp=2007-11-07 09:45:10.205, Address=10.5.176.86:8088, MachineId=48982, Edition=Grid Edition, Mode=Development, CpuCount=4, SocketCount=2)
Could you please explain why it happens, and what should I do to resolve this issues ?
Many Thanks,
BingHi, Gene
Thank you for the response. I will send you our full log files and thread dumps.
I just want to give you more details about our cases :
1. This only happened without starting cache servers (com.tangosol.net.DefaultCacheServer).
2. And our application which are running on weblogic cluster will just call "CacheFactory.getCache("XXX")", and running as the Tangosol DataClient.
3. All weblogic member servers will be up running successfully if our cache servers are up running.
Also I tried to test another case :
Suppose all weblogic instances and cache server instances are up running. Now I trying to restart (kill weblogic instance process and restart) one of the weblogic member, It will up running successfully only if add some sleep times after killing weblogic processes and restarting it. Looks like tangosol cluster need certain time to aware the member has left cluster, then the restart process will be successful.
Questions :
1. Should we start our weblogic cluster only after cache server cluster is up running ?
2. How do we decide how many time we should wait before start new process to join the cache cluster ?
Could you please help to explain this one for me and let us if there anyway we can do to avoid the problem.
Many Thanks !!!
Bing -
[URGENT!] illustrator rectangular tool is not working with adjusting the size!!!!
Other tools are working well otherwise the only rectangular tool has problem whenever I try to adjust the size.
I tried 'show bounding box(shift+command+B), but it's still not working.
Please help me with this problem and find attached pics.
The pics above are the captured screen we could find on PC, but on Mac the size is not adjustable. :-(tomato,
I am afraid you have come across the Live Rectangle bug which is limited to the MAC versions starting with 10.7 and 10.8, but not 10.9 (Mavericks) or 10.10 (Yosemite). Hopefully, the bug will be fixed soon.
So a switch to Mavericks or Yosemite with a reinstallation might be the way to solve it here and now.
To get round it in each case, it is possible to Expand the Live Rectangles to get normal old fashioned rectangles, or to Pathfinder>Unite, or to use the Scale Tool or the Free Transform Tool.
A more permanent way round that is to create normal old fashioned rectangles, after running the free script created by Pawel, see this thread with download link:
https://forums.adobe.com/thread/1587587 -
Unable to plot 1-D array with a cluster of 2 elements on an XY graph
I'm Unable to plot a 1-D array with a cluster of 2 elements on an XY graph. The data appears at the input to the graph but nothing is plotted. I'm trying to plot a line connecting each point generated.
Solved!
Go to Solution.
Attachments:
TEST11.vi 13 KBChuck,
0. Do not post VIs with infinite loops! Change the True constant to a control. One of the regular participants on these Forums has commented that using the Abort button to stop a VI is like using a tree to stop a car. It works, but may have undesired consequences!
1. Use a shift register on the For loop also.
2. Inserting into an empty array leaves you with an empty array. Initialize the array outside the loop to a size greater or equal to the maximum size you will be using. Then use Replace Array Subest inside the loop.
3. Just make an array of the cluster of points. No need for the extra cluster.
Lynn
Attachments:
TEST11.2.vi 11 KB -
How I pass a cluster with array of various data type (double, I32, string)
I have to pass from a VI to a Microsoft Visual C++ DLL, a cluster with some arrays of various data type. The problem is with Double array, that during Visual C debug is incorrect:the dimension is correct passed, but not array data. In the DLL I have inserted the C code genereted by LabVIEW. I tried to pass a cluster of only one array of double, and the results is the same. Then, I tried to pass a cluster with scalar number and the result is correct in only one case. If the double data is the first in the cluster, the result is correct; if the first is another data type, such as integer or boolean, the double data is incorrect during the debug of the DLL.
This is the code of my DLL:
// LabViewP
aram.cpp : Defines the entry point for the DLL application.
#include "stdafx.h"
#include "LabViewParam.h"
#include "extcode.h"
BOOL APIENTRY DllMain( HANDLE hModule,
DWORD ul_reason_for_call,
LPVOID lpReserved
switch (ul_reason_for_call)
case DLL_PROCESS_ATTACH:
case DLL_THREAD_ATTACH:
case DLL_THREAD_DETACH:
case DLL_PROCESS_DETACH:
break;
return TRUE;
typedef struct {
long dimSize;
double elt[1];
} TD2;
typedef TD2 **TD2Hdl;
typedef struct {
TD2Hdl elt1;
} TD1;
// This is an example of an exported variable
LABVIEWPARAM_API int nLabViewParamPass=0;
// This is an example of an exported function.
LABVIEWPARAM_API int LabViewParamPass(TD1 *pparam)
double parametro;
int i;
for (i=0;i<(**(*pparam).elt1).dimSize;i++)
parametro=(**(*pparam).elt1).elt[i];
return 42;
// This is the constructor of a class that has been exp
orted.
// see LabViewParam.h for the class definition
CLabViewParam::CLabViewParam()
return;
I use LabVIEW 7.0 and Windows XP.
Sorry for my english.
Thanks to every one for your suggestions.
Filippo> I have to pass from a VI to a Microsoft Visual C++ DLL, a cluster with
> some arrays of various data type. The problem is with Double array,
> that during Visual C debug is incorrect:the dimension is correct
> passed, but not array data. In the DLL I have inserted the C code
> genereted by LabVIEW. I tried to pass a cluster of only one array of
> double, and the results is the same. Then, I tried to pass a cluster
> with scalar number and the result is correct in only one case. If the
> double data is the first in the cluster, the result is correct; if the
> first is another data type, such as integer or boolean, the double
> data is incorrect during the debug of the DLL.
It is hard tell for sure, but you might have alignment problems. The
key symptom
is that you can pass a cluster of big and small fine, but
small big doesn't pass correctly. You might also test this by seeing
what the size of your struct is. For Boolean and Double, sizeof()
should return nine bytes no matter what order the array is in. If you
are getting different sizes, you have two options. You can either order
them such that the sizes work, or you can build the EXE or a wrapper DLL
so that the alignment matches LV's native alignment.
Greg McKaskle -
How can I create a RAWpic-file with header(cluster of 8elements) and 2D Array?
I have created a cluster with 8 "I32"elements (Header). I also got picture information into a 2D array (i converted information from a ROI into a 2Darray("Image pixels(I16)")
Now I want to create a RAW picture file (first the header information followed by the picture information.)
I think I have to convert the Header-cluster into an array with "cluster to array". But even this is not possible(Info:"you cannot combine 2 different clusters"). Then I have to combine the 2 arrays with "insert into array"??? But the header array would be a 1Darray if the "cluster to array conversation" works and the picture information is 2D.
Can anyone help me please?I think this is actually pretty straightforward, barring any byte-order issues. Attached is an image that demonstrates what I think jotthape wants to do.
The key is to let multiple Write File nodes do the work for you. There's no need to combine all the data into a single structure for the write, and avoiding that makes things easier in this case, because you don't have to worry about some of the data being I32 and the rest being I16.
Give this a shot,
John
P.S. It does seem likely that you will run into byte-order problems if you want to read your custom RAW file in using some other piece of Windows software. You can check the forum and the NI site for info on byte order, then ask a new question if you're still having a problem.
Attachments:
writeRaw.png 8 KB -
Array of Cluster with event structure
Hi,
I am having Array of cluster with cluster having 1 String Control , 1 Combo box, 1 Led control and 2 Numeric control. In the combo box i am having two options to select ('Binary' and 'PWM').Whenever Binary is selected then Led control has be enabled and whenever PWM is selected 2 Numeric control has to be enabled.
Is there any way to do this??
Pleas help me...
Regards
Meenatchiactually in my application, the front panel has to have 16 rows of controls (1 string control, 1 combo box, 1 Led control, 2 numeric control).so i planned to keep all those controls in a cluster and create one array.If i didnt so i will have 16x5 controls in my front panel and i have to put 16 event cases for each combo box to do the enable and disable of controls..
is there any simple way to do this..i have attached my front panel view
Attachments:
Untitled10.vi 139 KB -
Do we need to format data and log files with 64k cluster size for sql server 2012?
Do we need to format data and log files with 64k cluster size for sql server 2012?
Does this best practice still applies to sql server 2012 & 2014?Yes. The extent size of SQL Server data files, and the max log block size have not changed with the new versions, so the guidance should remain the same.
Microsoft SQL Server Storage Engine PM -
Write an 1d-array of cluster with 3 elements
Hi,
I have to make a "Power spectral densities" analyse from my waveform data. The results from this VI is an array of cluuster with 3 elemments. Now I want to write this array of cluster with 3 elements to a file. And later it must be able to use this file with EXCEL!!
thanksHi
I found some outer Forum entries about this topic.
Look at this links:
http://forums.ni.com/ni/board/message?board.id=170&message.id=49553&requireLogin=False
http://forums.ni.com/ni/board/message?board.id=170&message.id=51526&requireLogin=False
I hope this helps
Manuel -
Array of cluster with string controll??
Hello again!
Now we have another type of problem. We have an array of clusters. The cluster is built by two controlers. One is a string and the other is a menu ring. How can we get a text in the strings that stays there even if one close the program. The text is supposed to be different. Example: B1, B2 and so on. then we want to be able to choos from a menu ring different options that are coupled with B1, B2 and so on. Best regards.Using "make current values default" will save a set of default values into all controls on the front panel. If you want the values to not just be default but be saved from run-to-run you need serialization of controls. When initializing controls (usually before the main user loop) you feed your controls data from a stored file and at the end of the program the settings are stored back (overwritten) to the same "preference" file. Reading and writing complex data forms might seem like it would be a pain to implement but Labview has a nice method for such data persistence. Use the Advanced>>Data Manipulation>>XML VI's. Flatten your control to XML using, you guest it, "Flatten to XML" then use write XML to file to save settings. Do the reverse to initialize controls by reading XML file and unflattening XML data. I have had nice results with these VIs in the past and although not the most compact data form (we are in the age of 100+GB hard drives so what's a few bytes between friends?) will give you well formatted data with almost no additional work. If you just want default data settings and not data persistence then ignore this message.
Paul
Paul Falkenstein
Coleman Technologies Inc.
CLA, CPI, AIA-Vision
Labview 4.0- 2013, RT, Vision, FPGA -
How can I write a 1d array of cluster with 3 elements to a file?
Hi,
I have to make a "Power spectral densities" analyse from my waveform data. The results from this VI is an array of cluuster with 3 elemments. Now I want to write this array of cluster with 3 elements to a file. And later it must be able to use this file with EXCEL!!
thanksHello schloronzo,
make a for loop feeded with your array. Inside the for loop unbundle
the cluster, "format into string" the 3 values, adding the result to
the ones before and collect them in a shift register. Then save the
resulting string to a txt-file. If you make a good format string then
Excel is able to read your txt-file (use tab a separator and CR/LF
after each 3 values aka "csv format").
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome -
Write 1d array of cluster with 2 elements to file
HI!
I'm new at LabView so I hope the question is very simple to you:
I am using a waveform graph to display several measurements.
Now I want to save these Measuremens. The data are stored in 1d array of cluster with 2 elements.
What is the easiest way to do this??
ThanksIf you are already using waveforms you can simply wire right up to "Write Waveforms to File.vi" in the Waveform palette under Waveform File I/O.
Daniel L. Press
PrimeTest Corp.
www.primetest.com -
We are evaluating the Cluster features of WebLogic and got a eval
license for the Cluster Support.
I am running a default cluster (mycluster) using the default Multicast
address (237.0.0.1) and am seeing
some strange behaviour/errors.
Would appreciate some asistance in this matter.
Our Environment
I created directory in a shared file system to host the cluster.
(h:\kkanth\weblogic)
Created the mycluster directory and other directories as recommended in
the Administrator's guide.
I have two WL Servers (asera190 and asera162) with permanent IP
addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
I'm using a NES proxy on asera190 with the plugin for WL specified in
obj.conf alongwith the other parameters.
I'm able to have both the servers join to cluster mycluster and the WL
Admin Console does display a tree that depicts the cluster as well as
servers in it (server61 and server70). The individual server directories
are being created in h:\kkanth\weblogic\mycluster directory with the
appropriate access.log and weblogic.log files.
When a browser attempts to access a URL such as
http://asera190/weblogic/snoop it does return the proper response, but
all requests are processed by asera162 which is listed first in the
obj.conf. Opening multiple sessions does not cause the requests to be
sent to asera190 which is the second server in the cluster. When
asera162 is shutdown and removed from the cluster, I hoped that
subsequent requests would go to asera190. However , depending on the
origin of the request, different errors were thrown. If I try to access
http://asera190/weblogic/snoop from a browser on asera190, I get an
error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
from asera162 cause "Failure at line 706 of file proxy.cpp".
I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
directory as well as the obj.conf file in the ....\config\ directory of
asera190.
We are running NES 3.5.1 and have setup proxy35.dll appropriately.
weblogic.properties
# THE WEBLOGIC PROPERTIES FILE
# This file, which conforms to the java.util.Properties file
# definition, configures your WebLogic products. You cannot run
# WebLogic Server without setting required configuration properties in
this
# file. Required properties are marked and appear first in the file.
# Details on each entry and important information about configuration
# and security are documented on our website. Please go to:
# http://www.weblogic.com/docs45/admindocs/properties.html
# for full instructions on how to edit this file.
# You do not need to include properties in this file unless you want to
# change the default, embedded property. Some properties on the
# T3AdminProps page are not listed here because the default property
# is being used. You can change the default by adding the property and
# its value to this file.
# You cannot set weblogic.system.home in this file, since the WebLogic
Server
# must know where home is in order to retrieve this file. You can
# change WebLogic home on the command line when you start the
# WebLogic Server.
# CLUSTER USERS: Note that the (shared) per-cluster properties file
should
# contain most all of the properties in this file. The only properties
# that potentially belong in a per-server properties file for a server
# running in a cluster are the registration (startup class) of pinned
# RMI objects, and a few tuning properties that may be different for
# servers in the cluster, depending upon hardware and memory. If you use
# a per-server properties file, please REMOVE all properties except
those
# that are specifically required in the per-server properties file. You
# can find specific notes on clusters by searching through this file for
# "CLUSTER USERS".
# The way this file is organized:
# Core properties (includes REQUIRED and RECOMMENDED)
# Core system properties
# Core security-related properties
# Core security-related properties for SSL
# Core HTTPD administrative properties
# Optional properties
# Administrator properties
# System properties
# System startup files
# System shutdown files
# Security-related properties for Workspaces
# Jolt for WebLogic properties
# WebLogic Enterprise Connectivity properties
# WebLogic File properties
# WebLogic JMS demo properties
# WebLogic RMI demo properties
# WebLogic EJB demo properties
# WebLogic ZAC demo properties
# HTTPD administrative properties
# WebLogic JDBC driver properties
# WebLogic JDBC connection pool management
# WebLogic demo connection pool
# WebLogic HTTP Servlet properties
# Proxy servlet registration
# Classpath servlet registration
# File servlet registration
# ServerSideInclude servlet registration
# PageCompileServlet (used by JHTML)
# JSPServlet (used by JSP)
# ServletServlet registration
# Servlet reload properties
# Servlet ACLs
# WebLogic JHTML properties
# User-written and demo servlet registrations
# CORE PROPERTIES
# You should set these before you start the WebLogic Server the first
time.
# If you need more instructions on individual properties in this
# section, check the same section in the Optional Properties, where
# we've left the long explanations. Or, better yet, go to our
# website and read all about properties, at:
# http://www.weblogic.com/docs45/admindocs/properties.html
# CORE SYSTEM PROPERTIES
# TCP/IP port number at which the WebLogic Server listens for
connections
weblogic.system.listenPort=7001
# CORE SECURITY-RELATED PROPERTIES
# Read important information about security at:
# http://www.weblogic.com/docs45/admindocs/properties.html
# REQUIRED: The system password MUST be set in order to start the
# WebLogic Server. This password is case-sensitive, at least 8
characters.
# The username for the privileged user is ALWAYS "system".
# This username and password also includes httpd access (see
# HTTPD properties below).
weblogic.password.system=kaykayka
# RECOMMEND Set to 'everyone' if HTTPD is enabled
weblogic.allow.execute.weblogic.servlet=everyone
# Set individual ACLs to restrict access to HTTP-related resources,
# such as the Administration servlets.
# To make your own servlets generally available, follow this
# pattern (provide a weblogic.allow.execute) for your packages and
# set ACLs as appropriate.
# CORE SECURITY-RELATED PROPERTIES FOR SSL
# Read important information about SSL at:
# http://www.weblogic.com/docs45/classdocs/API_secure.html
# Enable SSL
# (default if property not defined is false)
weblogic.security.ssl.enable=true
# SSL listen port
weblogic.system.SSLListenPort=7002
# Servlets for SSL
# Authentication servlet for creating tokens for applets
weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationServlet
# Limits number of unclaimed stored tokens
weblogic.security.certificateCacheSize=3
# Capture CA root of client servlet
weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
# Certificates for SSL
# Name of acceptable CA roots
# For client authentication change value to a valid .pem file
#weblogic.security.clientRootCA=SecureServerCA.pem
# Server certificates for SSL
weblogic.security.certificate.server=democert.pem
weblogic.security.key.server=demokey.pem
weblogic.security.certificate.authority=ca.pem
# registration for certificate generator servlet
weblogic.httpd.register.Certificate=utils.certificate
weblogic.allow.execute.weblogic.servlet.Certificate=system
# CORE HTTPD ADMINISTRATIVE PROPERTIES
# True permits the HTTPD to run (default)
# Uncomment this property to disable HTTPD
#weblogic.httpd.enable=false
# If authentication is required, add username/password for each user
# who will be included in an ACL, as in this commented-out example:
#weblogic.password.peter=#8gjsL4*
# OPTIONAL PROPERTIES
# These properties affect the behavior of the WebLogic Server.
# You only need to set these properties if you want
# to change the default setting, which is the property shown.
# ADMINISTRATOR PROPERTIES
# Administrator properties are optional information properties,
# particularly useful for clusters.
#weblogic.administrator.location=3355 California Drive, West Hampshire,
CA 94104
#weblogic.administrator.name=Joe Administrator
#weblogic.administrator.phone=1 415 555 1234
# SYSTEM PROPERTIES
# System properties in this section are set to system defaults
# Performance pack. The shared library must be accessible from your
# PATH (NT) or from your shared library path (UNIX; the name of the
# variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
weblogic.system.nativeIO.enable=true
# Outputs logging information to the console as well as to the log file
weblogic.system.enableConsole=true
# Sets the directory or URL for the WebLogic Admin help pages
# The help pages are shipped in the "docs/adminhelp" directory, in the
# default document root in public_html
weblogic.system.helpPageURL=d:/weblogic/myserver/public_html/docs/adminhelp/
# If you prefer to access the most recent help pages, you can do so
online
# by commenting out the previous property and uncommenting this one:
#weblogic.system.helpPageURL=http://www.weblogic.com/docs45/adminhelp/
# Properties for tuning the server's performance
# Number of WebLogic Server execute threads.
weblogic.system.executeThreadCount=15
# Other optional system properties
# Limits size of weblogic.log (in K) and versions old log
weblogic.system.maxLogFileSize=1024
# Adjust minimum length of password
weblogic.system.minPasswordLen=8
# UNIX only: If running on port 80 on UNIX, enable the setUID program
#weblogic.system.enableSetUID=false
# UNIX only: Unprivileged user to setUID to after starting up
# WebLogic Server on port 80
#weblogic.system.nonPrivUser=nobody
# CLUSTER-SPECIFIC PROPERTIES
# Cluster-specific properties in this section are set to system
defaults.
# CLUSTER USERS: Note that ALL Cluster-specific properties should be set
# in the per-cluster properties file ONLY.
# Time-to-live (number of hops) for the cluster's multicast messages
# (default 1, range 1-255).
#weblogic.cluster.multicastTTL=1
# Sets the load-balancing algorithm to be used between
# replicated services if none is specified. If not specified,
# round-robin is used.
#weblogic.cluster.defaultLoadAlgorithm=round-robin
# SERVER-SPECIFIC CLUSTER PROPERTIES
# Cluster-related properties in this section are set to system defaults.
# CLUSTER USERS: Note that these server-specific cluster-related
properties
# should be set in the per-server properties file ONLY.
# Sets the weight of the individual server for the weight-based
load-balancing.
# Range is 0 - 100.
# Larger numbers increase the amount of traffic routed to this server.
#weblogic.system.weight=100
# SYSTEM STARTUP FILES - Examples
# CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
# objects should be registered in the per-server properties file.
# All other startup classes should be registered in the per-cluster
# properties file.
# For more info on writing and using startup file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs45/classdocs/API_t3.html
# Register a startup class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.startupClass.[virtual_name]=[full_pathname]
# Add arguments for the startup class
#weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
# This example shows the entry for examples/t3client/StartupQuery.java
#weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
#weblogic.system.startupArgs.doquery=\
# query=select * from emp,\
# db=jdbc:weblogic:pool:demoPool
# Other system startup files for use with VisiBroker
# Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
# You must have installed Visigenic 2.5 for use with
# the WebLogic Server before you uncomment these properties
#weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
#weblogic.system.startupArgs.dovisi=\
# clientName=T3Client Manager,\
# connName=T3Connection Manager
# SYSTEM SHUTDOWN FILES - Examples
# For more info on writing and using shutdown file, see the
# Developers Guide "Writing a WebLogic Client application," at
# http://www.weblogic.com/docs45/classdocs/API_t3.html
# Register a shutdown class by giving it a virtual name and
# supplying its full pathname.
#weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
# Add arguments for the shutdown class
#weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
# This example shows the entry for examples/t3client/ShutdownTest.java
#weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
#weblogic.system.shutdownArgs.ShutdownTest=\
# outfile=c:/temp/shutdown.log
# SECURITY-RELATED PROPERTIES FOR WORKSPACES
# For backward compatibility, the following entries disable Access
# Control on Workspaces
weblogic.allow.read.weblogic.workspace=everyone
weblogic.allow.write.weblogic.workspace=everyone
# JOLT FOR WEBLOGIC PROPERTIES
# These properties configure a BEA Jolt connection pool for use with
# the simpapp and bankapp examples, and register a servlet for use with
# with the simpapp example. The default server address provided here
# points to a public TUXEDO server that is hosted by BEA for use with
# this example.
# Servlet registration for simpapp example:
#weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServlet
# Pool creation and cleanup
# note this example is set up to work with the public
# demo TUXEDO server available from BEA's website:
#weblogic.system.startupClass.demojoltpoolStart=\
# bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
#weblogic.system.startupArgs.demojoltpoolStart=\
# poolname=demojoltpool,\
# appaddrlist=//beademo1.beasys.com:8000,\
# failoverlist=//beademo1.beasys.com:8000,\
# minpoolsize=1,\
# maxpoolsize=3
#weblogic.system.shutdownClass.demojoltpoolStop=\
# bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
#weblogic.system.shutdownArgs.demojoltpoolStop=\
# poolname=demojoltpool
# WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
# The registrations enable a BEA IIOP connection pool and
# register servlets for use with the simpapp and university examples.
# Configure for your environment and uncomment to use.
# Uncommenting these properties requires WebLogic Enterprise
Connectivity
# and an operating WebLogic Enterprise Server.
# Servlet registration for simpapp servlet example
#weblogic.httpd.register.SimpappServlet=\
# examples.wlec.servlets.simpapp.SimpappServlet
#weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
# Servlet registration for simpapp EJB example
# (You'll need to add the wlec_ejb_simpapp.jar to the
# weblogic.ejb.deploy property in this file.)
#weblogic.httpd.register.ejbSimpappServlet=\
# examples.wlec.ejb.simpapp.ejbSimpappServlet
#weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
# Pool creation and cleanup for the simpapp example
#weblogic.CORBA.connectionPool.simplepool=\
# appaddrlist=//wlehost:2468,\
# failoverlist=//wlehost:2468,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# domainname=simpapp
# Servlet registration for university Servlet example:
#weblogic.httpd.register.UniversityServlet=\
# examples.wlec.servlets.university.UniversityServlet
#weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
# Pool creation and cleanup for the University example:
#weblogic.CORBA.connectionPool.Univpool=\
# appaddrlist=//wlehost:2498,\
# failoverlist=//wlehost:2498,\
# minpoolsize=2,\
# maxpoolsize=3,\
# username=wleuser,\
# userrole=developer,\
# apppassword=wlepassword,\
# domainname=university
# WEBLOGIC FILE PROPERTIES
# Maps a volume name to a path, for client file read/write
#weblogic.io.fileSystem.[volumeName]=[fullPathName]
# WEBLOGIC JMS DEMO PROPERTIES
# CLUSTER USERS: Note that ALL JMS deployment should be done in the
# per-cluster properties file ONLY.
# You set up a JDBC connection pool if you want persistent messages
# (including durable subscriptions). To use JMS and EJBs in the same
# transaction, both must use the same JDBC connection pool. Uncomment
# the following property to use the default JDBC connection pool
# 'demo', which is defined in the Demo connection pool section of this
file.
#weblogic.jms.connectionPool=demoPool
# The JMS Webshare example demonstrates how the ClientID for a
# durable subscriber is configured in the connection factory:
#weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
#weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
#weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
#weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
# The JMS trader example shows how to use JMS with an EJB. In addition
# to uncommenting the following properties, you must also set up and
# deploy the EJB example examples.ejb.basic.statefulSession.Trader to
# try out this JMS example:
#weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
#weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
#weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
#weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
# Registers the underlying servlet
#weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
# These properties are used with the ServerReceive JMS example,
# which demonstrates how to establish a JMS message consumer
# in a startup class:
#weblogic.system.startupClass.serverReceive=\
# examples.jms.startup.ServerReceive
#weblogic.system.startupArgs.serverReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# These properties are used with the PoolReceive JMS example,
# which demonstrates how to establish a pool of JMS message consumers
# in a startup class:
#weblogic.system.startupClass.poolReceive=\
# examples.jms.startup.PoolReceive
#weblogic.system.startupArgs.poolReceive=\
# connectionFactory=javax.jms.TopicConnectionFactory,\
# topic=javax.jms.exampleTopic
# WEBLOGIC RMI DEMO PROPERTIES
# CLUSTER USERS: Note that pinned RMI objects should be registered
# in the per-server properties file ONLY. All other RMI startup
# classes should be registered in the per-cluster properties file.
# Remote classes registered at startup after the pattern:
#weblogic.system.startupClass.[virtualName]=[fullPackageName]
# These examples can be compiled to see RMI in action. Uncomment to use:
#weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
#weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
# WEBLOGIC EJB DEMO PROPERTIES
# CLUSTER USERS: Note that ALL EJB deployment should be done in the
# per-cluster properties file ONLY.
# See WebLogic Demo Connection Pool below for a connection pool
# to use with these examples.
# Deploys EJBeans. Uncomment the appropriate lines below and
# modify DBMS-related info and paths to match your particular
installation:
#weblogic.ejb.deploy=\
# d:/weblogic/myserver/cluster_ejb.jar, \
# d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
# d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
# d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
# d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
# d:/weblogic/myserver/ejb_extensions_isModified.jar, \
# d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
# d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
# d:/weblogic/myserver/ejb_sequence_oracle.jar, \
# d:/weblogic/myserver/ejb_subclass.jar, \
# d:/weblogic/myserver/jolt_ejb_bankapp.jar
# Servlets used by the EJB basic examples beanManaged and
# containerManaged. Uncomment to use:
#weblogic.httpd.register.beanManaged=\
# examples.ejb.basic.beanManaged.Servlet
#weblogic.httpd.register.containerManaged=\
# examples.ejb.basic.containerManaged.Servlet
# Add a list of users (set the password with
weblogic.password.[username]=XXX)
# to set an ACL for this servlet:
#weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
#weblogic.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
#weblogic.password.user1=user1Password
#weblogic.password.user2=user2Password
# WEBLOGIC ZAC DEMO PROPERTIES
# These registrations enable the ZAC Publish Wizard.
weblogic.zac.enable=true
# Set the publish root for a WebLogic Server. Edit and
# uncomment to use
#weblogic.zac.publishRoot=d:/weblogic/zac
# Set an ACL for each package you publish. The [name] is
# the "Package name" you assign in the ZAC Publish Wizard.
# Publish a package, edit this property, and uncomment to use.
#weblogic.allow.read.weblogic.zac.[name]=[user list]
#weblogic.allow.write.weblogic.zac.[name]=system
# HTTPD ADMINISTRATIVE PROPERTIES
# Enables logging of HTTPD info in common log format and
# sets the log file name (default is "access.log" in "myserver")
weblogic.httpd.enableLogFile=true
weblogic.httpd.logFileName=access.log
# Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
weblogic.httpd.enableEvents=false
# Enables HTTP sessions
weblogic.httpd.session.enable=true
# Sets an optional cookie name. The default name is "WebLogicSession".
# Prior to version 4.0, the default was "TengahSession". To make
# this backward compatible with cookies generated from previous
# installations, you should set this property to "TengahSession".
# Uncomment this line and set this to any string of your choice,
# or comment out this property to use the default.
#weblogic.httpd.session.cookie.name=WebLogicSession
# MIME types
weblogic.httpd.mimeType.text/html=html,htm
weblogic.httpd.mimeType.image/gif=gif
weblogic.httpd.mimeType.image/jpeg=jpeg,jpg
weblogic.httpd.mimeType.application/pdf=pdf
weblogic.httpd.mimeType.application/zip=zip
weblogic.httpd.mimeType.application/x-java-vm=class
weblogic.httpd.mimeType.application/x-java-archive=jar
weblogic.httpd.mimeType.application/x-java-serialized-object=ser
weblogic.httpd.mimeType.application/octet-stream=exe
# In seconds, the keep-alive for HTTP and HTTPS requests
weblogic.httpd.http.keepAliveSecs=60
weblogic.httpd.https.keepAliveSecs=120
# WEBLOGIC JDBC DRIVER PROPERTIES
# Enables JDBC driver logging and sets the file name for the log
# The weblogic.jdbc.logFile is placed in the per-server
# directory (default is "myserver")
weblogic.jdbc.enableLogFile=false
weblogic.jdbc.logFileName=jdbc.log
# WEBLOGIC JDBC CONNECTION POOL MANAGEMENT
# CLUSTER USERS: Note that ALL JDBC connection pools should be set up
# in the per-cluster properties file ONLY.
# For creating JDBC connection pools. This example shows a connection
# pool called "oraclePool" that allows 3 T3Users "guest," "joe," and
"jill"
# to use 4 JDBC connections (with a potential for up to 10 connections,
# incremented by two at a time, with a delay of 1 second between each
# attempt to connect to the database), to an Oracle database server
called
# "DEMO." If more than 4 connections are opened, after 15 minutes,
unused
# connections are dropped from the pool until only 4 connections remain
open.
# Every 10 minutes, any unused connections in the pool are tested and
# refreshed if they are not viable.
#weblogic.jdbc.connectionPool.oraclePool=\
# url=jdbc:weblogic:oracle,\
# driver=weblogic.jdbc.oci.Driver,\
# loginDelaySecs=1,\
# initialCapacity=4,\
# maxCapacity=10,\
# capacityIncrement=2,\
# allowShrinking=true,\
# shrinkPeriodMins=15,\
# refreshMinutes=10,\
# testTable=dual,\
# props=user=SCOTT;password=tiger;server=DEMO
# Get more details on each argument for this property in the
# Administrators Guide on setting properties at:
# http://www.weblogic.com/docs45/admindocs/properties.html
# Set up ACLs for this connection pool with the following:
#weblogic.allow.reserve.weblogic.jdbc.connectionPool.oraclePool=\
# guest,joe,jill
#weblogic.allow.reset.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
#weblogic.allow.shrink.weblogic.jdbc.connectionPool.oraclePool=\
# joe,jill
# This property is an ACL that specifies the users who can
# create dynamic connection poolsTry the following obj.conf file. By the way why are using NES 35 version. If you are using NES 36 you should use proxy36.dll.
Init fn="load-types" mime-types="mime.types"
Init fn="load-modules" funcs="wl-proxy,wl-init" shlib="d:/weblogic/bin/proxy35.dll"
Init fn="wl-init"
Init access="C:/Netscape/SuiteSpot/https-octavia/logs/accessNewELF" format.access="%Ses->client.ip% - %Req->vars.auth-user% [%SYSDATE%] \"%Req->reqpb.clf-request%\" %Req->srvhdrs.clf-status% %Req->srvhdrs.content-length%
\"%Req->headers.referer%\" \"%Req->headers.user-agent%\" %Req->reqpb.method% %Req->reqpb.uri% %Req->reqpb.query% \"%Req->reqpb.protocol%\"" fn="flex-init"
<Object name="tg" ppath="*/weblogic/*">
Service fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001" PathTrim="/weblogic"
</Object>
<Object name="default">
NameTrans fn="pfx2dir" from="/ns-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
NameTrans fn="pfx2dir" from="/mc-icons" dir="C:/Netscape/SuiteSpot/ns-icons"
NameTrans fn="pfx2dir" from="/help" dir="C:/Netscape/SuiteSpot/manual/https/ug"
NameTrans fn="document-root" root="C:/Netscape/SuiteSpot/docs"
PathCheck fn="nt-uri-clean"
PathCheck fn="check-acl" acl="default"
PathCheck fn="find-pathinfo"
PathCheck fn="find-index" index-names="index.html,home.html"
ObjectType fn="type-by-extension"
ObjectType fn="force-type" type="text/plain"
Service method="(GET|HEAD|POST|PUT)" type="text/jsp" fn="wl-proxy" WebLogicCluster="asera190:7001,asera162:7001"
Service method="(GET|HEAD)" type="magnus-internal/imagemap" fn="imagemap"
Service method="(GET|HEAD)" type="magnus-internal/directory" fn="index-common"
Service method="(GET|HEAD)" type="*~magnus-internal/*" fn="send-file"
AddLog fn="flex-log" name="access"
</Object>
<Object ppath="/usr/suitespot/docs/.perf">
Service fn="service-dump"
</Object>
<Object name="cgi">
ObjectType fn="force-type" type="magnus-internal/cgi"
Service fn="send-cgi"
</Object>
Hope this helps
Krishna Kanth wrote:
> We are evaluating the Cluster features of WebLogic and got a eval
> license for the Cluster Support.
> I am running a default cluster (mycluster) using the default Multicast
> address (237.0.0.1) and am seeing
> some strange behaviour/errors.
> Would appreciate some asistance in this matter.
>
> Our Environment
> ----------------
>
> I created directory in a shared file system to host the cluster.
> (h:\kkanth\weblogic)
> Created the mycluster directory and other directories as recommended in
> the Administrator's guide.
>
> I have two WL Servers (asera190 and asera162) with permanent IP
> addresses of 10.1.1.61 and 10.1.1.70 respectively. They run NT 4.0.
> I'm using a NES proxy on asera190 with the plugin for WL specified in
> obj.conf alongwith the other parameters.
>
> I'm able to have both the servers join to cluster mycluster and the WL
> Admin Console does display a tree that depicts the cluster as well as
> servers in it (server61 and server70). The individual server directories
> are being created in h:\kkanth\weblogic\mycluster directory with the
> appropriate access.log and weblogic.log files.
>
> When a browser attempts to access a URL such as
>
> http://asera190/weblogic/snoop it does return the proper response, but
> all requests are processed by asera162 which is listed first in the
> obj.conf. Opening multiple sessions does not cause the requests to be
> sent to asera190 which is the second server in the cluster. When
> asera162 is shutdown and removed from the cluster, I hoped that
> subsequent requests would go to asera190. However , depending on the
> origin of the request, different errors were thrown. If I try to access
> http://asera190/weblogic/snoop from a browser on asera190, I get an
> error "Failure at line 351 of file proxy.cpp" ,while trying the same URL
> from asera162 cause "Failure at line 706 of file proxy.cpp".
>
> I'm attaching the weblogic.properties file kept in h:\kkanth\weblogic
> directory as well as the obj.conf file in the ....\config\ directory of
> asera190.
>
> We are running NES 3.5.1 and have setup proxy35.dll appropriately.
>
> weblogic.properties
> *********
> # THE WEBLOGIC PROPERTIES FILE
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # This file, which conforms to the java.util.Properties file
> # definition, configures your WebLogic products. You cannot run
> # WebLogic Server without setting required configuration properties in
> this
> # file. Required properties are marked and appear first in the file.
> #
> # Details on each entry and important information about configuration
> # and security are documented on our website. Please go to:
> #
> # http://www.weblogic.com/docs45/admindocs/properties.html
> #
> # for full instructions on how to edit this file.
> #
> # You do not need to include properties in this file unless you want to
> # change the default, embedded property. Some properties on the
> # T3AdminProps page are not listed here because the default property
> # is being used. You can change the default by adding the property and
> # its value to this file.
> #
> # You cannot set weblogic.system.home in this file, since the WebLogic
> Server
> # must know where home is in order to retrieve this file. You can
> # change WebLogic home on the command line when you start the
> # WebLogic Server.
> #
> # CLUSTER USERS: Note that the (shared) per-cluster properties file
> should
> # contain most all of the properties in this file. The only properties
> # that potentially belong in a per-server properties file for a server
> # running in a cluster are the registration (startup class) of pinned
> # RMI objects, and a few tuning properties that may be different for
> # servers in the cluster, depending upon hardware and memory. If you use
>
> # a per-server properties file, please REMOVE all properties except
> those
> # that are specifically required in the per-server properties file. You
> # can find specific notes on clusters by searching through this file for
>
> # "CLUSTER USERS".
> #
> # -------------------------------------------------
> # The way this file is organized:
> # Core properties (includes REQUIRED and RECOMMENDED)
> # Core system properties
> # Core security-related properties
> # Core security-related properties for SSL
> # Core HTTPD administrative properties
> #
> # Optional properties
> # Administrator properties
> # System properties
> # System startup files
> # System shutdown files
> # Security-related properties for Workspaces
> # Jolt for WebLogic properties
> # WebLogic Enterprise Connectivity properties
> # WebLogic File properties
> # WebLogic JMS demo properties
> # WebLogic RMI demo properties
> # WebLogic EJB demo properties
> # WebLogic ZAC demo properties
> # HTTPD administrative properties
> # WebLogic JDBC driver properties
> # WebLogic JDBC connection pool management
> # WebLogic demo connection pool
> # WebLogic HTTP Servlet properties
> # Proxy servlet registration
> # Classpath servlet registration
> # File servlet registration
> # ServerSideInclude servlet registration
> # PageCompileServlet (used by JHTML)
> # JSPServlet (used by JSP)
> # ServletServlet registration
> # Servlet reload properties
> # Servlet ACLs
> # WebLogic JHTML properties
> # User-written and demo servlet registrations
> # -------------------------------------------------
>
> #################################################################
> # CORE PROPERTIES
> # -------------------------------------------------
> # You should set these before you start the WebLogic Server the first
> time.
> # If you need more instructions on individual properties in this
> # section, check the same section in the Optional Properties, where
> # we've left the long explanations. Or, better yet, go to our
> # website and read all about properties, at:
> # http://www.weblogic.com/docs45/admindocs/properties.html
> #################################################################
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE SYSTEM PROPERTIES
> # -------------------------------------------------
> # TCP/IP port number at which the WebLogic Server listens for
> connections
> weblogic.system.listenPort=7001
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE SECURITY-RELATED PROPERTIES
> # -------------------------------------------------
> # Read important information about security at:
> #
> # http://www.weblogic.com/docs45/admindocs/properties.html
> #
> # REQUIRED: The system password MUST be set in order to start the
> # WebLogic Server. This password is case-sensitive, at least 8
> characters.
> # The username for the privileged user is ALWAYS "system".
> # This username and password also includes httpd access (see
> # HTTPD properties below).
> weblogic.password.system=kaykayka
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # RECOMMEND Set to 'everyone' if HTTPD is enabled
> weblogic.allow.execute.weblogic.servlet=everyone
> # Set individual ACLs to restrict access to HTTP-related resources,
> # such as the Administration servlets.
> # To make your own servlets generally available, follow this
> # pattern (provide a weblogic.allow.execute) for your packages and
> # set ACLs as appropriate.
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE SECURITY-RELATED PROPERTIES FOR SSL
> # ------------------------------------------------
> # Read important information about SSL at:
> #
> # http://www.weblogic.com/docs45/classdocs/API_secure.html
> #
> # Enable SSL
> # (default if property not defined is false)
> weblogic.security.ssl.enable=true
> #
> # SSL listen port
> weblogic.system.SSLListenPort=7002
>
> # Servlets for SSL
> # ------------------------------------------------
> # Authentication servlet for creating tokens for applets
> weblogic.httpd.register.authenticated=weblogic.t3.srvr.ClientAuthenticationServlet
>
> # Limits number of unclaimed stored tokens
> weblogic.security.certificateCacheSize=3
> # Capture CA root of client servlet
> weblogic.httpd.register.T3AdminCaptureRootCA=admin.T3AdminCaptureRootCA
>
> # Certificates for SSL
> # ------------------------------------------------
> # Name of acceptable CA roots
> # For client authentication change value to a valid .pem file
> #weblogic.security.clientRootCA=SecureServerCA.pem
> #
> # Server certificates for SSL
> # ------------------------------------------------
> weblogic.security.certificate.server=democert.pem
> weblogic.security.key.server=demokey.pem
> weblogic.security.certificate.authority=ca.pem
>
> # registration for certificate generator servlet
> weblogic.httpd.register.Certificate=utils.certificate
> weblogic.allow.execute.weblogic.servlet.Certificate=system
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CORE HTTPD ADMINISTRATIVE PROPERTIES
> # ------------------------------------------------
> # True permits the HTTPD to run (default)
> # Uncomment this property to disable HTTPD
> #weblogic.httpd.enable=false
> #
> # If authentication is required, add username/password for each user
> # who will be included in an ACL, as in this commented-out example:
> #weblogic.password.peter=#8gjsL4*
>
> #################################################################
> # OPTIONAL PROPERTIES
> # ------------------------------------------------
> # These properties affect the behavior of the WebLogic Server.
> # You only need to set these properties if you want
> # to change the default setting, which is the property shown.
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # ADMINISTRATOR PROPERTIES
> # ------------------------------------------------
> # Administrator properties are optional information properties,
> # particularly useful for clusters.
> #weblogic.administrator.location=3355 California Drive, West Hampshire,
> CA 94104
> #weblogic.administrator.name=Joe Administrator
> #weblogic.administrator.phone=1 415 555 1234
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SYSTEM PROPERTIES
> # ------------------------------------------------
> # System properties in this section are set to system defaults
>
> # Performance pack. The shared library must be accessible from your
> # PATH (NT) or from your shared library path (UNIX; the name of the
> # variable varies: LD_LIBRARY_PATH, SHLIB_PATH, etc.)
> weblogic.system.nativeIO.enable=true
>
> # Outputs logging information to the console as well as to the log file
> weblogic.system.enableConsole=true
>
> # Sets the directory or URL for the WebLogic Admin help pages
> # The help pages are shipped in the "docs/adminhelp" directory, in the
> # default document root in public_html
> weblogic.system.helpPageURL=d:/weblogic/myserver/public_html/docs/adminhelp/
>
> # If you prefer to access the most recent help pages, you can do so
> online
> # by commenting out the previous property and uncommenting this one:
> #weblogic.system.helpPageURL=http://www.weblogic.com/docs45/adminhelp/
>
> # Properties for tuning the server's performance
> # ------------------------------------------------
> # Number of WebLogic Server execute threads.
> weblogic.system.executeThreadCount=15
>
> # Other optional system properties
> # ------------------------------------------------
> # Limits size of weblogic.log (in K) and versions old log
> weblogic.system.maxLogFileSize=1024
>
> # Adjust minimum length of password
> weblogic.system.minPasswordLen=8
>
> # UNIX only: If running on port 80 on UNIX, enable the setUID program
> #weblogic.system.enableSetUID=false
>
> # UNIX only: Unprivileged user to setUID to after starting up
> # WebLogic Server on port 80
> #weblogic.system.nonPrivUser=nobody
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # CLUSTER-SPECIFIC PROPERTIES
> # ------------------------------------------------
> # Cluster-specific properties in this section are set to system
> defaults.
> # CLUSTER USERS: Note that ALL Cluster-specific properties should be set
>
> # in the per-cluster properties file ONLY.
> #
> # Time-to-live (number of hops) for the cluster's multicast messages
> # (default 1, range 1-255).
> #weblogic.cluster.multicastTTL=1
> #
> # Sets the load-balancing algorithm to be used between
> # replicated services if none is specified. If not specified,
> # round-robin is used.
> #weblogic.cluster.defaultLoadAlgorithm=round-robin
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SERVER-SPECIFIC CLUSTER PROPERTIES
> # ------------------------------------------------
> # Cluster-related properties in this section are set to system defaults.
>
> # CLUSTER USERS: Note that these server-specific cluster-related
> properties
> # should be set in the per-server properties file ONLY.
> #
> # Sets the weight of the individual server for the weight-based
> load-balancing.
> # Range is 0 - 100.
> # Larger numbers increase the amount of traffic routed to this server.
> #weblogic.system.weight=100
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SYSTEM STARTUP FILES - Examples
> # ------------------------------------------------
> # CLUSTER USERS: Note that ONLY startup registrations for pinned RMI
> # objects should be registered in the per-server properties file.
> # All other startup classes should be registered in the per-cluster
> # properties file.
> #
> # For more info on writing and using startup file, see the
> # Developers Guide "Writing a WebLogic Client application," at
> # http://www.weblogic.com/docs45/classdocs/API_t3.html
> #
> # Register a startup class by giving it a virtual name and
> # supplying its full pathname.
> #weblogic.system.startupClass.[virtual_name]=[full_pathname]
> #
> # Add arguments for the startup class
> #weblogic.system.startupArgs.[virtual_name]={argname]=[argvalue]
> #
> # This example shows the entry for examples/t3client/StartupQuery.java
> #weblogic.system.startupClass.doquery=examples.t3client.StartupQuery
> #weblogic.system.startupArgs.doquery=\
> # query=select * from emp,\
> # db=jdbc:weblogic:pool:demoPool
> #
> # Other system startup files for use with VisiBroker
> # ------------------------------------------------
> # Starts the VisiBroker WebLogic Server proxy with the WebLogic Server
> # You must have installed Visigenic 2.5 for use with
> # the WebLogic Server before you uncomment these properties
> #weblogic.system.startupClass.dovisi=weblogic.corba.visi.t3server.Startup
>
> #weblogic.system.startupArgs.dovisi=\
> # clientName=T3Client Manager,\
> # connName=T3Connection Manager
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SYSTEM SHUTDOWN FILES - Examples
> # ------------------------------------------------
> # For more info on writing and using shutdown file, see the
> # Developers Guide "Writing a WebLogic Client application," at
> # http://www.weblogic.com/docs45/classdocs/API_t3.html
> #
> # Register a shutdown class by giving it a virtual name and
> # supplying its full pathname.
> #weblogic.system.shutdownClass.[virtual_name]=[full_pathname]
> #
> # Add arguments for the shutdown class
> #weblogic.system.shutdownArgs.[virtualName]={argname]=[argvalue]
> #
> # This example shows the entry for examples/t3client/ShutdownTest.java
> #weblogic.system.shutdownClass.ShutdownTest=examples.t3client.ShutdownTest
>
> #weblogic.system.shutdownArgs.ShutdownTest=\
> # outfile=c:/temp/shutdown.log
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # SECURITY-RELATED PROPERTIES FOR WORKSPACES
> # ------------------------------------------------
> # For backward compatibility, the following entries disable Access
> # Control on Workspaces
> weblogic.allow.read.weblogic.workspace=everyone
> weblogic.allow.write.weblogic.workspace=everyone
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # JOLT FOR WEBLOGIC PROPERTIES
> # ------------------------------------------------
> # These properties configure a BEA Jolt connection pool for use with
> # the simpapp and bankapp examples, and register a servlet for use with
> # with the simpapp example. The default server address provided here
> # points to a public TUXEDO server that is hosted by BEA for use with
> # this example.
> #
> # Servlet registration for simpapp example:
> # ------------------------------------------------
> #weblogic.httpd.register.simpapp=examples.jolt.servlet.simpapp.SimpAppServlet
>
> #
> # Pool creation and cleanup
> # note this example is set up to work with the public
> # demo TUXEDO server available from BEA's website:
> # ------------------------------------------------
> #weblogic.system.startupClass.demojoltpoolStart=\
> # bea.jolt.pool.servlet.weblogic.PoolManagerStartUp
> #weblogic.system.startupArgs.demojoltpoolStart=\
> # poolname=demojoltpool,\
> # appaddrlist=//beademo1.beasys.com:8000,\
> # failoverlist=//beademo1.beasys.com:8000,\
> # minpoolsize=1,\
> # maxpoolsize=3
> #
> #weblogic.system.shutdownClass.demojoltpoolStop=\
> # bea.jolt.pool.servlet.weblogic.PoolManagerShutDown
> #weblogic.system.shutdownArgs.demojoltpoolStop=\
> # poolname=demojoltpool
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC ENTERPRISE CONNECTIVITY PROPERTIES
> # ------------------------------------------------
> # The registrations enable a BEA IIOP connection pool and
> # register servlets for use with the simpapp and university examples.
> # Configure for your environment and uncomment to use.
> # Uncommenting these properties requires WebLogic Enterprise
> Connectivity
> # and an operating WebLogic Enterprise Server.
> #
> # Servlet registration for simpapp servlet example
> # ------------------------------------------------
> #weblogic.httpd.register.SimpappServlet=\
> # examples.wlec.servlets.simpapp.SimpappServlet
> #
> #weblogic.allow.execute.weblogic.servlet.SimpappServlet=everyone
> #
> # Servlet registration for simpapp EJB example
> # (You'll need to add the wlec_ejb_simpapp.jar to the
> # weblogic.ejb.deploy property in this file.)
> # --------------------------------------------
> #weblogic.httpd.register.ejbSimpappServlet=\
> # examples.wlec.ejb.simpapp.ejbSimpappServlet
> #weblogic.allow.execute.weblogic.servlet.ejbSimpappServlet=everyone
> #
> # Pool creation and cleanup for the simpapp example
> # -------------------------------------------------
> #weblogic.CORBA.connectionPool.simplepool=\
> # appaddrlist=//wlehost:2468,\
> # failoverlist=//wlehost:2468,\
> # minpoolsize=2,\
> # maxpoolsize=3,\
> # username=wleuser,\
> # userrole=developer,\
> # domainname=simpapp
> #
> # Servlet registration for university Servlet example:
> # ---------------------------------------------------
> #weblogic.httpd.register.UniversityServlet=\
> # examples.wlec.servlets.university.UniversityServlet
> #weblogic.allow.execute.weblogic.servlet.UniversityServlet=everyone
> #
> # Pool creation and cleanup for the University example:
> # ----------------------------------------------------
> #weblogic.CORBA.connectionPool.Univpool=\
> # appaddrlist=//wlehost:2498,\
> # failoverlist=//wlehost:2498,\
> # minpoolsize=2,\
> # maxpoolsize=3,\
> # username=wleuser,\
> # userrole=developer,\
> # apppassword=wlepassword,\
> # domainname=university
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC FILE PROPERTIES
> # ------------------------------------------------
> # Maps a volume name to a path, for client file read/write
> #weblogic.io.fileSystem.[volumeName]=[fullPathName]
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC JMS DEMO PROPERTIES
> # -------------------------------------------------
> # CLUSTER USERS: Note that ALL JMS deployment should be done in the
> # per-cluster properties file ONLY.
> #
> # You set up a JDBC connection pool if you want persistent messages
> # (including durable subscriptions). To use JMS and EJBs in the same
> # transaction, both must use the same JDBC connection pool. Uncomment
> # the following property to use the default JDBC connection pool
> # 'demo', which is defined in the Demo connection pool section of this
> file.
> #
> #weblogic.jms.connectionPool=demoPool
> #
> # The JMS Webshare example demonstrates how the ClientID for a
> # durable subscriber is configured in the connection factory:
> #
> #weblogic.jms.topic.webshareTopic=jms.topic.webshareTopic
> #weblogic.jms.connectionFactoryName.webshare=jms.connection.webshareFactory
>
> #weblogic.jms.connectionFactoryArgs.webshare=ClientID=webshareUser
> #weblogic.httpd.register.webshare=examples.jms.webshare.WebshareServlet
> #
> # The JMS trader example shows how to use JMS with an EJB. In addition
> # to uncommenting the following properties, you must also set up and
> # deploy the EJB example examples.ejb.basic.statefulSession.Trader to
> # try out this JMS example:
> #
> #weblogic.jms.topic.exampleTopic=javax.jms.exampleTopic
> #weblogic.jms.connectionFactoryName.trader=jms.connection.traderFactory
> #weblogic.jms.connectionFactoryArgs.trader=ClientID=traderReceive
> #weblogic.httpd.register.jmstrader=examples.jms.trader.TraderServlet
> #
> # Registers the underlying servlet
> #weblogic.httpd.register.jmssender=examples.jms.sender.SenderServlet
> #
> # These properties are used with the ServerReceive JMS example,
> # which demonstrates how to establish a JMS message consumer
> # in a startup class:
> #
> #weblogic.system.startupClass.serverReceive=\
> # examples.jms.startup.ServerReceive
> #weblogic.system.startupArgs.serverReceive=\
> # connectionFactory=javax.jms.TopicConnectionFactory,\
> # topic=javax.jms.exampleTopic
> #
> # These properties are used with the PoolReceive JMS example,
> # which demonstrates how to establish a pool of JMS message consumers
> # in a startup class:
> #weblogic.system.startupClass.poolReceive=\
> # examples.jms.startup.PoolReceive
> #weblogic.system.startupArgs.poolReceive=\
> # connectionFactory=javax.jms.TopicConnectionFactory,\
> # topic=javax.jms.exampleTopic
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC RMI DEMO PROPERTIES
> # ------------------------------------------------
> # CLUSTER USERS: Note that pinned RMI objects should be registered
> # in the per-server properties file ONLY. All other RMI startup
> # classes should be registered in the per-cluster properties file.
> #
> # Remote classes registered at startup after the pattern:
> #weblogic.system.startupClass.[virtualName]=[fullPackageName]
> #
> # These examples can be compiled to see RMI in action. Uncomment to use:
>
> #weblogic.system.startupClass.multihello=examples.rmi.multihello.HelloImpl
>
> #weblogic.system.startupClass.hello=examples.rmi.hello.HelloImpl
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC EJB DEMO PROPERTIES
> # -------------------------------------------------
> # CLUSTER USERS: Note that ALL EJB deployment should be done in the
> # per-cluster properties file ONLY.
> #
> # See WebLogic Demo Connection Pool below for a connection pool
> # to use with these examples.
> #
> # Deploys EJBeans. Uncomment the appropriate lines below and
> # modify DBMS-related info and paths to match your particular
> installation:
> #weblogic.ejb.deploy=\
> # d:/weblogic/myserver/cluster_ejb.jar, \
> # d:/weblogic/myserver/ejb_basic_beanManaged.jar, \
> # d:/weblogic/myserver/ejb_basic_containerManaged.jar, \
> # d:/weblogic/myserver/ejb_basic_statefulSession.jar, \
> # d:/weblogic/myserver/ejb_basic_statelessSession.jar, \
> # d:/weblogic/myserver/ejb_extensions_isModified.jar, \
> # d:/weblogic/myserver/ejb_extensions_isModifiedBeanManaged.jar, \
>
> # d:/weblogic/myserver/ejb_sequence_jdbc.jar, \
> # d:/weblogic/myserver/ejb_sequence_oracle.jar, \
> # d:/weblogic/myserver/ejb_subclass.jar, \
> # d:/weblogic/myserver/jolt_ejb_bankapp.jar
> #
> # Servlets used by the EJB basic examples beanManaged and
> # containerManaged. Uncomment to use:
> #weblogic.httpd.register.beanManaged=\
> # examples.ejb.basic.beanManaged.Servlet
> #weblogic.httpd.register.containerManaged=\
> # examples.ejb.basic.containerManaged.Servlet
> #
> # Add a list of users (set the password with
> weblogic.password.[username]=XXX)
> # to set an ACL for this servlet:
> #weblogic.allow.execute.weblogic.servlet.beanManaged=user1,user2,etc
> #weblogic.allow.execute.weblogic.servlet.containerManaged=user1,user2,etc
>
> #weblogic.password.user1=user1Password
> #weblogic.password.user2=user2Password
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # WEBLOGIC ZAC DEMO PROPERTIES
> # -------------------------------------------------
> # These registrations enable the ZAC Publish Wizard.
> #
> weblogic.zac.enable=true
> #
> # Set the publish root for a WebLogic Server. Edit and
> # uncomment to use
> #
> #weblogic.zac.publishRoot=d:/weblogic/zac
> #
> # Set an ACL for each package you publish. The [name] is
> # the "Package name" you assign in the ZAC Publish Wizard.
> # Publish a package, edit this property, and uncomment to use.
> #weblogic.allow.read.weblogic.zac.[name]=[user list]
> #weblogic.allow.write.weblogic.zac.[name]=system
>
> # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # # #
> # HTTPD ADMINISTRATIVE PROPERTIES
> # ------------------------------------------------
> # Enables logging of HTTPD info in common log format and
> # sets the log file name (default is "access.log" in "myserver")
> weblogic.httpd.enableLogFile=true
> weblogic.httpd.logFileName=access.log
>
> # Tracks HTTPD requests with events delivered to WEBLOGIC.LOG.HTTPD
> weblogic.httpd.enableEvents=false
>
> # Enables HTTP sessions
> weblogic.httpd.session.enable=true
>
> # Sets an optional cookie name. The default name is "WebLogicSession".
> # Prior to version 4.0, the default was "TengahSession". To make
> # this backward compatible with cookies generated from previous
> # installations, you should set this property to "TengahSession".
> # Uncomment t -
How do i send an array of clusters with variable size over TCP/IP?
Hi,
I'm trying to send an array of clusters with varible size over TCP/IP,. But I'm facing the following problems:
1) I need to accept the size of array data from the user and increase the size dynamically.
I'm doing this using the property node but how do I convey the new size to my TCP read?
2) I need to wire an input to my 'bytes to read' of the TCP read.
But the number of bytes to read changes dynamically
How do I ensure the correct number of bytes are read and reflected on the client side?
3) Is there anyway I can use global varibles over a network such that their values are updated just as if they would on one computer?
Will be a great help if someone posts a solution!
Thank you...twilightfan wrote:
Altenbach,
... xml string. ...number of columns that I'm varying using property node s... I solved these problems by using a local variable as the type input ...o TCP read is creating a problem.... second TCP read gets truncated data because
its no longer just the first four bytes that specify the length of the data, it could be more as my array of cluster can be pretty huge.
Instead of writing long and complicated sentences that make little sense, why don't you simply show us your code?
What does any of this have to do with xml strings???? I don't see how using a local variable as type input changes anything. The user cannot interact with "property nodes", just with controls. Please clarify. Once the array of clusters is flattened to a string you only have one size that describes the size of the data, no matter how huge it is (as long as it is within the limits of I32). Similarly, you read the string of that same defined length and form the array of clusters from it. How big are the strings? What is your definition of "huge"?
Here's is my earlier code, but now dealing with an array of clusters. Not much of a change. Since you have columns, you want 2D. Add as many diensions you want, but make sure that the control, diagram constant, and indicator all match.
The snipped shows for a 1D array, while the attached VI shows the same for a 2D array. Same difference.
Message Edited by altenbach on 01-31-2010 01:13 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
FlattenArrayOfClusters.vi 12 KB
ioclusters3MOD.png 25 KB -
How to create an intensity waveform graph cluster with t_0 and dt ?
Hi all,
I would like to know whether it is possible to create an intensity waveform like you can do with a 1-d waveform (with "build waveform") so that you get a cluster with the waveform array, the t_0, the dtand the attributes.
If not I would like to know the following: I use references to cluster typedefs to update my controls and indicaters on the front panel. Now if I use a property node for the intensity graph to set the offset and multiplier on the x-scale, the x-scale on the graphs on the sub-VI work perfectly, however not on the real front panel, probably since these get updated through a reference. Does anyone have a clue how to fix this?
Regards, PieterYou are only writing the "value" of the type definition via the property node. This does not include properties such as offset and multiplier.
On a sidenote, you are using way too much code for most operations.
For example, the to-I32 can be placed on the cluster, so only one instance is needed.
Also property nodes are resizeable, so only one instance is needed.
There are also Rube Goldberg constructs, such as ">0 *AND* TRUE", which is the same as a simple ">0"
Overall, you are really fragmenting memory by constantly building and then resizing arrays to keep them at a max size of 2880. This can cause performance problems due to the constant need of reallocations. It might be better to use fixed size arrays and do things "in place".
Message Edited by altenbach on 03-19-2009 09:57 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
OneIsEnough.png 8 KB
CombineProperties.png 3 KB
Maybe you are looking for
-
Hello, I created a form in Acrobat Professional 8, and it works perfectly. When I send it to someone using Adobe Reader X they can not type in the fields or use the submit button. Any ideas on what the problem could be? I have reader enabled the form
-
Hey Guys, My eMac Screen shakes a little if yo look at a corner. It looks like a vibration. The speaker volume thing doesn't work, neither does resetting nvram or PRAM or even changing the resolution. What can i do? Oh, i know a lot about macs, but n
-
Creating new material using i/b MATMAS IDOC
Hi mates, I'm trying to create a material in R/3 using an inbound MATMAS IDOC. The material type I use is confiugured for internal number assignment. So, I'm leaving the E1MARAM-MATNR blank. But, the IDOC failing saying 'No Material Transfered'. I'm
-
I have created a pdf form from Indesign. Is there a way to enable the person filling out the form to then click a button (created in indesign) that collects their answers and exports them in a preformatted pdf? It's not something I'm aware of but a c
-
I bought a new laptop that has IE 11 and I need to downgrade to IE9 (Windows 7 Professional)
I bought a new laptop that has Win 7 Prof and IE 11 installed. I need IE 9 to run a remote login app for my work. How do I downgrade to IE 9? IE 11 came installed, not through an update so I can't delete the update.