We are looking for a new Wonderware Technical Training Instructor for our Lake Forest office in California.
As a Wonderware Instructor you will train customers, our distribution channel, and Invensys employees on different Wonderware products; from Application Server and InTouch to advanced applications, such as MES and Workflow. In addition to teaching at our state-of-the-art facility in Lake Forest, you will travel around the United States and the world conducting on-site classes at different facilities.
As part of the training team, you will become a Subject Matter Expert for the design and development of the training courses in collaboration with the course development team.
You can find more information and apply for the job here and search for the keywords: instructor.
Wednesday, September 25, 2013
Monday, September 23, 2013
NEW! InTouch for System Platform 2012 R2 eLearning
We are expanding our eLearning library!
We have released a Recorded Instructor-Led Training (RILT) for our InTouch for System Platform 2012 R2 course.
The Application Server 2012 R2 training course will be available very soon. I know that it seems backwards to release the InTouch course first, but we are fixing some technical issues with the Application Server recordings. Stay tune as I will announce when the course is available.
These are the first in our new RILT format. These and future RILTs include:
Click here to register for this eLearning course.
We have released a Recorded Instructor-Led Training (RILT) for our InTouch for System Platform 2012 R2 course.
The Application Server 2012 R2 training course will be available very soon. I know that it seems backwards to release the InTouch course first, but we are fixing some technical issues with the Application Server recordings. Stay tune as I will announce when the course is available.
These are the first in our new RILT format. These and future RILTs include:
- Lectures and demos
- Execution of all the labs
- Downloadable training manual
Click here to register for this eLearning course.
Monday, September 16, 2013
Using System.AppDomain to share data between Automation Objects - Part 2
In Part 1 I introduced you to the System.AppDomain .NET class a way to share complex types between objects in Application Server (as long as the objects are hosted in the same AppEngine). As an example, I shared a database connection to the Historian Server database (Runtime) through the AppEngine object.
Now, let's take a look at the sample script needed in the other objects to access the shared database connection.
Now, let's take a look at the sample script needed in the other objects to access the shared database connection.
Monday, September 9, 2013
Using System.AppDomain to share data between Automation Objects - Part 1
This one is for advance Application Server users.
When writing complex .NET scripts within automation objects, you might find the need to share information between objects that is not of a standard ArchestrA data type. In other words: if your script is using a .NET type that is not compatible with the data types available for a UDA, how do you share that data between two or more objects in your Galaxy? If you read the title of this post you guessed right: using the .NET System.AppDomain class.
There is one caveat, though. You can only share the data between objects in the same AppEngine.
Note: The AppDomain class provides an isolated environment to execute applications. We are using it as a "trick" to share data within your application, but it's not its real purpose.
In this 2-part article, I will walk you through an example sharing a connection to a SQL Server database. In Part 1 I will show you how to create and make the connection available to the rest of the application. In Part 2 I will show you how to access the connection from a different object.
When writing complex .NET scripts within automation objects, you might find the need to share information between objects that is not of a standard ArchestrA data type. In other words: if your script is using a .NET type that is not compatible with the data types available for a UDA, how do you share that data between two or more objects in your Galaxy? If you read the title of this post you guessed right: using the .NET System.AppDomain class.
There is one caveat, though. You can only share the data between objects in the same AppEngine.
Note: The AppDomain class provides an isolated environment to execute applications. We are using it as a "trick" to share data within your application, but it's not its real purpose.
In this 2-part article, I will walk you through an example sharing a connection to a SQL Server database. In Part 1 I will show you how to create and make the connection available to the rest of the application. In Part 2 I will show you how to access the connection from a different object.
Monday, September 2, 2013
New and updated Quick Reference cards available
For those of you that were not aware, we have several Quick Reference cards available for download. All cards are for QuickScript .NET, ArchestrA scripting engine.
We just updated the previously available cards (five of them) and added two new ones around the ShowGraphic() script function. I hope you find them useful.
Are there any other products and features you might want to see as a Quick Reference cards? Please, let us know in the comments what you'll like to see.
You can download PDF versions of the cards here.
We just updated the previously available cards (five of them) and added two new ones around the ShowGraphic() script function. I hope you find them useful.
Are there any other products and features you might want to see as a Quick Reference cards? Please, let us know in the comments what you'll like to see.
You can download PDF versions of the cards here.
Subscribe to:
Posts (Atom)