SBOPRepositoryExplorer v2.0.2 Released

Dear all,

It was detected in some versions of SAP BO BI 4.1 SPx for WRC and SAP BO BI WebI Server Side, doesn’t works in DDK the function to read CONFIGURATION parameters from SAP BO .COD files used in connection definition. In this release you can use one of next three options until SAP provide the patch for ConnectionServer.jar:

Option a) Missing parameters from environment variables:

For logs and debugging:

  • SBOPREPEXP_TRACELOG_HERETHECMSNAME=YES_TRACE or NO_TRACE
  • SBOPREPEXP_TRACEFILE_HERETHECMSNAME=path_to_file for example C:\SBOPREpositoryExplorer.log
  • SBOPREPEXP_LOGLEVEL_HERETHECMSNAME=Debug or Error

 To import XML Files:

  • SBOPREPEXP_XMLFILE_HERETHECMSNAME=path_to_xml_file for example C:\Samples\Samples.xml

To import EXCEL Files:

  • SBOPREPEXP_EXCELFILE_HERETHECMSNAME=path_to_excel_file for example C:\Samples\Samples.xlsx

To set Query Limits:

  • SBOPREPEXP_MAXQUERYOBJECTS_HERETHECMSNAME=Query_limit

Option b) Create a file called config.properties in same folder where SBOPRepositoryDriver.jar with next parameters:

MAX_OBJECTS_QUERY=Query_limit
TRACELOG=Yes_Trace or No_Trace
TRACE_FILE=Path_to_file_for_logs_in_JAVA_Format (use / for path)
LOGLEVEL=Debug or Error
XML_FILE=path_to_xml_file (use / for path)
EXCEL_FILE=path_to_excel_file (use / for path)

Option c) Use environment variable with path of config.properties file:

SBOPREPEXP_CONFIG_FILE=path_to_config_properties_file(must_include_file_name)

 

See you soon! Enjoy!

Jorge Sousa


Leave a Reply

Subscribe

  • Facebook
  • Twitter
  • Google+
  • RSS Feed
  • YouTube