-
Notifications
You must be signed in to change notification settings - Fork 612
Migrating 1.3 to 1.4
Ruben de Laat edited this page Apr 5, 2015
·
1 revision
...is not possible using the normal database upgrade scripts, e.a. is not automatic.
However there is a way to get the most important data migrated, but it involves more manual work.
- Always make sure you backup first
- This type of migration requires both the old and new server runnning at the same time, obviously they have to be able to find each other on the network
- Make sure there is an admin account with the same name/password on both servers
- In your local environment (Eclipse for example), run TriggerImportDataRemote with the right arguments (see documentation in file). This call will end quickly, but starts the migration on the new server.
- Wait and read the logs of the new server
This has only been tested once!
Get Started
- Quick Guide
- Requirements Version 1.2
- Requirements Version 1.3
- Requirements Version 1.4
- Requirements Version 1.4 > 2015-09-12
- Requirements Version 1.5
- Download
- JAR Starter
- Setup
Deployment
- Ubuntu installation 1.3
- Windows installation
- Security
- Memory Usage
- More memory
- Performance statistics
- Large databases
Developers
- Service Interfaces
- Common functions
- Data Model
- Low Level Calls
- Endpoints
Clients
BIMServer Developers
- Plugins in 1.5
- Plugin Development
- Eclipse
- Eclipse Modeling Framework
- Embedding
- Terminology
- Database/Versioning
- IFC STEP Encoding
- Communication
- Global changes in 1.5
- Writing a service
- Services/Notifications
- BIMserver 1.5 Developers
- Extended data
- Extended data schema
- Object IDM
New developments
- New remote service interface
- Plugins new
- Deprecated
- New query language
- Visual query language
- Reorganizing BIMserver JavaScript API
General