Sybase Business Intelligence Solutions - Database Management, Data Warehousing Software, Mobile Enterprise Applications and Messaging
Sybase Brand Color Bar
delete

Search for    in all of Sybase.com
view all search results right arrow
  blank
 
 
 
 
 
Support > Technical Documents > Document Types > Release Bulletin > Release Bulletin e-Biz Impact 5.5

Release Bulletin e-Biz Impact 5.5

Documents known problems and changes to installation, functionality and documentation for e-Biz Impact Server and Client, v5.5, on HP-UX PA-RISC, IBM AIX, Sun Solaris SPARC, and Windows x86.
 
RSS Feed
 
 
 

Release Bulletin e-Biz Impact™ 5.5 for Windows, AIX, HP-UX, and Solaris

 

Document ID: DC70221-01-0550-02

Last revised: Novemeber 17, 2006



Accessing current release bulletin information

A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the release of the product CD, use the Sybase Technical Library Product Manuals Web site.

Accessing release bulletins at the Technical Library Product Manuals Web site
  1. Go to Product Manuals.

  2. Follow the links to the appropriate Sybase product.

  3. Select the Release Bulletins link.

  4. Select the Sybase product version from the Release Bulletins list.

  5. From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.



Product summary

e-Biz Impact 5.5 includes these components:

  • e-Biz Impact Server 5.5

  • e-Biz Impact Client 5.5

  • Documentation

See the e-Biz Impact Getting Started CD that comes with the product for additional information.

e-Biz Impact version 5.5 is compatible with the following platform and operating system configurations:

  • HP-UX PA-RISC

  • IBM AIX

  • Sun Solaris SPARC

  • Windows x86

See the e-Biz Impact Installation Guide for data server compatibilities and disk requirements.



ODBC driver changes

e-Biz Impact version 5.5 on UNIX platforms is shipped with the UNIX ODBC driver manager, rather than the previous DataDirect ODBC driver and driver manager.

WARNING! The UNIX ODBC driver manager serves as a place holder only. Sybase does not support the UNIX ODBC driver manager, and recommends that you use the DataDirect driver and driver manager.

If you are an existing customer, continue to use the DataDirect drivers used with e-Biz Impact 5.4 or earlier.

  1. Copy the odbc.ini file from your e-Biz Impact version 5.4 or earlier to the ImpactServer-5_5\udbc directory.

  2. Add the ODBC library directory to your library path environment variable.

If you are a new customer, Sybase recommends you purchase the ODBC driver and driver manager from DataDirect.

  1. To purchase the DataDirect ODBC drivers directly, go to the DataDirect Web site.

  2. Follow the instructions include with the drivers to set up and configure the DataDirect ODBC driver and driver manager.

  3. Copy the odbc.ini file into the ImpactServer-5_5\udbc directory.

  4. Add the ODBC library directory to your library path environment variable.



Special upgrade instructions

For migration instructions, see the e-Biz Impact Installation Guide, Chapter 4, “Upgrading e-Biz Impact” and the e-Biz Impact Configurator Guide guide.


Shared memory

If you are upgrading to e-Biz Impact version 5.5 from e-Biz Impact pre-5.4.5, e-Biz Impact version 5.4.5 introduced an operating system shared memory real time extension, which:

  • Eliminates the need to set up TCP ports for inter-controller communication.

  • Renders obsolete the distinction of local versus remote controllers.

  • Allows DFC server applications to be monitored.

Existing clusters created with e-Biz Impact version 5.4 or the version 5.4.2 EBF must be upgraded using the e-Biz Impact 5.5 Configurator.



Changed functionality in this version

This section contains information about changed functionality in e-Biz Impact 5.5.


Emanate SNMP

The Emanate SNMP service is no longer setup as a service by the installer. Use the new utility ims55svchost.exe.



Documentation updates and clarifications

This section contains updates, corrections, and additions to the e-Biz Impact core documentation.


Command Line Tools Guide


Automating controller shutdown

This example shuts down the cluster object CLUSTER1 to disable its child controller CONT1 using the configuration file myCncFile.cfg. See the e-Biz Command Line Tools Guide, Chapter 2, “Using Command and Control Requests,” for more information.

Syntax

ims cnc –file shutdown.cfg

Configuration file

myCncFile.cfg contains:

cluster 
     name=CLUSTER1
     server=HOST1
cnc
     user=JOHN
     password=PWD
     subject=CLUSTER1
     type=mgr
     command=shutdown
     object=CONT1
domain
     type=PROD1
     name=DOMAIN1

Monitoring e-Biz Impact

The following information is an update to the section “Understanding SNMP” in the Monitoring e-Biz Impact Guide, Chapter 1, “Overview.”


SNMP basics

The Simple Management Network Protocol (SNMP) requires two basic elements to function: an agent and a manager. A Management Information Base (MIB) is also required, which provides a small set of commands for the exchange of information between the agent and the manager, and lists the unique object identifier (OID) of each managed element in an SNMP network. To view SNMP trap groups and their object identifiers (OIDs), open the impact8info.dat file, which is location in x:\Sybase\ImpactServer-5_4\snmp on Windows and in ~/Sybase/ImpactServer-5-4/snmp on UNIX (where “x” and “~” represent where the e-Biz Impact server is installed).

WARNING! Do not edit this file. The codes are automatically generated by the MIB.


Incorrect alert IDs

The alert IDs listed in the Monitoring e-Biz Impact Guide, Appendix A, “Alert IDs,” are incorrect. SFM alerts are in the 70xxx range. Router alerts are in the 80xxx range.


MSG-IDE Guide


Creating database callback functions

Database callback functions manipulate data received from each result row of a SQL statement object. The function executes after each result row has gathered events and data in the new row.

The callback function traps events after the execution of a SQL query or stored procedure using the database interface object. You can place additional ODL logic within callbacks to execute against a query or stored procedure.To create a database callback function:

  1. In the MSG-IDE Browse window, select Function in the object list on the left, then click Add. The Edit Function window opens.

  2. Click DBcallback. The return type appears in the Returns field and the callback function argument appears in the Arguments field, supplied by the MSG-IDE tool:

    _cdecl char *_cop, short event, long row
    
    • _cdecl char *_cop – pointer to the associated database interface object that executes against the database.

    • short event – event code for triggering the callback function. Event codes are listed in table below.

    • long row – associated database row, if applicable.

  3. Enter the name for this database callback function; for example, dbi_callback1.

  4. In the text editor pane, enter the body of the callback function, which generally checks the event code (and/or current result set row), then takes appropriate actions based on those values. For example:


Associating a database callback function with a database interface object

To associate a callback function with an database interface object,

  1. Create the database interface object using the instructions in “Defining database interface objects” in the e-Biz Impact MSG-IDE Guide, Chapter 3, “Use MSG-IDE.”

  2. Referencing the instructions in the above-referenced section, subsection “SQL statement result options,” define a SQL statement result option.

  3. In the SQL Statement Result Options dialog box, click the down arrow in the Callback field and select an existing function to execute against each result row, or click the ellipsis button (three dots) to build a new function using the instructions in “Creating database callback functions”.


Undocumented DFC error codes

The following DFC error should be added to Table 2-2 “DFC errors”.

Error code

Description

4333

DFC connection error.

4341

The DFC server disabled.

4342

The DFC is in the process of being disabled.

4343

The DFC is in the process of being enabled.

4361

DFC ODL error.

4362

DFC ODL error.

4363

DFC ODL error.


ODL Guide

The following information is missing from the e-Biz Impact ODL Guide, Chapter 5, “General Objects and Methods”.


initialize()

Description

Opens connection.

Syntax

initialize();

Return value

Integer. Returns a positive integer if successful, and zero or negative integer, if failed.

Usage

Pointer to object

Object

pdbi->initialize();

my_dbi.initialize();


TRAN-IDE Guide


Transaction status

The following transaction statuses may display in the SFM log. This information supersedes the list of statuses that display in the e-Biz Impact TRAN-IDE Guide, in the sections of Chapter 1 entitled “SFM log overview” (Table 1-5), and “Transaction status.”

Status

Description

BOGUS

The transaction’s destination that no longer exist due to a configuration change between cluster startups.

CANCELLED

Operator has cancelled the transaction or the destination returned -999, cancel and continue.

COMPLETE

Transaction has been delivered to the destination endpoint

DELETED

Operator deleted the transaction using the Global Console.

FAILED_RESUBMIT

Operator resubmitted the transaction using the Global Console but it failed.

NOT_ARCHIVED

When auto-archiving is turned on, and the transaction failed to be archived. Similar to a completed transaction that is waited to be archived. Each time the SFM starts, it goes through the completed log to see if there are any such transactions that need to be archived.

PENDING

Transaction has not been delivered to the destination endpoint.

REPAIRED

Operator repaired the transaction using the Global Console, but the transaction has not yet been resubmitted.

RESEND

Operator has resubmitted the transaction using the Global Console.

SKIPPED

Operator has skipped the transaction

UNROUTABLE

Transaction could not be delivered to any destination.


isRegEx update

The following table replaces the table in Chapter 3, “Building Production Objects,” in the Examples section that describes using special characters for the isRegEx built-in qualification function:

Table 1: isRegEx special characters

Symbol

Description

[ ]

Brackets define a range of characters to match to a single character position. The example looks for any string that begins with the characters “abc” then has a “d”, “e”, or “f”, followed by a “g”.

Example – “gr[ae]y” matches “gray” and “grey”, but does not match “graay” or “graey”.

.

A period matches single character (except newline).

Example – “abc.g” matches “abcag”, “abcbg”, “abccg”, and so on.

*

An asterisk matches the preceding character 0 or more times.

Example – “a*” matches “aa”, “a”, “aaa” and so on.

^

A caret sign as the first character of a regular expression anchors the expression to the beginning of a line. Strings that start with the expression’s characters that follow the ^ fulfill the search criteria.

Example – “^ab” matches “abrefok” but not “erafxab”.

+

A plus sign following a regular expression repeats the expression one or more times.

Example – “[1-5]+” is equivalent to “[1-5][1-5]*”.

Specifies a range of characters.

  • If the minus sign is in an expression in brackets, it matches on a string of consecutive values.

    Example – “[a-e]” is equivalent to “[abcde]”.

  • If the minus sign is placed immediately after an opening bracket ([), it matches on a hyphen.

    Example – “[-[]” matches the characters “-” and “[“.

$

A dollar sign as the last character of a regular expression anchors the expression to the end of a line. Strings that end in the expression’s characters that precede the $ fulfill the search criteria.

Example – “ab$” matches “erafxab” but not “abrefok”.

?

Makes the preceding character optional.

Example – “abc?” matches “ab” or “abc”.

{m} {m,} {m,u}

Integers that specify the number of times to repeat the preceding regular expression. “m” is the minimum number and “u” is a number in the range of 0 – 255. The expression “{m}” by itself indicates the exact number of times the preceding regular expression should be repeated.

Example – “a{3}” matches “aaa”.

The expression “{m,}” specifies “{m,infinity}”.

( )

Round brackets group parts of a regular expression together. Round brackets can also create a “back reference”, which stores the part of the string matched by the part of the regular expression inside the parentheses.

Note:Only round brackets can be used for grouping. Square brackets define a character class, and curly braces are used by a special repetition operator.

Use parentheses to group other expressions. Operators like *, {}, and + can work on a regular expression enclosed in parentheses ( ) as well as on a single character.

You can also make several characters optional by grouping them together using round brackets, and placing the question mark after the closing bracket. For example, “Nov(ember)?” matches both “Nov” and “November”.

\

You can use any of the above characters as a literal value by preceding the character with a backslash. The backslash works on only one character at a time.

Example – “AB\.\*CD” matches to the literal “AB.*CD”.

Note:All other regular characters should not be preceded with a backslash because the backslash is also a special character. The backslash in combination with a literal character can create special meaning; for example, “\d” matches a single digit from 0 to 9.


HL7 repository

The e-Biz Impact version 5.4.5 client installation adds an HL7 data source name (DSN)—”hl7repo”—which allows you to connect to the HL7 repository database.

The e-Biz Impact TRAN-IDE Guide, Chapter 2, “Using TRAN-IDE,” contains a section entitled “Using the HL7 objects repository.” This section has a procedure that you use to create a new HL7 DSN. You can still use this procedure; however, because the e-Biz Impact client installation creates an HL7 DSN, you can now also edit the existing DSN and use that, rather than creating a new one.

Use this procedure to edit the HL7 DSN created by the e-Biz Impact client installation.

Configuring the HL7 repository connection
  1. On Windows, select Start | Settings | Control Panel.

  2. Select Administrative Tools.

  3. Select Data Sources (ODBC). The ODBC Data Source Administrator window appears.

  4. Select the System DSN tab.

  5. Select “hl7repo” and click Configure. The ODBC Configuration for Adaptive Server Anywhere 8 window appears.

  6. Modify the options on the ODBC tab as necessary:

    • Data Source Name – accept HL7repo or enter a different name. This tells the ODBC driver manager or Embedded SQL library where to look in the file or registry to find the ODBC data source information.

    • Description – enter an optional longer description of the data source to help you or end users to identify this data source from among their list of available data sources.

      Leave the remaining fields blank.

      Note:See the ASA Database Administration Guide for more information:

      1. Go to the Technical Library Product Manuals Web site at Product Manuals, select SQL Anywhere Studio from the product drop-down list, and click Go.

      2. When the Core Documentation list displays, select SQL Anywhere Studio 8.0, then choose the PDF or online version of the ASA Database Administration Guide.

  7. Select the Login tab, verify that Supply User ID and Password are selected, but the actual user ID and password fields are blank.

  8. Select the Database tab and modify these options as necessary:

    • Server Name – accept “hl7repo,” which is the name of the local machine or network server where the HL7 repository is located and the e-Biz Impact client is installed.

    • Start Line – accept the path to the HL7 repository database executable, modify the path, or leave the field blank.

      Note:This value automatically starts the HL7 repository database when you start your machine.

      To automatically start the HL7 repository database, you must also select the option “Automatically start the database if it isn’t running,” in addition to providing a Start Line value.

      To manually start the database, leave this field empty and unselect “Automatically start the database if it isn’t running.”

    • Database Name – enter hl7repo, which is the name of the HL7 database to which you want to connect. This entry is case sensitive.

      WARNING! Do not enter the “.db” extension for the database in this field. For example, do not enter hl7repo.db.

    • Database file – accept the full path and name of the file, or click Browse to locate the file and change the path. For example:

      x:\Sybase\ImpactClient-5_4\DevApplication\.bin\hl7repo.db
      

    where “x” represents the location where the e-Biz Impact client is installed.

  9. Accept the defaults for the remaining options.

  10. Click OK to save your entries and close the ODBC Configuration window.

  11. Click OK to exit the ODBC Data Source Administrator.



Technical support

Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.



Other sources of information

Use the Sybase Getting Started CD, the SyBooks CD, and the Sybase Product Manuals Web site to learn more about your product:

  • The Getting Started CD contains release bulletins and installation guides in PDF format, and may also contain other documents or updated information not included on the SyBooks CD. It is included with your software. To read or print documents on the Getting Started CD, you need Adobe Acrobat Reader, which you can download at no charge from the Adobe Web site using a link provided on the CD.

  • The SyBooks CD contains product manuals and is included with your software. The Eclipse-based SyBooks browser allows you to access the manuals in an easy-to-use, HTML-based format.

    Some documentation may be provided in PDF format, which you can access through the PDF directory on the SyBooks CD. To read or print the PDF files, you need Adobe Acrobat Reader.

    Refer to the SyBooks Installation Guide on the Getting Started CD, or the README.txt file on the SyBooks CD for instructions on installing and starting SyBooks.

  • The Sybase Product Manuals Web site is an online version of the SyBooks CD that you can access using a standard Web browser. In addition to product manuals, you will find links to EBFs/Maintenance, Technical Documents, Case Management, Solved Cases, newsgroups, and the Sybase Developer Network.

    To access the Sybase Product Manuals Web site, go to Product Manuals.


Sybase certifications on the Web

Technical documentation at the Sybase Web site is updated frequently.

Finding the latest information on product certifications
  1. Point your Web browser to Technical Documents.

  2. Select Products from the navigation bar on the left.

  3. Select a product name from the product list and click Go.

  4. Select the Certification Report filter, specify a time frame, and click Go.

  5. Click a Certification Report title to display the report.

Finding the latest information on component certifications
  1. Point your Web browser to Availability and Certification Reports.

  2. Either select the product family and product under Search by Product; or select the platform and product under Search by Platform.

  3. Select Search to display the availability and certification report for the selection.

Creating a personalized view of the Sybase Web site (including support pages)

Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.

  1. Point your Web browser to Technical Documents.

  2. Click MySybase and create a MySybase profile.


Sybase EBFs and software maintenance

Finding the latest information on EBFs and software maintenance
  1. Point your Web browser to the Sybase Support Page.

  2. Select EBFs/Maintenance. If prompted, enter your MySybase user name and password.

  3. Select a product.

  4. Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.

    Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.

  5. Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.


 

DOCUMENT ATTRIBUTES
Last Revised: Nov 14, 2006
Part Number: DC70221-01-0550-02
Product: e-Biz Impact
Technical Topics: Security, Messaging, Cost Control, Data Management, Application Servers, Application Deployment, Transaction Processing, Application Development
  
Business or Technical: Technical
Content Id: 1048006
Infotype: Release Bulletin
 
 
 

© Copyright 2013, Sybase Inc. - v 7.6 Home / Contact Us / Help / Jobs / Legal / Privacy / Code of Ethics