Please enable JavaScript to view this site.

Made in EU
Estate Forums

Invantive Estate

Perform the following steps to install the database:

•[All] Stop Tomcat, for example with ‘/etc/init.d/invantive stop’ (UNIX) or ‘net stop "Apache Tomcat"’ (Microsoft Windows).

•[All] Create/check configuration files p104/cfg/XXX.bat and p104/cfg/XXX.sql.

•[All, Installation] The tablespace will be created automatically if all data files are located in 1 folder. Else: Create a tablespace ‘<OMGEVING>’ that will contain the data of Invantive Estate. This can be done, for example, with:

 

create tablespace invantive datafile 'LOCATION' size 25m autoextend on maxsize 2000m

 

•[All, Installation] In case the application is installed for the first time, use bubs_create.bat in the bin-directory to prepare the installation of Invantive Estate. This takes about 1 minute.

•[All, Installation] If the application is installed for the first time, use bubs_smoke.bat in the bin directory to install the application. This takes approximately 60 minutes. Break off when asked if the demo data can be loaded.

•[All, Installation] Create the license with the special installation steps from doc/*.sql.

•[All, Upgrade] Run the upgrade_main.sql script from the map ddl/upgrades/build<DOEL-1>to<DOEL>. It takes approximately 10 minutes to the steps that may only be performed after the upgrade. Confine yourself to the builds between the start and target build. Execute bubs_smoke.bat located in the bin-directory if this is mentioned in the upgrade_main.sql script. It will take 60 minutes. Abort when asked if the demo data should be loaded.

•[All, Upgrade] Install the possible customizations from xx<COMPANYNAME>.sql.

•[All] Start Tomcat, for example with ‘/etc/init.d/invantive start’ (UNIX) or ‘net start "Apache Tomcat"’ (Microsoft Windows).

X

Important Safety and Usage Information

Intended Use and Limitations: This software, developed by Invantive, is designed to support a variety of business and information technology data processing functions, such as accounting, financial reporting an sales reporting. It is important to note that this software is not designed, tested, or approved for use in environments where malfunction or failure could lead to life-threatening situations or severe physical or environmental damage. This includes, but is not limited to:

  • Nuclear facilities: The software should not be used for operations or functions related to the control, maintenance, or operation of nuclear facilities.
  • Defense and Military Applications: This software is not suitable for use in defense-related applications, including but not limited to weaponry control, military strategy planning, or any other aspects of national defense.
  • Aviation: The software is not intended for use in the operation, navigation, or communication systems of any aircraft or air traffic control environments.
  • Healthcare and Medicine Production: This software should not be utilized for medical device operation, patient data analysis for critical health decisions, pharmaceutical production, or medical research where its failure or malfunction could impact patient health.
  • Chemical and Hazardous Material Handling: This software is not intended for the management, control, or operational aspects of chemical plants or hazardous material handling facilities. Any malfunction in software used in these settings could result in dangerous chemical spills, explosions, or environmental disasters.
  • Transportation and Traffic Control Systems: The software should not be used for the control, operation, or management of transportation systems, including railway signal controls, subway systems, or traffic light management. Malfunctions in such critical systems could lead to severe accidents and endanger public safety.
  • Energy Grid and Utility Control Systems: This software is not designed for the control or operation of energy grid systems, including electrical substations, renewable energy control systems, or water utility control systems. The failure of software in these areas could lead to significant power outages, water supply disruptions, or other public utility failures, potentially endangering communities and causing extensive damage.
  • Other High-Risk Environments: Any other critical infrastructure and environments where a failure of the software could result in significant harm to individuals or the environment.

User Responsibility: Users must ensure that they understand the intended use of the software and refrain from deploying it in any setting that falls outside of its designed purpose. It is the responsibility of the user to assess the suitability of the software for their intended application, especially in any scenarios that might pose a risk to life, health, or the environment.

Disclaimer of Liability: Invantive disclaims any responsibility for damage, injury, or legal consequences resulting from the use or misuse of this software in prohibited or unintended applications.
  
Disclaimer