Oracle Data Reader as XML Document

Sometime you just want to return some data from the DB to client in XML format. Here is my Function to return an XML doc.

Public Function GetReaderAsXML(ByVal sql As String, ByVal Environment As String, Optional ByRef OtherOraConnection As OracleConnection = Nothing) As XmlDocument

Dim cmdfunc As New OracleCommand

If OtherOraConnection Is Nothing Then
If Not oraConnection.State = ConnectionState.Open Then
Me.ConnectToOracle(Environment)
End If
cmdfunc.Connection = oraConnection
Else
cmdfunc.Connection = OtherOraConnection
End If

cmdfunc.CommandText = sql
cmdfunc.XmlCommandType = OracleXmlCommandType.Query
cmdfunc.BindByName = True
cmdfunc.XmlQueryProperties.MaxRows = -1

Dim XmlReaderOut As System.Xml.XmlReader
XmlReaderOut = cmdfunc.ExecuteXmlReader
Dim XmlDocOut As New System.Xml.XmlDocument

XmlDocOut.PreserveWhitespace = True
XmlDocOut.Load(XmlReaderOut)

Return XmlDocOut

End Function

PeopleSoft LDAP Schema Cache Error

There is an issue sometimes when you try to cache the LDAP Server's schema if the user you are using has access to attributes with names that are longer than 50 Characters.

When it is time to setup the LDAP Directory you have the cache the the Ldap Schema on the app server. The problem comes in when we have an attribute that is longer than 50 Chars in ldap, and the process bombs.

In order to fix this, we modify the peoplecode on the PSDSCHEMA.DSDIRID fieldforula and replace ":3" with "substr(:3,1,50)" in the insert statements at lines 811, 819, 826 and 843. (In PeopleTool 8.48). Then re-run the Schema Cache Process.

If you can't modify the PSDSCHEMA.DSDIRID People code, you might need to temporally take the PSDSCHEMA record out of the peopletools permission group, just make sure u put it back in.

App Designer Basic Considerations

There are a lot of objects that can be in a project that aren't listed ing the "Development" Tab. The reason for this is that you can move objects with App Designer that you can't edit with app designer. They are made part of the project, but aren't editable. These objects sit on the "Upgrade" tab.

A prime example is content References and folders.

These are great to have in the project so that when you move it around you don't have to keep re-registering components, but can be bad if the parent folders aren’t there in the target environment etc etc…

Things to watch for:

Menus

Content References

Permission Lists

Folders

PeopleCode not pertinent to your project (it by definition shouldn’t be in your project!)

Closing:

Always check the "Upgrade" Tab on the project explorer to make sure you're not moving stuff that doesn’t need to be moved.