Web Profile Configuration - auditPWD

Web Profile Configuration - Custom Properties page.

This page enables the use of web profile properties, for each property, you enter the property name, select its validation type, and provide the appropriate property value. The validation type ensures that the property value that you enter is the correct format.

One such Custom Property is...

## auditPWD

This property enables certain debug and control settings...

# http://[server]/psp/[site]/?cmd=viewsprop&pwd=[password] Displays session properties

# http://[server]/psp/[site]/?cmd=reloadconfig&pwd=[password] — Reloads the Web Profile

# http://[server]/psp/[site]/?cmd=viewconfig&pwd=[password] Displays currently cached Web Profile

Note: The [password] parameter is defined in the Web Profile as a custom property called auditPWD. Not recommended to set in production environment unless directed to do so.

Thanks
Sandeep G

 

Repeat header on each page doesn' work for RTF output

You are using "repeat as headline on each page" in a template
to generate the header on each page of a report.
However, with RTF output the header is not being generated on each page.
CauseBug <6270261> ER: RTF OUTPUT TO SUPPORT SET TABLE HEADER REPEAT, TABLE ROW KEEP-TOGETHER.
SolutionTo implement the solution, execute the following steps:1. Apply patch <7702372> plus any pre-requisite patches included in the readme file.2. Retest for the issue

 

XML Publisher code for XMLDoc Data source

import PSXP_XMLGEN:*;

import PSXP_RPTDEFNMANAGER:*;

Component string &FilePath;

Local Rowset &rsStg; /*Staging record rowset*/

Local PSXP_RPTDEFNMANAGER:ReportDefn &oRptDefn;

Local PSXP_XMLGEN:RowSetDS &oDS;

Local File &filXsdOutput, &filXmlOutput;

&filXmlInput = "//usr/local/psft/cny/dev/hc900/datafiles/" "Report_" CU_R239_FW_AET.PROCESS_INSTANCE ".xml";

/* Publish report */

&sReportname = "CU_R239_FW";

&oRptDefn = create PSXP_RPTDEFNMANAGER:ReportDefn(&sReportname);

&oRptDefn.Get();

&oRptDefn.SetRuntimeDataXMLFile(&filXmlInput);

If CU_R239_FW_AET.CU_REPORT_TYP = "A" Then

&oRptDefn.ProcessReport("CU_R239_FW_4", "ENG", %Date, "PDF");

Else

If CU_R239_FW_AET.CU_REPORT_TYP = "B" Then

&oRptDefn.ProcessReport("CU_R239_FW_5", "ENG", %Date, "PDF");

Else

&oRptDefn.ProcessReport("CU_R239_FW_6", "ENG", %Date, "PDF");

End-If;

End-If;/* send output to destination */

&oRptDefn.Publish("", "", "", CU_R239_FW_AET.PROCESS_INSTANCE);

 

BI Publisher performance issues

BI Publisher performance dependent on the Data source that is selected.
1 ) XML File Data Source ( XML File)
2) XMLDoc Data Source ( Peoplecode string - XML file )
3) Rowset Data Source (XMLDoc - Peoplecode string - Xml file)
4) PSQuery Data Source (Rowset - XMLDoc - Peoplecode string - Xml file)

XML File data source has better performance and PSQuery being the least as it has more conversion steps.

 

Verify Node Password

Integration Broker - Node Password:

One method that i use to verify the Node Password.

1. Set the password to desired value for some un-used node.

2. Compare the encrypted value of the unused Node Password & the Node for which you want to check the password using the below SQL.

select IBPASSWORD from PSMSGNODEDEFN where MSGNODENAME=''NodeName";

 

Peoplecode to Create BI publisher XML and XSD Data source file.

import PSXP_RPTDEFNMANAGER:*;
import PSXP_XMLGEN:*;
&rs = create PSXP_XMLGEN:RowSetDS();
&rsStg = CreateRowset(Record.STAG_REC);
&rsStg.Fill();
/*Create Schema*/
&mySchema = &rs.GetXSDSchema(&rsStg);
&f1 = GetFile("STAG_XSD.xsd", "W", %FilePath_Relative);
&f1.WriteLine(&mySchema);
&f1.Close();
/*Create Sample XML File*/
&myXMLFile = &rs.GetXMLData(&rsStg, "CU_Add_XSD.xsd");
&f2 = GetFile("STAG_XML.xml", "W", %FilePath_Relative);
&f2.WriteLine(&myXMLFile);
&f2.Close();