Prepare IFS Touch Apps Server Database

In this step the database used by IFS Touch Apps Server is prepared. Only Oracle database can be used,

Contents

• Database

Database

You can use an existing instance or create a separate instance for the TAS schema, a pluggable database can be used.

Using IFS Applications database cloning and Push

In the IFS Applications schema the connection (i.e. address) to the TAS used for Push is stored in mobile_push_msg_setting_tab.
If the Prod database is cloned to Test, this may cause some push messages from the Test Application Server to be sent to the Prod TAS. To avoid that, exclude the table while cloning or delete the content after cloning. (When the Test TAS is recycled the connection will be updated).
The best way to prevent the Test Apps Server from pushing to the Prod TAS is to ensure the Prod TAS is unreachable from the Test installation (e.g. use a firewall block or completely separate the two networks).

In the TAS schema, the IFS User and Password information used to register each system is stored in the service_instance_tab. When a TAS is recycled, registrations will be made for each system that have credentials.

To be able to run one Prod and one Test TAS the Prod and Test systems needs to be stored in different schemas, that is, each TAS uses its own schema.These schemas can be stored in the IFS Applications Prod instance or a separate instance.

Its recommended to physically separating Prod and Test Installations so that one installation cannot adversely affect the other.   

When a cloning has been done, the Test TAS should be recycled.

Also see, Troubleshooting Push.

TAS Schema

An Oracle administrator must first create a user that can create/upgrade the TAS schema (Default name below is IFSTAS).

The installation user requires the following privileges:

• Alter Session
• Create Procedure
• Create Sequence
• Create Session
• Create Synonym
• Create Table
• Create Trigger
• Create Type
• Create View
• Unlimited Tablespace.

The IFSTAS user should be given a separate tablespace.

The TAS can be run as the installation user but it's recommended that a separate runtime user is used (Default name below is TASRUNTIME).

The runtime user requires the following privileges:

• Alter Session
• Create Synonym.

In the database folder in the TAS Installation there is a utility script called PrepareTas.sql that creates TableSpaces and the installation user (IFSTAS) and the runtime user (TASRUNTIME). The script should be run as sys connected as sysdba.