There was a comment on one of my earlier posts asking the status of the Advanced Security Manager. My developer is still working on the code although it is not on the top of his priority list. After a brief discussion, it appears the code changes, as requested by the OLAP Underground team as a condition for releasing the code, is complete and he has been working on properly commenting the code. I have directed him to make sure our automated build processes for ASM are in place and, once that is done, I would like to have some users start testing. If you are interested in testing the ASM, please drop me an email at timtow@appliedolap.com; it will probably be a week or two before I get anything out.
I also intended to blog 'real-time' about the Collaborate conference. Unfortunately, I didn't even have time to eat most of the time I was there. I will try to post something soon (after a few Dodeca installs this week, reviewing a couple of patent filings, doing a bunch of followup calls, etc).
Showing posts with label OLAP Underground. Show all posts
Showing posts with label OLAP Underground. Show all posts
Advanced Security Manager Update uploaded
We have uploaded a minor update to the Advanced Security Manager. This update contains the following changes:
- Support for exporting external authentication information (for versions 7x and higher). The new information is appended to the end of the User Access string in the export.
- Fixed a bug where command line functionality did not work with the version 6.x runtime client.
The new version is available on our website. Don't hesitate to contact us at support@appliedolap.com if and when you find issues in either of the OlapUnderground utilities that we support.
Essbase API for Unicode Applications
Recently we had a user report that the OlapUnderground Essbase Outline Extractor, which we now maintain and distribute, does not work with Unicode outlines. I had never tried working with a Unicode outline but I had my assistant take a look at it and sure enough, it didn't work. Upon further investigation, I found the ESB_INIT_T structure has a new parameter to handle Unicode (UTF-8) encoding:
' Essbase ESB Initialization Structure
Type ESB_INIT_T
Version As Long
MaxHandles As Integer
LocalPath As String * ESB_PATHLEN
MessageFile As String * ESB_PATHLEN
HelpFile As String * ESB_PATHLEN
ClientError As Integer
ErrorStack As Integer
usApiType As Integer
vbCallbackFuncAddress As Long
End Type
The usApiType parameter takes one of two constants as a parameter:
Global Const ESB_API_NONUNICODE = &H2
Global Const ESB_API_UTF8 = &H3
If you don't pass a value, the default value internally must be non-unicode as the ESB_API_NONUNICODE value is non-zero value but non-unicode applications work.
In the Outline Extractor, there is a catch-22 in the code. The EsbInit function gets called before the application can know whether the outline being targeted is from a Unicode application. We have added a checkbox to the user interface so a user can indicate if the outline being targeted from a Unicode application.
We still have one issue to work through before the Outline Extractor functions with Unicode. Visual Basic 6 does not write strings in UTF-8 encoding but rather uses ASCII encoding. Writing the strings produced by native VB6 to a file writes the wrong encoding and thus certain characters change. We still need to update the file writing algorithm to properly write the strings before we release it.
Most of my programming these days is in Java; encoding seems to be much easier in Java. Further, I do not believe a parameter like usApiType is necessary in the Essbase Java API.
' Essbase ESB Initialization Structure
Type ESB_INIT_T
Version As Long
MaxHandles As Integer
LocalPath As String * ESB_PATHLEN
MessageFile As String * ESB_PATHLEN
HelpFile As String * ESB_PATHLEN
ClientError As Integer
ErrorStack As Integer
usApiType As Integer
vbCallbackFuncAddress As Long
End Type
The usApiType parameter takes one of two constants as a parameter:
Global Const ESB_API_NONUNICODE = &H2
Global Const ESB_API_UTF8 = &H3
If you don't pass a value, the default value internally must be non-unicode as the ESB_API_NONUNICODE value is non-zero value but non-unicode applications work.
In the Outline Extractor, there is a catch-22 in the code. The EsbInit function gets called before the application can know whether the outline being targeted is from a Unicode application. We have added a checkbox to the user interface so a user can indicate if the outline being targeted from a Unicode application.
We still have one issue to work through before the Outline Extractor functions with Unicode. Visual Basic 6 does not write strings in UTF-8 encoding but rather uses ASCII encoding. Writing the strings produced by native VB6 to a file writes the wrong encoding and thus certain characters change. We still need to update the file writing algorithm to properly write the strings before we release it.
Most of my programming these days is in Java; encoding seems to be much easier in Java. Further, I do not believe a parameter like usApiType is necessary in the Essbase Java API.
Advanced Security Manager
Oracle recently took down the HDN website and not all of the content, including third party downloads, is currently available on the OTN site. Of course, someone posted on OTN their need to get ahold of the OlapUnderground Advanced Security Manager. In response, I got in contact with the OlapUnderground team and they have sent me the Advanced Security Manager (along with the source code).. We are considering taking over development and management on the ASM but, in the meantime, I have made the Advanced Security Manager files available on our website:
http://www.appliedolap.com/olapunderground/downloads/temp/secmon1.zip
I will leave this download, as received from the OlapUnderground team, on our website until it is determined if it will be available on OTN or until another home is found for it. If we decide to take on management of the ASM development, we will create a separate page for it on our website.
I guess the question is this. How many people actually still use the Advanced Security Manager? Should we spend any cycles working it at all? Note: I have promised not to release the source code unless it is cleaned up a bit. Thoughts anyone?
http://www.appliedolap.com/olapunderground/downloads/temp/secmon1.zip
I will leave this download, as received from the OlapUnderground team, on our website until it is determined if it will be available on OTN or until another home is found for it. If we decide to take on management of the ASM development, we will create a separate page for it on our website.
I guess the question is this. How many people actually still use the Advanced Security Manager? Should we spend any cycles working it at all? Note: I have promised not to release the source code unless it is cleaned up a bit. Thoughts anyone?
Subscribe to:
Posts (Atom)