2014 Software Global Client Conference

Transcription

1

2 WW TSS 12 Maintaining Galaxy Integrity for Optimum Performance Jerry Lau Sr. Principal Technical Support Engineer

3 Overview Integrity of the Galaxy Database Before a Galaxy Migration - Galaxy Scrubber ArchestrA Graphics Compaction ManagedApp Compaction Platform Communication Issues Galaxy related corruptions ManagedApp Communication Issues

4 Why are we doing this? Ampla Citect OASyS DNA

5 Is something wrong or missing?

6 Is something wrong or missing?

7 Galaxy Database Integrity Checking the integrity of the Galaxy Database Ampla Citect OASyS DNA

8 Galaxy Database Integrity Problems caused by Galaxy database integrity Stored Procedure Where can you find it? Integrity tests in System Platform 2012 / 2012 R2 / 2014 How to interpret the results? How to fix the reported problems? Demo

9 Problems caused by database integrity Red-X ArchestrA Graphics Corrupted ManagedApp Version mismatch of objects Objects with missing references Objects imported into the Galaxy from a wrong version (patch issue) ArchestrA Graphics having corrupted references

10 dbo.internal_validate_integrity

11 System Platform means test passed 0 means test failed 22 different tests Object with blank tag names Unreferenced packages Orphaned checked_in or checked_out package ids Orphaned deployed_package_id Version numbers of object are increasing

12 System Platform 2012 All instances have checked-in packages Template references are correct Checked-in and Check-out bound VERs do not have NULL entries Visual element reference view does not have any null reference strings Objects are not missing any inherited visual element references from their parent Checked out visual element versions have corresponding checked out packages All object instances have a corresponding row in time stamp table Previous checked in clean up is finished

13 System Platform 2012 Other previous checked in cleanup is finished - no unnecessary packages to be deleted Integrity of visual element reference unbound should have some data Query visual_element_reference table to see if visual_element_reference_index is in sequence, starting from 1 Integrity of visual_element_version table compared to parent tables Check package table to see if there are any duplicate entries Check visual_element_reference to see that there are no duplicates in checked_out_bound_ Columns.

14 System Platform 2012

15 System Platform 2012 R2 / different tests First 22 tests are similar to those tests in WSP 2012 Some additional tests in WSP 2012 R2 System Platform 2014 has the same number of tests as WSP 2014 R2

16 System Platform 2012 R2 / 2014 Additional 6 tests: deployment_pending_status of gobject table validation file_version of file_table validation file_modified_time of file_table validation file_version of deployed_file validation file_modified_time of deployed_file validation gobject_id of intouchviewapptemplate_allsymbols validation

17 System Platform 2012 R2 / 2014

18 How to interpret the results? Depending on what is being reported, in the test results, review each section accordingly. If the reported problem is related to ManagedApp, follow the steps in the next section for the ManagedApp. Not all failed tests equate to a corrupted database Pervious checked in cleanup is finished

19 How to interpret the results?

20 How to fix the reported problems? ManagedApp Delete all derived instances Export the ManagedApp Template Delete the ManagedApp Template Import ManagedApp Template Objects / ArchestrA Graphics Depending on what is reported Open the object or template and check / correct the reported references Close and save the object / template and run the Integrity test again

21 What s next? CR L (Investigation CR) CR L (Investigation CR) Further ongoing research into this topic

22

23 Galaxy Database Migration Ampla Citect OASyS DNA

24 Galaxy Migration For a successful migration: Make sure the Galaxy DB is in a clean state before migration Enough hard disk space where the DB resides Use the Galaxy Scrubber to: Deletes all unused packages Decreases database unused space Decreases the transaction log file size Updates the indexes in some tables The migration process updates the Galaxy DB to the new version. If the DB is in a clean state, it can then be upgraded easily.

25 Galaxy Scrubber Download from WDN under

26 Galaxy Database Size

27 Galaxy Database Size Database Log 1746 MB 3399 MB

28 Galaxy Database Size

29 Galaxy Database Size Database Log 1009 MB 1 MB

30 Galaxy Backup Size Before 2.13 GB After 1.32 GB

31 A² Graphics Compaction Ampla Citect OASyS DNA

32 ArchestrA Graphics Compaction The number and size of the ArchestrA Graphics affect the total size of the ManagedApp The more the ArchestrA Graphics, the bigger the deployed Managed App The bigger the ArchestrA Graphics, the larger the deployed Managed App Most ArchestrA Graphics are vector-based If you do not need to insert a raster-based graphics (BMP / PNG / JPG), don t.

33 ArchestrA Graphics Compaction Use.EMF if possible. EMF is vector-based.

34 ArchestrA Graphics Compaction

35 ArchestrA Graphics Compaction

36 ManagedApp Compaction Ampla Citect OASyS DNA

37 ManagedApp Compaction Do not copy or create unnecessary files in the ManagedApp folder

38 ManagedApp Compaction Files in the CheckIn / CheckOut folder will be copied upon deployment If network bandwidth is low, do make sure you keep the ManagedApp small Even if the network bandwidth is high, deploying a large ManagedApp will affect the performance of the GR If there are multiple developers working in the same GR, this degradation of performance will definitely be seen and felt

39 ManagedApp Compaction - IMPORTANT files while the ManagedApp is being edited

40 ManagedApp Compaction As in doing a backup of a standalone InTouch application, the removal of unnecessary files will help to keep the ManagedApp small Delete files: del *.wvw del *.?bk Create a cleanup.bat with the above commands

41 Platform Communication How to resolve Platform communication issue Ampla Citect OASyS DNA

42 Platform Communication Issues Platform communication issues occur if the following is experienced: Physical network breaks DNS not working correctly Renaming a computer when a platform is already deployed Changing a fixed IP address when a platform is already deployed Bootstrap is in a non working state Causes are not only limited to the above points

43 Galaxy Related Corruptions Ampla Citect OASyS DNA

44 Galaxy Related Corruptions Importing a aapkg from another system where the Service Pack or Patch level is different Multiple CheckIn and CheckOut of objects with multiple developers which causes the GR to hang up Tech Alert 115 No more than 5 developers (depending on the workflow) working on the same GR If there are high write-operations (e.g. check in of very large ManagedApp or templates with numerous derived instances), reduce the number of developers. Adjust number of developers against the amount of operations

45 Galaxy Related Corruptions Do not shutdown the GR while a checkin process is in progress * If there are multiple developers working on the GR, check the CPU / Memory usage before checking in a large object

46 ManagedApp Communication Ampla Citect OASyS DNA

47 ManagedApp Communication Issue Depending on what is not updating correctly in the ManagedApp, check the following: ObjAttr Check that the Platform is communicating with the Galaxy IOAttr Check that the DIObject is communicating correctly Memory Tags from another node Check that InTouch WindowViewer is running on the other node and that node is reachable

48 2014 Schneider Electric. All Rights Reserved. All trademarks are owned by Schneider Electric Industries SAS or its affiliated companies or their respective owners. Ampla Citect OASyS DNA 48