June 2009

Sun Mon Tue Wed Thu Fri Sat
  1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30        
Blog powered by TypePad
I Love JotSpot

June 09, 2009

The Right URLs for PayFlow Pro V4

If you're on version 10.6 and are applying the patch for 10.6.30.17, the release notes are incorrect in one critical way.

On page 4, the release notes say:

After you apply this release, the URL current in use is automatically updated. However, if you need to change modes in the future, you must use one of the following URLS:
  • Test mode: pilot-payflowpro.verisign.com
  • Live mode: payflowpro.verisign.com


Unfortunately, those URLs are incorrect. So in the May TechLet this was corrected to say:

Once you apply the update, you will need to change your payment URL in iMIS > AR/Cash > Set up module > Credit Card Auth to the following:

  • Test server: pilot-payflowpro.paypal.com
  • Live server: payflowpro.paypal.com

If you have previously applied the Payflow Pro updates, the payment URL must still be changed to the above URL. The old payment URLs pilot-payflowpro.verisign.com and payflowpro.versign.com will no longer work on September 1, 2009.

(emphasis added)



June 08, 2009

Applying the 10.6.30.17 Patch

Note to self:
If you are applying the .17 patch to a computer and see this error:

Error 1304.Error writing to file Payflow_dotNET.dll.  Verify that you have access to that directory.


It has nothing to do with permissions. It means that you don't have the .NET Framework 2.0 installed on that computer. That is a requirement for the .17 patch. All previous versions of 10.6.30.xx only require the 1.1 Framework. And this requirement is right there in the documentation for the patch install as Step #1.

June 02, 2009

Windows 7 releases on October 22

Details here.

Just felt like mentioning...

IMUS is the name of a scary guy on the radio.
DonImus

iMIS is the name of the software we all know and love.
SNAG-432

They are really different things.

June 01, 2009

Querying the system views of your iMIS db

My favorite teacher for all things SQL really stressed the importance of knowing the system tables that drive SQL Server. That was back in the era of SQL Server 6.0 when Enterprise Manager could be kinda stupid and sometimes fail to reflect the reality of the database. Now, many years later, in SQL Server 2005, the GUI is so much more reliable that it accurately reflects the underlying metadata.

But there are still times where it's very useful to be able to query the metadata. Beginning with SQL 2005, it is no longer recommended that you query the system tables directly. Instead, Microsoft recommends that you use the catalog views:

We recommend using catalog views to access metadata for the following reasons:

  • All metadata is made available as catalog views.

  • Catalog views present metadata in a format that is independent of any catalog table implementation, therefore catalog views are not affected by changes in the underlying catalog tables.

  • Catalog views are the most efficient way to access core server metadata.

  • Catalog views are the general interface to catalog metadata and provide the most direct way to obtain, transform, and present customized forms of this metadata.
  • Catalog view names and the names of their columns are descriptive. Query results match what might be expected by a user who has a moderate knowledge of the feature that corresponds to the metadata that is being queried.

For backwards compatibility, Microsoft included views that mirror the old system tables I am used to and since they're there, I've struggled to change my old habits of relying upon them.

Here are some examples of using the system tables to do some iMIS-related tasks.

Finding all of the triggers in a db
Here's a common one you need for doing sysadmin of an iMIS db. Prior to an upgrade, you will want to make sure you know what triggers you have. The correct way using the catalog view:

select * from sys.triggers
order by name

What permissions exist on a given table?
This query tells you what permissions have been granted on the Name table.

select  p.STATE_DESC, p.permission_name, t.name, pr.name,
                pr.type_desc 
from    sys.database_permissions p
          inner join sys.database_principals pr
                        on p.grantee_principal_id = pr.principal_id

          inner join sys.tables t on p.major_id = t.object_id
where    t.name = 'Name'


Returns a result set like this:

DELETE          Name    IMIS                      DATABASE_ROLE
INSERT            Name    IMIS                      DATABASE_ROLE
REFERENCES  Name    IMIS                      DATABASE_ROLE
SELECT           Name    IMIS                      DATABASE_ROLE
UPDATE         Name    IMIS                       DATABASE_ROLE
SELECT          Name    StandardReporting   DATABASE_ROLE

Key Dates

iMIS Resources

Other iMIS Related Resources

  • Communicate for iMIS
    The best-selling third party tool for iMIS. Made by VanDamme Associates.
  • Crystal Reports Tech Support
    Found on the website for Business Objects, today's owner of Crystal Reports.
  • L-Soft
    Makers of listserv, which is highly recommended if you have the e-Series module, e-Communities.
  • Macromedia
    Makers of ColdFusion, which the iMIS e-Series runs on.
  • VanGo Web modules
    A great set of products from VanDamme Associates

Useful Tech Stuff

  • Firefox
    A better browser than IE 6. Love the tabs.
  • GoToMyPC
    Remote Access to Your PC From Anywhere
  • LogMeIn
    Remote Access and Desktop Control Software for your PC. Has a free trial.
  • SnagIt from TechSmith
    I couldn't live without this screen capture tool (and lots more).
  • Tiny URL
    Take a long URL and make it tiny!
  • YouSendIt
    Email large files quickly, securely, and easily! AND FREE!!