How to add separate more restrictive user for running the application and another user for adding/amending data without error?
When it throws permission error or restricts to run DDL
The entityDeployer command uses the user specified in the jdbc.properties and if you have this configured to the restrictive application user, it therefore fails to amend the database structure.
This shell is reading the userid/password from jdbc.properties or customer_overrides.properties file.
In the scenario when user does not have permission to run DDL, you can set no_dbverify to true in sandbox.cfg file. Instead of running entitydeployer.sh (which will automatically execute SQLs generated when no_dbverify is false), run dbverify.sh first. The SQL scripts generated by dbverify can be executed by the user that has the permission of running DDL(Data Definition Language). After this, run entitydeployer.sh to rebuild entities.jar. Rebuild ear file and deploy fresh EAR file.
Passing a value to the "sysproperties" will not work here.
Rate this page:
Copyright and trademark information
IBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.