What not to do - Case Sensitive Business Spaces

[james_richards]

I bet this about the most obvious thing ever but I went and did it. So, just offering a word to the wise that in my 8.4 installation I initially created the business space MyApp for an example. Eventually, this got corrupted due do a few years of doing massive changes (I think) without updating and publishing incrementally.

I thought this was a perfect opportunity to actually make the business space match the marketing brand name of the app that was let's say myapp. Everything looked great. I ran this for a few months after manually importing the data table by table into the new business space and I thought it was finally time to delete the initial MyApp business space. Then got the error "unable to drop table" and things are not going well lol.

Now I can't delete obsolete versions of myapp because they are "under" MyApp. I suspect I will have to create a new database during a user blackout and recreate my business spaces for all the apps and manually import all the tables (using MySQL and not Derby). I hope that is the case and that I don't have to create a new server and fresh install of AIM first!

Anywho, lesson learned. Passing it on.

[james_richards]

Actually its even worse. I now realize that the MyApp is the root business space and not "default" in the Tomcat folder. 4 years ago I thought I would only ever create one app I guess. Now do I create a new business space MyApp or hit full escape now? I guess this thread got started in the wrong spot now.

I don't think this is a "problem report" for the app but understand if this thread needs to be moved. Looking for advice on how not to compound this problem.

[customaware]

The practice I use these days is to only ever create the initial DefaultApplication in BASDB

ALL other Business Spaces are in their own DB.
Additionally, as I run Aware V6, V8.5, V8.8 and V9 on my laptop, I PostFix every Business Spaces with the Aware IM Version...

ie... Suppose my app is called MySuperApp

mySuperApp880PROD
mySuperApp880TEST
mySuperApp900PROD
mySuperApp900TEST

Except on a Production server, as there is only ever a single version of Aware and only this Business Space running...

mySuperAppPROD
mySuperAppTEST

I run both MS-SQL and MariaDB on my Laptop.
For what it is worth....

[PointsWell]

Have you changed versions of MySQL? Version 8 is case sensitive whereas prior version were not.

[customaware]

I never use MySQL

I only use MS-SQL or Maria DB as they support Sequences and MySQL does not

[james_richards]

Just as clarification here. I did not understand that the fine fellow who knew AwareIM who helped me set up this installation had renamed the Tomcat default webapps folder to my application name. I did request that because at the initial start down this road I didn't foresee any other applications. Thus I have ended up with other clients now who wonder why their application URL has a different "MyApp" {not the real name} in their URL.

Thus, when I had a corrupted application or Business Space with the same name as what should normally be the "AwareIM" folder under webapps, and I then deleted that business space, is where my trouble x2 began.

Anywho, I was able to get a support ticket and AwareSoft support was kind enough to help me get a new installation of 8.4 validated. I manually updated the tables, files and URL's to a default Tomcat folder and won't have to go through that again.

The whole thing only set me back a month. lol

[Jaymer]

It still doesn't have to be "AwareIM"
Could be something generic for all customers/apps on that server...
like "apps"

www.customapps.com/apps/blah-blah

[james_richards]

That makes sense. The folder could be "apps" and as long as you don't have a Business Space named "apps" you will never end up in the p-storm I did lol.