Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire "conf" directory found under Control Center install location. Please




Download 65.38 Kb.
NameBefore starting the Control Center upgrade/uninstall process, you mu­­st backup the entire "conf" directory found under Control Center install location. Please
A typeDirectory
manual-guide.com > manual > Directory
Please Read: Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire "conf" directory found under Control Center install location. Please follow the steps below before upgrading: The following instructions apply to maintenance upgrades.

1. Stop Control Center engine

2. Back up \conf directory found under Control Center install location.

3. Proceed normally with installing the latest version of Control Center in original .

(The installer would automatically un-install the previous version - but all of the configuration data will still be there).

4. On Unix, Linux platforms, run configCC.sh

List of Fixes (or Enhancements) included in Control Center

5.4.1.0 iFix02 (Released 05/15/2014)

  1. IC97987 / R401722

Description of issue: The following exception was thrown: [java.lang.IndexOutOfBoundsException: Index: 66, Size: 18] when a rule action attempted to send a SNMP trap for an event type 66 (SLC Suppressed Notification).  This was caused by an invalid index into an array, while attempting to obtain the SNMP OID value for that event type (66).  The original reported symptom was that neither the expected alert email nor SNMP trap were processed for the associated workflow SLC and rule.

Description of fix: Added code to correctly return the requested SNMP OID to the caller (i.e. corrected the IndexOutOfBounds condition).

  1. IC98056 / R399608

Description of issue: The Web Console Statistics Viewer filter did not allow for specification of the Log Date and Log Time rules in a combination that would retrieve statistics records in a consistent and logical manner. The Log Date and Log Time rules are combined to generate the Log Date/Time column used in the statistics database table.

Description of fix: Modified code so that the user can specify Log Date and Log Time rules in a consistent and logical manner using the guidelines below. (Note that it is possible to specify illogical rules that result in fewer/more statistics records than desired, unless these guidelines are followed.)
(1) To view statistics records on a particular date, specify a Log Date rule with an "is" condition. (The Log Time option will be removed in this situation.)
(2) To view statistics records before or after a specific date , specify one Log Date rule with either a "before" or an "after" condition. Log Time is assumed to be 00:00:00 (midnight).
(3) To view statistics records before or after a specific date and time, specify one Log Date rule and one Log Time rule with both rules having the same condition ("before" or "after").
(4) To view statistics records using a range, specify four rules: one Log Date rule and one Log Time rule with both rules having an "after" condition", and one Log Date rule and one Log Time

  1. IC98668 / R408183

Description of issue: The "file.encoding" property is set to Cp1252 (instead of UTF-8), when the SCC console is activated using webstart.  The reported symptom was the customer could not use action and rule names with special characters as used in France (é è à ç...). 

Description of fix: Specified a new program argument "file.encoding=UTF-8" in the GUI jnlp files and added logic in the GUI startup code to set the system property accordingly (i.e. to the file.encoding=xxxx value).

  1. IC98294 / R405740

Description of issue: Reports submitted from the Web Console do not honor DVG or Server restrictions of the user.
Description of fix: Added code to check the DVG and Server restrictions of the user before running the report.

  1. IC98293 / R405714

Description of issue: If a server is part of a user-defined server group, and that server group is referenced in a rule, then the server cannot be removed from the server group.

Description of fix: Modified code so that the server can be removed from the server group even if the server group is referenced in rules.

  1. IC98874 / R409030

Description of issue:  The Control Center GUI will not start from the SCC webstart launch page after the user's local machine has been upgraded to Oracle JRE 7 update 51 or later.  The following exception is thrown: java.lang.SecurityException: Missing required Permissions manifest attribute in main jar.         
Description of fix:  Added the required permissions attribute in the main jar file.   

  1. R408994

Description of issue:  ORA-01502: Index 'CE_MAILBOX_ID_IX' and 'CE_RECORD_INDEX' or partition of such index become unusable after new partitions are created.
Description of fix:  Added code to create the CE indexes as LOCAL the first time configCC is run, after an upgrade.

  1. IC99352 / R411865

Description of issue: SQL exception thrown for a query that tries to retrieve records from Connect:Direct i5/OS when Oracle is the database for Control Center.

Description of fix: Removed the query optimization that caused the query to fail. 

  1. IC99310 / R410175

Description of issue: Variables currently available in SCC actions are insufficient to manage C:X (Connect:Express) transfer error conditions resulting from a connection error. These errors generate an event type 11 (Server Error) record, with minimal detail information about the attempted transfer. The customer requires all of the available information residing on the C:X server be made available in Sterling Control Center to effectively report on the failed event.

Description of fix:  Added the following CX.xxxxx variables to the EventVariables.properties file.

CX.CRCO=CRC Used
CX.FAPI=User Description of the Transfer
CX.FLAO=Interconnected File Agent is Active
CX.FRLG=Local Record Length
CX.MULT=Multi-Article is Used in Fpfu Data
CX.NMGS=Network Message Size
CX.PI11=PeSIT File Type
CX.PI15=File Date and Time Creation
CX.PID=Process Identifier of the Process that Executed the Request
CX.PRIO=Transfer Priority
CX.REQD=Request Accepted Date
CX.REQR=Name of the Entity that Submitted the Request
CX.RETN=Number of Retries
CX.RSTA=Transfer Status
CX.TCPA=Remote Node TCP/IP Address
CX.TCPH=Remote Node Host Name
CX.TCPP=Remote Node Port Number
CX.TRTN=Translation Table Identifier
CX.TYPC=Compression Type
CX.TYPD=Data Type
CX.TYPF=File Type
CX.TYPN=Notification Type
CX.TYPP=Partner Type
CX.FTOP=Type-Structure-Mode Options
CX.FTSU=Store Unique Option

Note: A Corresponding C:X code modification is required to make these new variables available in SCC. At the time of this fix, the new variables will only be present for C:X Unix transfer errors. C:X Unix 1.5.0.11 fix pack 12 and beyond is required, in addition to SCC fix in order for the variables to be available to SCC actions.

  1. IC99270 / R410180

Description of issue: Connect:Express reports are not displayed within Cognos report viewer, when Oracle is the database.
Description of fix: Modified the length of the DATE_TIME column to 255, as the date/time value provided by CX exceeded the defined length of 30.

  1. IT00253/R413884

Description of issue: Views do not get created during the upgrade process when DB2 is used as the database.
Description of fix: Added code to add missing views regardless of the database type, while configuring Control Center by running configCC. The engine will not come up, if any tables or views are missing. The user must run configCC in order for it to create any missing tables or views, during an upgrade process

  1. IC99835/R413839

Description of issue: Control Center shuts down while trying to retrieve statistics for the user specified criteria for a C:E Unix node.

Description of fix: Modified code to run the query from a data access object that does not initiate a SQL shutdown error.

  1. IT00388/R415351

Description of issue:  When a userid is deleted on Linux/Unix, the /conf/Users/user.xml file does not get deleted, if it contains any upper case characters.  This is because the userid value in the file pathname is changed to lower case.  In systems which are case sensitive, the file was not detected and consequently did not deleted.   
Description of fix:  Construct the file path name using the exact userid value that is being deleted (i.e. preserve the casing), when deleting the file.  



  1. IT00528/R417208

Description of issue: Customer requested that 25 recently added C:X (Connect:Express) variables to Actions, also be exposed to the Rules Parameters selection menu.  Additionally, the customer requested one brand new C:X variable be added to SCC (SSLRC - SSL Return Code).     

Description of fix:  Added the following CX.xxxxx variables to the RuleMatchKeyInfo.properties file.   
CX.CRCO=CRC Used
CX.FAPI=User Description of the Transfer
CX.FLAO=Interconnected File Agent is Active
CX.FRLG=Local Record Length
CX.MULT=Multi-Article is Used in Fpfu Data
CX.NMGS=Network Message Size
CX.PI11=PeSIT File Type
CX.PI15=File Date and Time Creation
CX.PID=Process Identifier of the Process that Executed the Request
CX.PRIO=Transfer Priority
CX.REQD=Request Accepted Date
CX.REQR=Name of the Entity that Submitted the Request
CX.RETN=Number of Retries
CX.RSTA=Transfer Status
CX.TCPA=Remote Node TCP/IP Address
CX.TCPH=Remote Node Host Name
CX.TCPP=Remote Node Port Number
CX.TRTN=Translation Table Identifier
CX.TYPC=Compression Type
CX.TYPD=Data Type
CX.TYPF=File Type
CX.TYPN=Notification Type
CX.TYPP=Partner Type
CX.FTOP=Type-Structure-Mode Options
CX.FTSU=Store Unique Option
CX.SSLRC=SSL Return Return Code

  1. IT01179/R421517

Description of issue: Alerts report does not run on Cognos when Oracle is used as the DB.
Description of fix: Corrected code in order for the alerts report to work.

  1. IT01223 / R420920

Description of issue: When a connection to a MQ server fails, the code attempted to retry. However it did not attempt to retry the connection.

Description of fix: Null out the producer object so that the connection will be retried.

List of Fixes (or Enhancements) included in Control Center

5.4.1.0 iFix01 (Released 11/08/2013)

  1. IC93052

Description of issue: Upgrading from 5.4.0.1 DB2 z/OS partitioned tables to 5.4.1 fails

Description of fix: Corrected the code to ignore the SQL error when creating a large table space, if one already exists.

  1. IC93051

Description of issue: Unable to execute Alerts Summary Report if Control Center engine is configured with a DB2 database.

Description of fix: Due to a bug in the JDBC Service, the Alerts Summary Report could not be executed.

  1. IC93057

Description of issue: Unable to launch SCC via thin client IBM Sterling Control Center Web Console, when using a firewall to redirect.

Description of fix: Instead of redirecting to /scclayout/ in LoginServlet, just return a HTML status code of 200 (SC_OK) and let login.jsp do the redirect on the xhrPost load..

  1. IC93260

Description of issue: Received the following error messages during bulk data movement of C:X (Connect:Express) stat records from the production to staging database: ERROR BulkDataMover - Error while moving CX_STATS_LOG data. ERROR BulkDataMover - Invalid column name 'DATE_TIME'. This was caused by a SQL statement, which erroneously specified DATE_TIME, instead of LOG_DATE_TIME.

Description of fix: Changed the reference in the SQL statement from DATE_TIME to LOG_DATE_TIME, which is the correct column name in the CX_STATS_LOG table.

  1. IC93898

Description of issue: FATAL ERROR in the Control Center engine log when monitoring a Sterling File Gateway instance that has custom protocols defined within SFG, that eventually trigger a custom business process that generates process data with XML elements that cannot be parsed by the XML parser used by Control Center.

Description of fix: If a custom protocol is defined in such a way that the process data has elements that are not usually provided by File Gateway, for instance, something of the nature of Params/LocalCDNodeName that are derived from the protocol, the user must add a system property to the engine.properties (located under the conf folder) to allow Control Center to parse the XML elements properly. The System Property is called SFG_IGNORE_KEYS, and it’s added to the engine.properties as SFG_IGNORE_KEYS=Params to ignore the XML element Params.

  1. IC93829 – R383161

Description of issue: SCC user authentication fails when using SEAS (Sterling External Authentication Service) and the password contains special characters (eg. &, <, >, etc.).

Description of fix: Added code to marshall the userid and password, when building the SEAS authentication xml string, allowing all valid special characters to be used in these fields.

  1. IC93829 - R383917

Description of issue: CC does not bind to a specific IP address for secure HTTP connections. SCC always listens on 0.0.0.0, because this is the value always saved in the secure connection xml file.

Description of fix: Corrected the installation logic when configCC is executed. The user is now prompted to specify a specific IP address, if they desire, and the address is saved in the xml configuration file and used as the address to bind to by the SCC HTTPS listener.

  1. IC93829 - R383599

Description of issue: The SCC web console logs show trying to make calls to google-analytics.com. The CRE (Common Rendering Engine) uses Apache Shindig which makes calls to Google Analytics.

Description of fix: Commented out lines in the shindig-extras-2.5.0-SNAPSHOT.jar to exclude this feature (i.e. #features-extras/analytics/feature.xml)

  1. IC93829 – R384185

Description of fix: The user login count, when logged in through the web UI, is not incremented and decrement properly, sometimes causing count to be incorrect.

Description of fix: Corrected the user login/logout count logic in the web UI. Note that if the browser is closed without logging off, the count will be decremented when the session times out.

  1. IC94051

Description of issue: If you have a password policy setup in /conf/security/passwordPolicy.xml and specify a minimum password length greater than 0, then try to add/update a user using SEAS you get an error, stating the password length is less than the minimum, because the password policy was erroneously being checked.

Description of fix: Added a check in the code to bypass password policy validation if the user is defined to use External Authentication.

  1. IC94165

Description of issue: Special characters in passwords don't work for the web UI. Password was URLEncoded coming from the Web UI, so special characters were changed to their %xx equivalents.

Description of fix: Call URLDecoder to change the special characters back.

  1. IC94166

Description of issue: Special characters in passwords such as @ don't work for stopEngine.sh

Description of fix: Modified the code to allow any special characters for user's password that are available on US keyboard.



  1. IC93829 – R387632

Description of issue: WebSphere Application Server Liberty isn't honoring the binding to a specific IP address but uses 0.0.0.0 instead.

Description of fix: Corrected the code that would incorrectly set the listen address when a specific listen address is specified.

  1. IC 94239

Description of issue: Sterling Integrator/File Gateway reports take a long time and do not generate any results.

Description of fix: Modified the reporting service DAO to not invoke the optimization code as it causes ambiguity with regards to column definitions.

  1. 15. IC94362 

Description of issue: The JDBC connection string for an Oracle SCAN configuration is not properly configured with in Cognos connection.

Description of fix: Modified the code to identify Oracle SCAN configurations.

  1. 16. IC94680 

Description of issue: SCC is not pulling all the statistics information from C:E/UNIX node on a consistent basis. C:E Unix has no way to uniquely identify a statistics record, so SCC attempts to cover this by assigning seq numbers.

Description of fix: Increased the sequence number range (for each second) from 10,000 to 100,000 for each CE Unix record category (ACD, RCD, OFF) and revised the logic which requests stat records from CEU to properly maintain record positioning between requests.

  1. 17. IC94679 

Description of issue: During configCC processing, a non-existing keystore or truststore file does not give error. Processing continues accepting user input and writes the invalid path in the installation.properties file. The error is then detected during SCC engine startup.

Description of fix: Added logic in configCC processing to check for a valid keystore/truststore path. If the path is invalid, configCC exits with corresponding error messages.

  1. IC95001

Description of issue: Handled alerts re-appear in the Active Alerts monitor.

Description of fix: Modified code to set the sequence number for those events that don't have one, and which eventually throw an exception.

  1. IC94741

Description of issue: Sterling File Gateway reports within Control Center do not display all the

transfers, and only display a subset of the transfers.

Description of fix: Added/Modified code that would retrieve file gateway records in batches

and display reportLimit number of records in the report.

  1. IC94681 - R388204

Description of issue: The following exception was being thrown in the SCC FTP Agent: WARNING: Failed to open connection: java.io.StreamCorruptedException: invalid stream header xxxxxxxx Throwable occurred. This error occurred because a specific log file name was specified for event logging.  The code expected a wildcard in the name as to assume a series of multiple log files to be used..

Description of fix: Add logic in the code to check for a single filename with no wildcard filter.

.

  1. IC95752

Description of issue: A Process History request for a QuickFile server results in the following SQL Exception msg : ORA-00918: column ambiguously defined.  The Process History query erroneously contained 2 occurrences of SERVER_DATA_3 in the SELECT statement. 

Description of fix: Corrected the query by removing the duplicate column name.

  1. IC95156

Description of issue: When updating a calendar, the range start/end dates are incorrectly displayed on the corresponding date buttons.  The start date always displays the default of today's date and the end date always displays the default of December 31 of the last selectable year (i.e. current year+1).  The actual start/end dates of the calendar should be displayed.  The customer also noted that more years into the future should be available in the year selection drop-down box.

Description of fix: Corrected the start date and end date buttons to display the correct user specified date values. Also, increased the number of years into the future that are available in the drop down box from current year+1 to current year+10.

  1. IC95095

Description of issue: OS commands are executed synchronously causing the threads to be blocked. 

Description of fix: Added code that would allow the OS commands to be executed asynchronously.

  1. IC96072/IC96073

Description of issue:  Date/time values are not correctly converted if time zone is EST.
Description of fix:  Modified code to use America/New_York as the time zone when connected to Cognos the first time.

  1. IC96103

Description of issue:  Control Center reports that no longer exist on Cognos cannot be deleted.
Description of fix:  Added code that will allow the user to delete reports from the UI, while making sure the list of reports that exist on Control Center match with those that exist on Cognos BI server.

  1. IC 96225

Description of issue:  SCC is not pulling all the information from Connect:Enterprise UNIX node on a consistent basis.
Description of fix:  Modified code to keep track of the statistics records already gathered from C:E UNIX using unique sequence numbers. (Note that the -n parameter should be added to the C:E UNIX log daemon startup script. Refer to the C:E UNIX documentation for more information.)

  1. R398885

Description of issue: Need JRE upgrade to include recent java fixes.  

Description of fix: Upgraded the java version used by Control Center and Cognos to JRE 1.6 SR14 and applied Cognos maintenance 10.1.6303.1096.

  1. IC96764
    Description of issue: Query performance on Oracle Database is too slow.
    Description of fix: Added new indexes to the CE_STATS_LOG table that would help improve the performance of the query, that's built by the engine, when the user filters statistics.



  1. IC96890
    Description of issue: Control Center shuts down when retrying a query that's built to filter stats
    Description of fix: Added new DAO objects that will only attempt the query once, and prevents the engine from shutting down.



  1. R400353
    Description of issue: SFG Consumer report does not display transfers in progress.
    Description of fix: Modified the report definition xml to display transfers in progress.



  1. IC96983
    Description of issue: Alert properties display incorrect information, for an event that transpired on a C:E UNIX node.
    Description of fix: Corrected the SQL query that retrieved information from the view.

32. R400288

Description of issue: Blanks not allowed in userid for C:D Windows node. When embedded blanks used in node definition, configuration management was not presented as an option in the right-click menu.

Description of fix: Functional authority userid, and user proxy name and local_userid fields now allow embedded blanks and internal commands are now built correctly using those fields with embedded blanks.

33. IC96933
Description of issue: Cognos Reports disappear despite being saved.
Description of fix: Added code to get rid of temporary reports that are saved within the IBMControlCenter folder, and not globally. Also introduced a new system property COGNOS_TEMP_REPORTS_CLEANUP_INTERVAL, which represents the days, the task waits before deleting the report.

34. R402153

Description of issue: The Web Console does not display any of the grids (e.g. Server List Viewer) in FireFox version 25.

Description of fix: A fix was made to the Dojo code to display the grids correctly for FireFox version 25.








Share in:

Related:

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconFurnish and install a control panel to interface automatic shut down...

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconDynatest Control Center and Field Programs

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconDescription of issue: The Control Center console displays a value of

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconAccess Control & Video Systems One Town Center Road Boca Raton, fl...

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconFor more detailed info of this latest update please download the...

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconFor more detailed info of this latest update please download the...

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconGuide for System Center Management Pack for Active Directory for Operations Manager 2012

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconGuide for System Center Management Pack for Active Directory for Operations Manager 2012

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconManual release switches and the load distribution center. The Dcr...

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconControl Goals of the Information Process

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconImplementing Statistical Process Control (spc)

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconThe Accessible Technology Webinar Series is sponsored by the Great...

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconSchedule-based system providing maximum flexibility of programming...

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconProcess control plant with industrial instrumentation and service module

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconEpc software Install/Update/Uninstall Instructions

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconAbstract In August of 2004, the aef center published its aef center...

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconSouthwest ada center and Great Lakes ada center, members of the ada national Network

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconResearch Service, Veterans Affairs Medical Center, Department of...

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconHeidelberg launches Prinect Inpress Control 2 – with faster setup...

Before starting the Control Center upgrade/uninstall process, you mu­­st backup the entire \"conf\" directory found under Control Center install location. Please iconStep 1: Attend an approved fda better Process Control School Class for Acidified Foods




manual




When copying material provide a link © 2017
contacts
manual-guide.com
search