Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Documentation updates needed, when we run application on IBM Bluemix. #20

Closed
cvishal opened this issue Jun 20, 2017 · 3 comments
Closed
Assignees

Comments

@cvishal
Copy link
Collaborator

cvishal commented Jun 20, 2017

Need to update documents to help end user execute installation of this app smoothly.

Please note following 2 issues were observed, one for existing documentation and second one was specifically for Cloud setup (Deploy this application on WASaaS (Bluemix WAS) and DashDB for analytics, on cloud.)

Problem 1 : User Creation scenario:

There are two steps mentioned:

  1. Documentation asks us to create users, using addBusinessCustomer.sql and addResidentialCustomer.sql. And asks to create same user in the Security Registry.
  2. Towards the end, Test part of application does create few users (kbrown and rbarcia).
    These two operations need to in sync, so that user kbrown and rbarcia would be created in Security Registry and same would be populated in DB, when Test part is ran.

Problem 2 : 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.
@jesusmah
Copy link
Contributor

Problem 2 is addressed in #22

@jesusmah jesusmah self-assigned this Jun 22, 2017
jesusmah pushed a commit that referenced this issue Jun 22, 2017
@jesusmah
Copy link
Contributor

@cvishal please, check commit 2d24268 and let me know if it still confuses the user. Thanks

@cvishal
Copy link
Collaborator Author

cvishal commented Jun 26, 2017

This is good. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants