...

• Unicode support works across any supported JS7 - Platforms.
• Limitations have to be considered in mixed environments that include Windows operating system that ship without Unicode support and use a two byte subset UTF-16 LE.

JOC Cockpit requires the JS7 - Database to support UTF-8 encoding in order to store objects that hold such characters.

• For UTF-8 a single character stored to a JS7 database table requires 1 to 4 bytes.
• For example, NVARCHAR(10) specifies a column width of 10 characters that can consume 40 bytes.

The JDBC Drivers in use have to support Unicode.

JOC Cockpit

When designing workflows with the Configuration -> Inventory view users can make use of any Unicode characters within the scope of JS7 - Object Naming Rules.

• Download workflow for Unix (upload .json) workflow for Unix: pduLanguage-日本語.workflow.jsonDownload
• Download workflow for Windows (upload .json) workflow for Windows: pdwLanguage-日本語.workflow.json

...

The Configuration -> Inventory view allows to specify object names and job scripts using Unicode characters:

...

names and job scripts using Unicode characters:

Workflows View

The Workflows view displays workflows using Unicode characters accordingly:

• The below example makes use of Japanese object names.
• In addition, the JOC Cockpit interface language is switched to Japanese by use of JS7 - Profiles - Preferences.
  
  

...

• Output from Unix Operating Systems
  • Unix Operating Systems ship with built-in support for Unicode and UTF-8 encoding.
• Output from Windows Operating Systems
  • Windows does not offer Unicode. Instead the OS ships with different code pages preinstalled depending on the location in which the OS is used.
  • Some experimental Unicode support is available starting from Windows 10, however, as most Windows programs are not aware of Unicode there can be side-effects.
  • Therefore the encoding of output created by jobs depends on the code page in use for the respective Windows OS for which an Agent is operated.

...

The Controller does not read or write files related to workflow execution of workflows and jobs. The Controller reads configuration files and writes component log files only.

• Configuration files use UTF-8 encoding.
• Log Component log files are created with UTF-8 encoding.

...

• For Unix environments the OS creates output in UTF-8 encoding.
• For Windows environments the OS does not support Unicode but makes use of a code pagespage to encode output.

Use with Windows Code Pages

...

• In Asia frequently code page 65001 is or specific code pages such as 932 for Japan are used.
• In Western Europe frequently code page 850 is used.

...

js7.job.execution.encoding = "UTF-8"

Explanation:

• This setting specifies the MIME type not the numeric code page identifier, for example UTF-8 instead of 65001.
• Users should be aware that modifying the Agent's code page will not modify the code page of the underlying OS shell.
• OS commands will continue to encode output with the OS code page.

...

• The first job is assigned an environment variable JOB_NAME from a built-in global variable like this:
  
  
  
  
• Line 3: The output of the JOB_NAME environment variable can be scrambled if the server does not use a compatible code page, see chapter Log View.
• Line 4: The job displays Unicode characters that have been directly added to the job script.
• Line 6, 7: The job creates two variables for use with later jobs:
  • var1: the variable directly holds Unicode characters.
  • last_job_name: the variable holds the name of the current job.
• Line 9: The job displays the current code page.

...