1 / 18

Advanced Knowledge Localization

Key Takeaways . Understand Advanced Knowledge best practicesUnderstand the Globalization Best practices Understand how to create Language packs. Knowledge Best Practice. Management pack IDs should use the following structure:Microsoft.ProductName.ProductVersionMicrosoft.ProductName.ProductVer

temira
Download Presentation

Advanced Knowledge Localization

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

    1. Advanced Knowledge Localization Module 2 – Lesson 5 Roger Vaughn System Center Internationalization PM

    2. Key Takeaways Understand Advanced Knowledge best practices Understand the Globalization Best practices Understand how to create Language packs . An issue with storing product knowledge within the application’s management pack is that the entire management pack must be reinstalled to provide any knowledge updates. . An issue with storing product knowledge within the application’s management pack is that the entire management pack must be reinstalled to provide any knowledge updates.

    3. Knowledge Best Practice Management pack IDs should use the following structure: Microsoft.ProductName.ProductVersion Microsoft.ProductName.ProductVersion.Discovery Microsoft.ProductName.ProductVersion.Library Microsoft.ProductName.ProductVersion.Monitoring MP display name should use the portion of the ID after “Microsoft.” and add spaces for readability. For example: Microsoft.SQLServer.2005.Monitoring (ID) SQL Server 2005 Monitoring (display name) Localizers will not translate items that connected with underscores or dots.Localizers will not translate items that connected with underscores or dots.

    4. Knowledge Best Practice Display Strings and Knowledge should be contained to the Language Pack section This approach will make Separating, Localizing, and Updating knowledge much easier. While a single management pack can hold any number of language pack sections, multiple languages can very quickly increase the size of the management pack significantly

    5. Separating Knowledge One strategy to the size issue is to provide live links in the product knowledge. This will hinder any console user that does not have external access to the internet. Another solution is to separate the knowledge into separate management pack (called language packs) Allows authors to update without changing the core management pack Allows the authors to perform different translations independent of core management pack A solution to both the issue of management pack size and updates is to separate knowledge into is own management pack. Updates to this management pack could be performed frequently since it would only include static text giving the user a low risk with no testing prior to installation. With each language in its own file, a customer would only load those languages they require.A solution to both the issue of management pack size and updates is to separate knowledge into is own management pack. Updates to this management pack could be performed frequently since it would only include static text giving the user a low risk with no testing prior to installation. With each language in its own file, a customer would only load those languages they require.

    6. Updating Knowledge Remember, in the past, that entire management pack had to get updated even for updating knowledge. Product knowledge may change often for: Newly found bugs Updates and hotfixes But with Language Packs this can: Update MPs independent of core management pack Ship updates often with little risk. An issue with storing product knowledge within the application’s management pack is that the entire management pack must be reinstalled to provide any knowledge updates. Product knowledge will typically change more frequently than the management pack elements such as discoveries and monitors, and it would be useful to provide the customer with updated knowledge as it comes available. The problem is that an updated management pack needs to be tested. Even though only knowledge has changed, the management pack still contains active monitoring and must be tested in most environments prior to production installation. Frequent updates to a management pack to provide updated knowledge results in a significant effort to the customer in terms of testing requirements.An issue with storing product knowledge within the application’s management pack is that the entire management pack must be reinstalled to provide any knowledge updates. Product knowledge will typically change more frequently than the management pack elements such as discoveries and monitors, and it would be useful to provide the customer with updated knowledge as it comes available. The problem is that an updated management pack needs to be tested. Even though only knowledge has changed, the management pack still contains active monitoring and must be tested in most environments prior to production installation. Frequent updates to a management pack to provide updated knowledge results in a significant effort to the customer in terms of testing requirements.

    7. Globalization Best practices Make sure that your scripts do not have display text to them. Scripts need to be language aware Outputs need to handle code page of the OS is it run on. All text included in the Operations Console including display strings and product knowledge are stored in a DisplayStrings section of the management pack specific to the language. To localize a management pack, we need to provide a translation for the English text and then include it in a section specific to the language. There is no change at all required for the individual management pack elements. All text included in the Operations Console including display strings and product knowledge are stored in a DisplayStrings section of the management pack specific to the language. To localize a management pack, we need to provide a translation for the English text and then include it in a section specific to the language. There is no change at all required for the individual management pack elements.

    8. MP Language Pack Creation Extracts all knowledge and display strings from MP Creates separate the language packs for each language Allows the user to load only language(s) required. An issue with storing product knowledge within the application’s management pack is that the entire management pack must be reinstalled to provide any knowledge updatesAn issue with storing product knowledge within the application’s management pack is that the entire management pack must be reinstalled to provide any knowledge updates

    9. MPLangPackTool Usage Functions: -exp – Used to export language packs the first time. -sync – Used to synchronize language packs with existing language packs. Options all - To perform function on more than one file (use path instead of filename, without \ at the end). s - To include subdirectories (only use with 'all'). Default – will create language pack for all the languages that Ops Mgr is localized. Example: MPLangPackTool -exp all "c:\MyMPs“ Default MPLangPackTool -sync all s "c:\MyMPs" All text included in the Operations Console including display strings and product knowledge are stored in a DisplayStrings section of the management pack specific to the language. To localize a management pack, we need to provide a translation for the English text and then include it in a section specific to the language. There is no change at all required for the individual management pack elements. All text included in the Operations Console including display strings and product knowledge are stored in a DisplayStrings section of the management pack specific to the language. To localize a management pack, we need to provide a translation for the English text and then include it in a section specific to the language. There is no change at all required for the individual management pack elements.

    10. Language Pack Tool Demo Open Command Window. CD to the Directory where the tool is. Show the MP with the text Run the tool (talk about the command line) Show the new SatMps. Update Core MP with new text. Run the –sync option of the tool (talk about the parameters) Show the updated SatMps. Open Command Window. CD to the Directory where the tool is. Show the MP with the text Run the tool (talk about the command line) Show the new SatMps. Update Core MP with new text. Run the –sync option of the tool (talk about the parameters) Show the updated SatMps.

    11. Adding screenshots for demo after this. Slide.

    12. Adding screenshots for demo after this. Slide.

    13. Adding screenshots for demo after this. Slide.

    14. Adding screenshots for demo after this. Slide.

    15. Adding screenshots for demo after this. Slide.

    16. Adding screenshots for demo after this. Slide.

    17. Adding screenshots for demo after this. Slide.

    18. Wrap Up Remember to not hardcode anything Scripts should not have text embedded The tool is available out on the MP best practices website. . An issue with storing product knowledge within the application’s management pack is that the entire management pack must be reinstalled to provide any knowledge updates. . An issue with storing product knowledge within the application’s management pack is that the entire management pack must be reinstalled to provide any knowledge updates.

More Related