You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Problem when using WASaaS and DashDB Service on Bluemix.
We need to add a specific section to explain how to handle application deployment on Cloud.
Key points:
As Bluemix trial account doesn't have permission to create 'DashDB for Transactions'. I used 'DashDB for Analytics', which is available with Free Tier.
User need to create two instances for DashDB (one for ORDERDB and one for INDB), as one instance can have only one DB.
createOrderDB.sql script failed with "DashDB for Analytics", as the default DB is Column Organised. Add key work "ORGANIZE BY ROW" while creating tables.
While installing application, documentation says "Step 12. Customize the environment variables DBUNIT_SCHEMA, DBUNIT_USERNAME, and DBUNIT_PASSWORD fields. Its not very clear, as which DB instance is needed here. In case of two different DB instances, we need to give ORDERDB SCHEMA and user/pw details.
Also there are other Environment Variables, which need to be populated , such as CUSTOMER_ORDER_SERVICES_WEB_ENDPOINT and CUSTOMER_ORDER_SERVICES_TEST_ENDPOINT.
The text was updated successfully, but these errors were encountered:
This is the second part of issue #20
Problem when using WASaaS and DashDB Service on Bluemix.
We need to add a specific section to explain how to handle application deployment on Cloud.
Key points:
As Bluemix trial account doesn't have permission to create 'DashDB for Transactions'. I used 'DashDB for Analytics', which is available with Free Tier.
User need to create two instances for DashDB (one for ORDERDB and one for INDB), as one instance can have only one DB.
createOrderDB.sql script failed with "DashDB for Analytics", as the default DB is Column Organised. Add key work "ORGANIZE BY ROW" while creating tables.
While installing application, documentation says "Step 12. Customize the environment variables DBUNIT_SCHEMA, DBUNIT_USERNAME, and DBUNIT_PASSWORD fields. Its not very clear, as which DB instance is needed here. In case of two different DB instances, we need to give ORDERDB SCHEMA and user/pw details.
Also there are other Environment Variables, which need to be populated , such as CUSTOMER_ORDER_SERVICES_WEB_ENDPOINT and CUSTOMER_ORDER_SERVICES_TEST_ENDPOINT.
The text was updated successfully, but these errors were encountered: