release note 2 4 -- 2010-10-14 · – release features – how to find the release level – how to...

© 2010 Online Development Inc 56eATM tManager Release Note www.oldi.com

Release Note 2.4

56eATM‐tManager Catalog Number 56eATM-tManager-xxxx Introduction Read this document before using the tManager Release 2.4 This release note contains important information about:

– software compatibility – release features – how to find the release level – how to download software

Software Compatibility with your GUI Always make sure that you update your tManager GUI when you update your tManager module. Software Compatibility with your past backups This release will import any 2.x module backup or exports.

NOTE: tManager Release 2.4 (RELEASENOTE 2.4 BUNDLE 2.4.18 .OLDI) can be used to update any of versions 2.3.1 through 2.4.17 When performing this update, you must follow the order defined in this document.

Download the Software You can download a free copy of release 2.4 from our knowledgebase (on our web site http://www.oldi.com ) For tManager Support, contact OLDI by submitting a service request on our website http://www.oldi.com or email via [email protected] .

Find the release level The release information is displayed in 2 locations in the xATM_MANAGER.


Changes in Release 2.4 (from 2.3)

• CLX L7X: Adds support of the new CLX L7x controllers

• JMS : Replaced support for JBoss RedHat EAP 4.3.0.GA CP04 with support of JBoss RedHat EAP 4.3.0.GA CP08.

• MAP : o STOREDPROCEDURE/FUNCTIONS ENHANCEMENT : Added support of

RECORD SET / RESULT SET when using the ORACLE and MSSQL database adapters

o ORACLEPACKAGEDSTOREDPROCEDURES : Added support for

ORACLE packaged stored procedures and functions.

o MAPDEBUG: Added to allow you to view the value of the last transaction when it fires. It will display the values of the inputs1.

1 Including OUTPUTS from functoids


o FUNCTOID: Added this functionality on the MAP configuration screen. This feature supports conversion of format, string manipulation, and math functions. For the full list, see the QUICKSTARTGUIDE of the function call FUNCTOID.

• ViewSQL : Added to provide window into the syntax of the transaction that

will occur when the trigger fires.

In this example: When the trigger fires, your transaction log for message would the complete message sent to the database :

Command=INSERT INTO [dbo].[TABLE03] ([COLUMN01],[COLUMN02],[COLUMN03],[COLUMN04]) VALUES (@COLUMN01,@COLUMN02,@COLUMN03,@COLUMN04), COLUMN01=3/4/2010 4:06:12 PM COLUMN02=22 COLUMN03=22 COLUMN04=34567


• TIME-SYNC : The time sync functionality was redesigned to be more robust

and support more logging. If time sync is enabled, a time synch cycle occurs

o after a time synch configuration change o after an appliance mode change o during appliance boot o at the specified frequency after configuration/mode-change-boot.

During a time synch cycle:

o The time of the appliance is set from the first active synch source found. o All of the time synch destinations are set from the appliance time. o Logging -- Failed and successful synch sources and destinations are logged.

• GUI changes for clarity:

o Separated database tables and views from the other schemas type in a navigation section titled TABLES/VIEWS

o Database StoredProcedures are now available in the navigation in a section titled PROCEDURES/FUNCTIONS (was labeled PROTOTYPES)

o Changed the reference on TIME MANAGEMENT screen for the TIME SOURCE OPTIONS to COMPUTER NETWORK and AUTOMATION DEVICE (was ENTERPRISE AND DEVICE)

o PROJECTEDITOR TRIGGER “Message Instruction” text added to the Event trigger

screen for clarity

Removed edge condition options (EEQ, ENEQ, ELT,ELTE, EGT, EGTE) from the SCHEDULED and MESSAGE INSTRUCTION condition options since they would not be appropriate.

Changed the default condition time for Periodic to ON CHANGE

o PROJECTEDITOR TAG VIEW : Changed name to TAGSTATUS to TAGSVIEW for clarity. This screen is available in the Status menu. It is supplied as a trouble-shooting aide. It allows reading/writing of up to 10 tags on your defined controllers (i.e. without the need for RSLogix5000 to update your CLX values when testing your triggers for example).


• LOG ENHANCEMENTS: Added trouble-shooting aides

o TRANSACTIONLOG: Added identification of the TRIGGER and the MESSAGE PATH that caused this message to be transmitted. The view of the log:

The data exported from the log:

2010-06-17 13:38:25,660 [\Demo\Automation\Trigger_1] [\Demo\Path_1] Command=INSERT INTO [dbo].[TABLE03] ([COLUMN01],[COLUMN02],[COLUMN03],[COLUMN04]) VALUES (@COLUMN01,@COLUMN02,@COLUMN03,@COLUMN04), COLUMN01=6/17/2010 1:38:25 PM COLUMN02=9888 COLUMN03=12 COLUMN04=34567

o TRIGGERLOG: Added identification of the tag read and its value in the expected format. The view of the log:

The data exported from the log:

2010-07-12 17:27:51,754 LogixCPU_1\TONR_02.ACC=0 LogixCPU_1\Timer1.ACC=0 Variable: 00 00 Reference: 00 00 00 00 Tag Data: 00 00 00 00 00 00 00 00

o SYSTEM LOG’S DEBUG MODE: Do not select SYSTEM log detail level of DEBUG unless instructed by OLDI tech support! In this case, it would be used to gathering additional log information for level 2 trouble-shooting. Warning: You would not wish to leave this logging level at DEBUG MODE any longer than necessary due to the performance hit on the appliance.


• NETWORKING: Added communication trouble-shooting aides

o NETWORKDIAGNOSTICS: Added IPConfig tab for this option. For iDB2 adapters (i.e. AS400, iSeries, System i), added support of CWBPing which is a verbose ping supported only by IBM systems.

o NETWORKSNOOPERS: This feature is a device communication trouble-shooting aide. It is for use with OLDI TECH SUPPORT. For example, if we need to trouble-shoot connect with your database commands, we would use this to gather the communication details. Today, MSSQL and ORACLE are supported.

• AUTOMATIC SMTP MESSAGEs: Enhancement to the subject for

STOREANDFORWARD NOTIFICATION and SYSTEMLOG NOTIFICATION emails, we add the module name in the subject line. In this example, if the module name is PANELONE and the subject defined for the StoreAndForward Notification is the text “S&F notification”, the subject of your smtp email received when the status of Store and forward has changed would be:

Subject: PANELONE - S&F notification

• DOCUMENTATION ENHANCEMENT: CROSS REFERENCE adds the USAGE column. For map, this column links the source to the destination. example: Tag Used In Type Usage

LogixCPU_1\ count100 \proj1\Map_1 Map

Linked from \proj1\Plant10_MSSQL\AUTO\OILTYPE

LogixCPU_1\ BLK1_CO1

\EMAIL_NOTIFICATION_Demo\Automation\Trigger_1

Trigger

Condition variable


• TCP/UDP : Added Bi-directional message paths in support of TCP and UDP communications that require linkage between the sending and the receiving information on the same port. The data formats of XML data, ASCII data, or binary data are supported from a source to a UDP or TCP destination. The UDP/TCP destination will send back a response to the data which is mapped into data in the Inbound Endpoint. Example of its use:

1. Controller tag trigger fires a request via TCP command (defined in the MAP to a device ENDPOINT).

2. This TCP device then responds with the information requested. 3. This requested data would be placed into the controller tags defined in

the INBOUND MAP using the INBOUND ENDPOINT.

• PC DIRECTORY LOCATION FOR EXAMPLES AND ACCESS PROXY: These files are installed in this location by the tManager GUI installation process. In preparation for support of WindowsStd the schema examples and proxy files had to change to a location under the MY DOCUMENTS \MY EATM MANAGER FILES directory. For example, on my machine the location for the examples is C:\DOCUMENTS AND SETTINGS\MYNAME\MY DOCUMENTS\MY EATM TMANAGER FILES\EXAMPLES

• Access and Excel Proxy: The proxy has been updated in 2.4 so install your new proxy on the Access/Excel server for use with your 2.4 tManager module. The proxy modification adds additional robustness on the connection into the Microsoft application.

• Trigger: Removed selection of the trigger conditions that were ‘edge-

triggered’ for the trigger types of Scheduled and CLX MSG Instruction. Decision for this modification was based on customer feedback.

© 2010 Online Development Inc 56eATM tManager Installation Process Page 1 www.oldi.com

Installation Process Release 2.4

56eATM‐tManager

Prep Step 1 Connect to the eATM using the XATM MANAGER.

Prep Step 2 Confirm the release level of the module that you are running as well as the revision of the GUI that you are running. You will be using this information as you proceed through this update path.

eATM Module Release under Administration | General

xATM MANAGER Release under Help | About

NOTE: If you are currently running a revision prior to 2.x, contact OLDI support for help updating your module.

Prep Step 3 Backup your module. We recommend maintaining both a COMPLETE APPLIANCE backup and a TRANSACTION CONFIGURATION backup. These backups are created using the XATM MANAGER as shown.


Prep Step 4 To simplify this process if multiple updates are required, more than one ZIP file will be attached to the knowledgebase solution. Download the file that applies to your original revision level. If you have any questions, contact OLDI support.

Prep Step 5 During the UPDATE process your eATM will have all of its STOREANDFORWARD(S&F) queue flushed (i.e. messages deleted) and eATM will be placed into the HALTED state. Therefore, you will need to make sure that your messages are not waiting for transmission S&F and that your module may be stopped during this time period.

Update Step 1 If you must be on 2.3.1 or greater to perform this update up to 2.4.18.

Using ADMININSTRATION | UPDATE | UPDATE APPLIANCE

You will be prompted to create a backup prior to the UPDATE.

We recommend that you always create a BACKUP with each UPDATE.


After the BACKUP, you will be prompted to select the UPDATE file (RELEASENOTE 2.4 BUNDLE 2.4.18 .OLDI)

When you select YES, the update process will begin. The eATM will reboot and install process will require approximately 10 minutes.

Do not interrupt this process for at least 10 minutes!

Note ‘Error Message’:

If you select the wrong update bundle file, you will receive this error at this time.

If you receive this message, double check your file selection and select the correct bundle file.


Update Step 2

When the install has begun, you can install any GUI update that is required during your wait for the install.

Note: Like Rockwell Software compatibility, the eATM GUI programs can communicate with any revision of the eATM appliance this is identical in the 2 most significant positions.

For example: GUI 2.3 can communicate ONLY to any 2.3.x revision eATM appliance.

If you wish to remove the current GUI programs prior to installing the update: You will need to remove the old revision. This is done by using WINDOWS | CONTROLPANEL | ADD\REMOVE PROGRAMS

Now, after you have removed the older revision, you can proceed with the install of the new GUI. This install is done by running the SETUP.EXE from the CD IMAGE \ INSTALL directory. When the install process has completed, start the program XATM MANAGER.

Update Step 3

Once the update is complete, the module will be scrolling on its alphanumeric display its module name, revision level, and its IP addresses.

release note 2 4 -- 2010-10-14 · – release features – how to find the release level – how to...

Documents