Please enable JavaScript to view this site.

Estate Forums

Invantive Estate

Onetime Action:

•Choose a unique prefix per Invantive Estate environment in the database. Often ‘P_’ is used for production and ‘A_’ for acceptance.

•Enter this prefix in the RDBMS User Prefix field in the screen Settings.

•Log on as user ‘system’ on the Oracle database.

•Execute the following statement (this usually happens during the installation):

grant execute on <APPLICATIE SCHEMA>.bubs_session to system

/

grant execute on <APPLICATIE SCHEMA>.itgen_maintain_my_synonyms to system

/

•Create a trigger which takes care that during the login to the database also automatically is logged in to Invantive Estate if the user is registered in Invantive Estate:

 

create or replace trigger set_bubs_user after logon on database

begin

 --

 -- Log on to development environment if available and applicable.

 --

 obubs.bubs_session.log_on_through_oracle;

 --

 -- Log on to test environment if available and applicable.

 --

 tbubs.bubs_session.log_on_through_oracle;

 --

 -- Log on to acceptance environment if available and applicable.

 --

 abubs.bubs_session.log_on_through_oracle;

 --

 -- Log on to production environment if available and applicable.

 --

 -- Caution: you will be logged on to multiple environments at one time. Increased

 -- risk of data loss in production due to human error!

 --

 pbubs.bubs_session.log_on_through_oracle;

 --

 -- Option to automatically correct synonyms.

 -- Currently not possible due to DDL. Might become autonomous in the future.

 --

 -- pbubs.itgen_maintain_my_synonyms('PBUBS');

exception

 when others

 then

   null;

   --

   -- To debug uncomment and: raise_application_error(-20163, dbms_utility.format_error_stack || dbms_utility.format_error_backtrace);

   -- you might be having al32utf8 problems when using java such as using ojdbc14 instead of ojdbc6.

   --

end;

/

•As an alternative to a real development environment, you can also use the following example:

 

create or replace trigger set_bubs_user after logon on database

begin

 if user = 'USR_HGO_BUBS'

 then

   execute immediate

   'begin'

   || ' usr_hgo_bubs.bubs_session.set_session_info'

   || '( ''toad.sql'''

   || ', ''install'''

   || ', ''system'''

   || ', ''various'''

   || ', coalesce(sys_context(''userenv'', ''ip_address''), ''?'')'

   || ', sys_context(''userenv'', ''host'')'

   || ', ''n/a'''

   || ', ''$Header: http://svn.invantive.com/repos/p104/trunk/help/nl/manual/Topics/voorbereiding-database-eenmalig.xml 23615 2013-11-17 11:25:45Z gle3 $'' || to_char(sysdate, ''YYYYMMDDHH24MISS'')'

   || ');'

   || 'end;'

   ;

 end if;

end;

/

•In real development environments it is also easy to turn off project security via the screen Settings or with:
update bubs_instellingen_v set isg_alle_pjt_zien_vlag='Y';
commit;

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