User interface through a network

Hello !
Is there a way (API or something else) in Java which would allow to load the UI
through a network? (except WebStart).
I mean something like Orace*Forms or telnet-session that is with no graphic in it.
Best wishes
Anton

The bit I didn't understand was whether you needed a
Graphical User Interface (GUI), or just a text based
interface.Just a text based interface.
Let me explain my task. I have two parts:
server side (EJB-based) and, of course, client (I don't know under what OS it will work). As for server side -- all is clear, I change something in it and a client automaticaly uses methods that I've changed. So all the client need to store localy is some interface (or declarations) to the main (executive) methods.
This is, unfortunatelly, not true for the user interface.
My question is: Is it possible to write in Java
text based user interface that can be sent to the client
over the network ? (for instance, over the telnet-protocol, so i don't care about what the telnet-client will be used, java-based or c-based or anything else).

Similar Messages

Use networked Users.ini in deployed simple user interface

I'm using the Simple LabVIEW UI that comes with TestStand 2014. I have customised it to my requirements, but have a small issue. I want to deploy the interface to numerous production PC's but cannot workout how to get the interface to use a networked Users.ini, at Login on those PC's. Does anyone know how to make the user interface use a networked Users.ini? I know that in TestStand 2014 you can use the menus Configure>Station Options>User Manager to tell it where to find a networked Users.ini. I don't know how to make the Simple LabVIEW UI do the same thing. Hopefully I've missed something obvious and will soon be felling rather stupid.
Thanks
Colin

Colin,
This setting is stored in TestExec.ini. You can deploy this by following this link: http://digital.ni.com/public.nsf/allkb/E5E4FEADEFE6023D862571590000C5CC
Here's another link:http://zone.ni.com/reference/en-XX/help/370052N-01/tsdeploysystem/infotopics/includingcfgfiles/
TestExec.ini is just 1 of many cfg files for TestStand. They all need to be in the same folder. Generally the ProgramData\National Instruments\<TestStand>\Cfg folder. The exception is Users.ini. It is the only cfg file that can be in a different location (as you have discovered)
So I recommend pointing to the users.ini on your development machine and then adding TestExec.ini to your workspace. Then you need ot put it in the Cfg directory on the deployment machine. Be careful though because there are a lot of other settings stored in that file.
Hope this helps,

I accidently deleted the Wi-fi interface in the Networks Menu window. HELP!

My computer is now saying that my Wi-Fi is not configured. It wont let me re-add the interface through the network window and I don't know what else to do! It's currently only working through Ethernet. HELP!
WIFI in the tool bar says "Wi-Fi: Not Configured."

Restart the computer and try again. If there's no change, then from the Location menu at the top of the preference pane, select Edit Locations. A sheet will drop down. Click the plus-sign button to create a new location. Give it any name you want. In the new location, set up the Wi-Fi service with the same settings you used before. Click Apply and test.

Can you change size of fonts in premiere pro user interface -- the text is often so small it is hard to read

The text is often so small it is hard to read. It would be nice if as in the Blender animation program you can easily increase the size of fonts used in the program's user interface, through the "preferences" menu item.

Hi Ewporter,
Sorry, sounds like an excellent feature request, though. Make it here: http://adobe.ly/feature_request
Thanks,
Kevin

I'm trying to delete multiple users through my network loaner. how do i do that?

I'm trying to delete multiple users through my network loaner. how do i do that?

Navigate to Settings>iCloud>iCloud Photo Settings and then select Turn Off Photo Sharing and then reenable it.

I do not see the user interface for the Logic software instruments. I can hear them play through my midi keyboard but I cannot see them to adjust parameters. Please advise.

I do not see the user interface for the Logic Pro software instruments. I can hear them play through my midi keyboard but cannot see them to adjust the parameters. Please advise.

Couple of things - you can open the interface for any instrument or plug-in by double-clicking its insert slot on the channel strip. You can configure Logic to automatically open the interface for a plug-in when you first instantiate it in the preferences. Go to Logic Pro > Preferences > Display > Mixer, and check the box for "Open plug-in window on insertion".

10.6: Apple and our customers place a high value on simple, refined, creative, well thought through interfaces. They take more work but are worth it. Apple sets a high bar. If your user interface is complex or less than very good it may be rejected

i am newbie in IOS i am web developer
so i use html 5 and i development jquery mobile based application.
in my application i just call view from web.I used objective c webview .
but my application rejected following issues
- Included low resolution/jagged image/s; see screenshot
- Portions of your app loaded, refreshed, ran, and/or responded very slowly.
- Was not optimized to support the device screen size and/or resolution; see screenshot
- Did not integrate with iOS features.
they said your app is slow but app speed is good(you can see here : http://teknonova.com/Map)
they said did not integrate with ios features .yes i just call URL from web view?is it illegal?
and they gave issues screenshot there is no problem with screenshot .it is good : (http://a1523.phobos.apple.com/us/r30/Purple/v4/c3/76/8a/c3768ae0-9b41-820f-9315- 40db2afc57b6/temp..gwvpnmiu.png)
what should i do?
should i delete and add new app?

10.6: Apple and our customers place a high value on simple, refined, creative, well thought through interfaces. They take more work but are worth it. Apple sets a high bar. If your user interface is complex or less than very good it may be rejected
for this problem what is a good solutions, how need to solve our problem, we need to published our apps. so plez telme the solution for this resons

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

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

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

Sharing an iTunes Library across multiple user account and a network.

Sharing an iTunes Music Library across multiple user accounts.
Hello Everybody!
Firstly, this was designed to be run in Mac OS X 10.4 Tiger. It will not work with earlier versions of Mac OS X! Sorry.
Here's a handy tip for keeping your hard drive neat and tidy, it also saves space, what in effect will be done is an iTunes music library will be shared amongst multiple users on the same machine. There are advantages and disadvantages to using this method.
• Firstly I think it might be worthwhile to state the advantages and disadvantages to using this approach.
The advantages include:
- Space will be saved, as no duplicate files will occur.
- The administrator will be able to have complete control over the content of the iTunes library, this may be useful for restricting the content of the Library; particularly for example if computer is being used at and education institution, business or any other sort of institution where things such as explicit content would be less favorable.
- The machine will not be slowed by the fact that every user has lots of files.
The disadvantages to this system include.
- The fact that the account storing the music will have to be logged in, and iTunes will have to be active in that account.
- If the account housing the music is not active then nobody can use the iTunes library.
- There is a certain degree of risk present when an administrator account must be continually active.
- Fast User Switching must be enabled.
Overview:
A central account controls all music on the machine/network, this is achieved by storing iTunes files in a public location as opposed to in the user's directory. In effect the system will give all users across the machine/network access to the same music/files without the possibility of files 'doubling up' because two different users like the same types of music. This approach saves valuable disk space in this regard and may therefore prove to be useful in some situations.
This is a hearty process to undertake, so only follow this tutorial if you're willing to go all the way to the end of it.
Process:
Step 1:
Firstly, we need to organize the host library, I tidied mine up, removing excess playlists, random files, things like that. this will make thing a bit easier in the later stages of this process.
Once the library is tidied up, move the entire "iTunes" folder from your Home directory to the "//localhost" directory (The Macintosh HD) and ensure that files are on the same level as the "Applications", "Users", "Library" and "System" directories; this will ensure that the files in the library are available to all users on the machine (this also works for networks)
Optionally you can set the ownership of the folder to the 'administrator' account (the user who will be hosting the library.), you may also like to set the permissions of 'you can' to "Read & Write" (assuming that you are doing this through the user who will host the library); secondly you should set the "Owner" to the administrator who will be hosting the library and set their "access" to "Read & Write" (this will ensure that the administrator has full access to the folder). The final part of this step involves setting access for the "Others" tab to "Read Only" this will ensure that the other users can view but not modify the contents on the folder.
Overview:
So far we have done the following steps:
1. Organized the host library.
2. Placed the iTunes directory into a 'public' directory so that other users may use it. (this step is essential if you plan on sharing the library across multiple accounts on the same machine. NOTE: this step is only necessary if you are wanting to share you library across multiple accounts on the same machine, if you simply want to share the music across a network, use the iTunes sharing facility.
3. set ownership and permissions for the iTunes music folder.
Step 2:
Currently the administrator is the only user who can use this library, however we will address this soon. In this step we will enable iTunes music sharing in the administrator's account, this will enable other users to access the files in the library.
If you are not logged in as the administrator, do so; secondly, open iTunes and select "Preferences" from the "iTunes" menu, now click the "Sharing" tab, if "share my library on my local network" is not checked, the radio buttons below this will now become active, you may choose to share the entire libraries contents, or share only selected content.
Sharing only selected content may be useful if their is explicit content in the library and minors use the network or machine that the library is connected to.
If you have selected "share entire library" go to Step 3, if you have selected share "share selected playlists" read on.
After clicking "share selected playlists" you must then select the playlists that you intend to share across your accounts and network. Once you have finished selecting the playlists, click "OK" to save the settings.
Overview:
In this step we:
1. Enabled iTunes sharing in the administrator's account, now, users on the local network may access the iTunes library, however, users on the same machine may not.
Step 3:
Now we will enable users on the same machine to access the library on the machine. This is achieved by logging in as each user, opening iTunes, opening iTunes preferences, and clicking "look for shared music". now all users on the machine may also access the library that the administrator controls.
This in effect will mean that the user will not need to use their user library, it will be provided to them via a pseudo network connection.
As a secondary measure, I have chosen to write a generic login script that will move any content from the user's "Music/iTunes/iTunes Music" directory to the trash and then empties the user's trash.
This is done through the use of an Automator Application: this application does the following actions.
1. Uses the "Finder" action "Get Specified Finder Items"
1a. The user's "~/Music/iTunes/iTunes Music" folder
2. Uses the "Finder" action "Get Folder Contents"
3. Uses the "Finder" action "Move to Trash"
4. Uses the "Automator" action "Run AppleScript"
4a. with the following:
on run {input, parameters}
tell application "Finder"
empty trash
end tell
return input
end run
IMPORTANT: Once the script is adapted to the user account it must be set as a login item. in order to keep the script out of the way i have placed it in the user's "Library" directory, in "Application Support" under "iTunes".
Overview:
Here we:
1. Enabled iTunes sharing in the user accounts on the host machine, in effect allowing all users of the machine to view a single iTunes library.
2. (Optional) I have created a login application that will remove any content that has been added to user iTunes libraries, this in effect stops other users of the machine from adding music and files to iTunes.
Step 4:
If it is not already enabled, open system preferences and enable Fast User Switching in Accounts Options.
Summary:
We have shared a single iTunes library across multiple user account, while still allowing for network sharing. This method is designed to save space on machines, particularly those with smaller hard drives.
I hope that this hint proves to be helpful and I hope everybody will give me feedback on my process.
regards,
Pete.
iBook G4; 60GB Hard Drive, 512MB RAM, Airport Extreme Mac OS X (10.4.6) iWork & iLife '06, Adobe CS2, Final Cut Pro. Anything and Everything!!!

how to share music between different accounts on a single computer

How can I display step info in User Interface with Tracing Disabled?

I'm trying to modify the CVI Operator Interface application to update the execute panel with some step information during the execution of the program. i.e. I want to display the measurement, high & low limits during the run WHEN TRACING IS DISABLED. (Doing this, when tracing is enabled is easy, all you do is access the step record that's been constructed (I can cope with that!))
I've successfully implemented a User defined execution event to signal the User Interface application when the current step is a result (using TS_UIMsg_UserMessageBase etc. I'm posting a UI Message in the Process Model under the ProcessModelPostStep so that I will only display if its a result step.) I've added a user defined
entry in the execute.c module execution event switch statement which will call a function in the exedisp.c module to update the display. However, I don't have a context to the step that I can use. (I can't use e.g. the exeRec record since this is only completed with the context if tracing is enabled.) I've got a handle to the correct panel to write the information to, but how do I get the context to the current step when tracing is disabled?
Regards,
Brian

Hi,
no problem - btw, if you wanted to acheive this in TS 1.x, you could always write to a local variable with the ActiveX reference for the step concerned, and then use the msg reference that you have in the OI within the UI Message handler, to dig through to the Execution ->Sequence File->Sequence->Locals, or Execution->Thread->SequenceContext (and you can get almost anywhere from that).
Hope that helps
S.
// it takes almost no time to rate an answer

Unable to load the user interface-please reinstall the application-Audigy 2 zs Platinum

unable to load the user interface-please reinstall the application---this is the message I get when my pc starts------Someone messing around with my computer tried to delete creative media source player 3 when they saw I had both 3 and 5 in folder and i get this error message every time I start my pc. In addition to this I have lost my EAX and THX consoles and my speaker settings are gone so I cannot adjust my 5. system at all. After I delete that error message when I click on the creative icon is sys tray instead of opening up the creative media player I get the error message--unable to load needed componants. Please reinstall the application. this is media player 3[version 3.32.]. I dont know why during the auto?updates through the last couple of years I have media player 3 in sys tray and if I need version 5 it is in file with 3--start-all programs-creative--any way my pc is a Cyberpower AMD FX-53 using win xp pro-32 bit-- and of course its a OEM product so they tell me the only way to get it to work is use the restoration cd they gave me when I bought the pc and it will revert back to its original state as when purchased. I would lose all my games, music, pictures?ect and would have to start from scratch.[ OR of course back everything up on a portable hard dri've]?It seems like there should be an easier way --hell I might as well buy a new soundcard and it would make it easier. If anyone?has an answer for someone who is not a tech head so I can understand please help !!--thank you in advance for any assistance as it is greatly appreciated. Sorry this message is so long winded, just irritating to have spen so much for a pc and not have the original installation disc.-tried moving to another slot and the fixes I saw posted here with no luck---thank you folks again--Tom

All the issues you guys are talking about have been reported in beta stage of these new drivers. I would say none of them has been fixed yet. The only solution for now is to use previous drivers which work fine or use some modified drivers which fixes some issues, but not all. Your choice.
[url="http://connect.creativelabs.com/windows/Lists/Audigy%20Issues/AllItems.aspx">Bug List[/url]
Message Edited by ronon0 on 08-07-2008 :47 AM

User settings to access network when logged on as service/batch

Hi.
We have been running Oracle Remote Agent (running external jobs on other host) on some linux-distros and have now started to do it on Windows as well.
But when we have setup everything properly, we get an 'Access denied' when trying to access the network from the Remote Host.
The way it works, in the database, you set up a credential with a user name and password. This information is then sent to the ETL (Remote Agent) which then starts the process as the user supplied in credentials.
So the service it self is running as Local Service and then starts a process as another user. Technically, how this is done on Windows I don't know...
Anyhow, the process starts fine and if we are not trying to access the network, it works fine.
But as soon as we are trying to access a network share using UNC path (\\192.168.1.10\share\directory), we get an 'Acces is denied'
The user we are using is an administrator. When doing a desktop login, this user can access the share without any problem.
Is there any other settings/policy/property the user must have to be able to access the network when logged on but not from the desktop?
Cheers
Richard

Have you checked the security logs on 192.168.1.10?
You should see the entries showing what account is attempting to log on through a network connect. You may need to grant the User Right for "Allow Access from Network" and you may be having basic folder permission errors.
I'm curious if the process is using the machine account to hit the share or if it's the user account you're starting the process with.
Chris Ream

Different user status profile for network header and activities

Hi everyone!
Is there any way to define different user status profile at network header level and at network activity level? As far as I know, it is only possible to enter a user profile at network type level, and both netwok headers and activities use the same statuses. Does it work this way?
Thanks!
Regards.
Edited by: Thalos on Jul 2, 2011 12:27 AM

Hi Punith, Hi abdul!
Thanks for the reply!
I've gone through the OPSC, but the thing is that here you define a user status profile at network plant level. But I need to define it at network activity level.
The reason why I need this is because we have types of activities. We use network activities for client activities, for internal activities, to identify and follow-up risk management, etc. Each group of activities -since they have different usages- has different user status associated. But as I don't have any way to assign different user status profiles, all the activities have the same statuses, although they will only use some of them.
Thanks!
Regards,
Thalos.

Need to send a email alert in PI 7.1 to user outside the intranet network

Hi,
How can I forward an alert from my alert inbox to a thirdparty user through email? Thirdparty user belongs to different network.

Hi Arindam,
One of the solution to your problem is as mentioned below.
1) Use RFC lookup in your mapping. Tell ABAP person to create a RFC for mail triggering. Or you can use standard RFC from ABAP for mail sending.
2) Once the value(Mail ID) will come in Message mapping, call the RFC lookup which will intern call the Mail sending RFC.
3) This way mail will be triggered from XI and will be sent from the ABAP system where the RFC is located. Just check whether in ABAP SMTP is there so you can send mail to external ID.

User interface for updating/adding attributes in OID

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

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

User interface through a network

Similar Messages

Maybe you are looking for