四 8

HOW TO: Achieve High Availability for Web Services Hub in the event of a failover

Informatica , Add Comment (1)

Solution

Using High Availability for Web Services Hub, a client application can access the Web Service even in the event of failover of the Web Service to another node (when the URL changes). To achieve this, use either of the following:  

  • Third party load balancer
  • Sample third party load balancers provided by Informatica (used only for test environment) 

Third party load balancer 

In the Administration Console, provide the HubLogicalAddress in the Advance properties of the Web Services Hub. For the HubLogicalAddress, provide the URL of the third party load balancer that manages the Web Services Hub. This URL is published in the WSDL for all Web Services that run on a Web Services Hub managed by the load balancer. 

With a load balancer, the client application sends a request to the load balancer and the load balancer routes the request to an available Web Services Hub. Any of the Web Services Hub services can process requests from the client application. The load balancer does not verify that the host names and port numbers given for the Web Services Hub services are valid or that the services are running.  

Before you send requests through the load balancer, ensure that the Web Service Hub services are available.

Some of the third party load balancers that can be used (available on the Web) are Apache tcpmon and Apache jmeter.

Sample third party load balancers provided by Informatica

Informatica provides sample third party load balancers (used only for test environment). This can be used to understand the usage of load balancer with web Services Hub. This sample third party load balancer is present at infa_home/server/samples/WebServices/samples/SoftwareLoadBalancer. 

Before using load balancer, read the Readme.txt file which is present in the same path. This guides you on:

  • How does the load balancer work
  • How to set up the Configuration File that is used by the load balancer 
Note

Informatica third party load balancers can be used only for test environment and not for production environment.


四 8

HOW TO: Disable the XMLW_31213 error messages in the PowerCenter

Informatica Add Comment (1)
Problem Description

The following error is in session log:

Error XMLW_31213 : Row rejected due to duplicate primary key.

Data is written correctly to target, but above error will appear multiple times in session log and it will grow to very large size.  Is there away to stop this message from being written to the session log?

Solution

In order to fix the issue do the following:

  1. Select Integration Service in the Administration Console
  2. Go to Properties > Configuration Properties >
  3. Click Edit
  4. Clear the XMLWarnDupRows option.

More Information

Setting the custom property XMLWarnDupRows to “NO” will not resolve this issue as it has been replaced by the XMLWarnDupRows Integration Service property.

To use the option on PowerCenter 8.5.1 install the latest HotFix.

Reference

PowerCenter Administrator Guide > “Creating and Configuring the Integration Service” > “Configuring the Integration Service Properties” > “Configuration Properties” > “Table 9-6. Configuration Properties for an Integration Service”


十一 25

How to create a Time Dimension in Framework Manager

Cognos , Add Comment (1)

Description:
This document describes how to create a Time Dimension in Framework Manager which is similar to a Time Dimension created in Powerplay Transformer.

Steps:

  • Right-click on the Namespace and choose Create->Regular Dimension.
  • From Available Items drag the date column and drop it under Hierarchies.
  • Click the ellipsis in Source field to open Calculation Definition windows.
  • Change the name of the calculation to Year.
  • Use ‘cast’ and ‘extract’ functions to extract the years from the date column and convert it to character string, e.g.:
    cast(extract ( year, [].[].[] ) , char(8))
  • Back in the Dimension Definition windows, click the ellipsis in the Role field.
  • Assign _businessKey and _memberCaption roles.
  • Under Hierarchies, Add Levels for Month and Day.
  • Repeat the steps 3-7 for the Month and Day using expressions:
    cast(extract ( month, [].[].[] ) , char(8))
    cast(extract ( day, [].[].[] ) , char(8))

    • Note:
    ‘cast’ function has to be used to convert a numeric field to a string as _memberCaption Role cannot be numeric.


    十一 24

    How To: Generate multiple worksheets from Report Studio

    Cognos , , , Add Comment (1)

    Description:
    How to generate multiple worksheets in excel from a report studio page

    Environment:
    Windows [All]

    Solution:
    Use grouping on a query item in the page break to generate separate excel worksheets

    Steps:
    1. Create a list report
    2. Group on a query item in the list report
    3. Open the page explorer and click on pages
    4. Add a page break using the grouped query item
    5. Run the report to generate an XLS output


    十一 24

    How to publish a package after modifying the model without impacting existing reports

    Cognos , Add Comment (0)

    Description:

    How to publish a package after modifying the model without impacting existing reports based on that package.

    Solution:

    This is essentially a question about how model versioning works.

    If you want all your old reports to still work fine after changing a model, you need to enable model versioning when you publish the package in Framework Manager. With this option checked, ReportNet (or Cognos 8) will create a new version of the model for this package in the content store, instead of overwriting the existing model.

    Once done, the published package will have multiple versions of the model in the content store. All old reports will automatically link to the old model, and all new reports will be created against the new model.

    Please be aware, however, that if you open an existing report from within the Studios, it will run against the newest model. There may be a validation prompt, and it may result in error messages becasue the old report may not match the metedata of the newest model.

    Steps:
    1. Check Enable model versioning in Framework Manager in the package publishing wizard.
    2. Publish the package.


    « Older Posts 下一页 »