Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Issue description

After exporting from IWS to MessageCenter, the stream isn't created (you can not see it in the Message Center Console or Message Center editor).

Issue Resolution

There are several potential reasons for this issue:

1. The unzip application did not work correctly – refer to the Custom Application files issue.

2. Import related streams do not exist. Please check that the following streams exist:

    • mc_import_stream_request
    • mc_import_stream_w
    • eagle_mc_import_stream_request
    • eagle_mc_import_stream_w

3. Check the import_streams noted above in Message Center for errors. If you see an error including JVM, it is most likely due to the settings of JVM or an error with it.

To check, open a cmd window and tpe 'java-version' and enter. If information about the Java verison appears, then this is a good sign that Java is working. Otherwise, check the windows 'PATH' variable for including the path to JVM or refer to the JVM or Export Jar section below.

...

Issue description

JVM or export jar file does not work correctly.

Issue Resolution

To check this, bring up IWS on the environment and under File, select Export to Local drive. If you get an error, reinstall JVM or refer to IWS does not create all of the necessary files or folders.

Issue: Process Stuck with Multiple Execution Attempts

Issue description

Process is stuck and shows a lot of execution attempts

Issue resolution

In this case we suggest checking estar/tpe/cfg/msgcenter/msgservice.ini config file first of all.

SplitBatchSize parameter defines the number of records loaded to memory for processing and should not be a large number, recommended value is 2. It is responsible for memory consumption and values like 100 may harm processing.