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
{{ message }}
This repository was archived by the owner on Apr 21, 2024. It is now read-only.
7
7
8
-
The following sections provide step-by-step guidelines for managing the WSO2 Identity Server 5.4.0 deployment pattern 2 BOSH release.
8
+
The following sections provide general steps required for managing the WSO2 Identity Server 5.4.0 deployment pattern 2
9
+
BOSH release in a BOSH environment deployed in the desired IaaS.
9
10
10
-
For clarity, examples for the relevant steps have been provided for managing the BOSH release in a [BOSH Lite](https://bosh.io/docs/bosh-lite) environment.
11
+
For step-by-step guidelines to manage the BOSH release in specific environments, refer the following:
12
+
-[In a local environment](bosh-lite.md) (using BOSH Lite)
Once you setup the BOSH Lite environment, visit the VirtualBox application to confirm a new VM has been created.
53
-
54
-
55
-
56
63
3. Move back to the root directory of deployment pattern 2 BOSH release (`<pivotal-cf-is>/pattern-2/bosh-release`).
57
64
58
65
```
59
66
cd ..
60
67
```
61
68
62
-
4. Add the WSO2 Identity Server 5.4.0 and Identity Server Analytics 5.4.0 WUM updated product distributions, JDK distribution and MySQL JDBC driver in the form of release blobs.
69
+
4. Add the WSO2 Identity Server 5.4.0 and Identity Server Analytics 5.4.0 WUM updated product distributions, JDK distribution and MySQL JDBC driver
70
+
in the form of release blobs.
63
71
64
72
Here, the **environment-alias** refers to the alias provided when saving the created environment, in step 2.
65
73
@@ -70,25 +78,11 @@ In order to create the BOSH release for deployment pattern 2, you must follow th
70
78
bosh -e <environment-alias> add-blob <local_system_path_to_WSO2_IS_Analytics_distribution> wso2is_analytics/wso2is-analytics-<version>.zip
71
79
```
72
80
73
-
**e.g.**
74
-
Assuming that,
75
-
76
-
- the created BOSH environment (with BOSH Lite as the Director) was saved with alias `vbox`, in step 2
77
-
- the required binaries reside within `~/Downloads` directory
78
-
79
-
```
80
-
bosh -e vbox add-blob ~/Downloads/jdk-8u144-linux-x64.tar.gz oraclejdk/jdk-8u144-linux-x64.tar.gz
81
-
bosh -e vbox add-blob ~/Downloads/mysql-connector-java-5.1.34-bin.jar mysqldriver/mysql-connector-java-5.1.34-bin.jar
82
-
bosh -e vbox add-blob ~/Downloads/wso2is-5.4.0.zip wso2is/wso2is-5.4.0.zip
83
-
bosh -e vbox add-blob ~/Downloads/wso2is-analytics-5.4.0.zip wso2is_analytics/wso2is-analytics-5.4.0.zip
84
-
```
85
-
86
81
5. **[Optional]** If the BOSH release is a final release, upload the blobs (added in step 4). Please refer
87
82
[BOSH documentation](https://bosh.io/docs/create-release.html#upload-blobs) for further details.
88
83
89
-
**e.g.**
90
84
```
91
-
bosh -e vbox -n upload-blobs
85
+
bosh -e <environment-alias> -n upload-blobs
92
86
```
93
87
94
88
6. Create the BOSH release.
@@ -105,34 +99,41 @@ In order to create the BOSH release for deployment pattern 2, you must follow th
105
99
```
106
100
Please refer [BOSH Documentation](https://bosh.io/docs/create-release.html#final-release) for detailed information on creating a final release.
107
101
108
-
## Deploy the BOSH Release
102
+
## Deploy release
109
103
110
-
1. Setup and configure external product MySQL database(s).
104
+
1. Setup and configure external product database(s).
111
105
112
-
- Following table shows the external product database configurations, which have been set as properties under WSO2 Identity Server and Analytics job specifications
106
+
- Currently, it is expected that the external database holds the user management, registry, identity and workflow feature database tables
107
+
for Identity Server and Identity Server Analytics.
108
+
Please see WSO2 Identity Server [Documentation](https://docs.wso2.com/display/IS540/Setting+Up+Separate+Databases+for+Clustering)
109
+
for further details.
110
+
111
+
- Following table shows the external product database configurations, which have been set as properties under WSO2 Identity Server job specifications
113
112
(**e.g.** see `properties` section under `<pivotal-cf-is>/pattern-2/bosh-release/jobs/wso2is_<job_number>/spec`).
114
113
115
114
<br>
116
115
117
116
Property | Description | Default
118
117
-------- | ----------- | -------
119
-
wso2is.mysql.host | Hostname/IP of the MySQL server in which WSO2 Identity Server product database resides. | 192.168.50.1
120
-
wso2is.mysql.product_db | Name of the WSO2 Identity Server product database. | wso2is_db
121
-
wso2is.product_db.username | Username of the WSO2 Identity Server product database user. | root
122
-
wso2is.product_db.password | Password of the WSO2 Identity Server product database user. | root
123
-
124
-
If you customize any of the above configurations in following steps, change the default property values to customized values in each job specification.
125
-
126
-
- Create the product database. For this purpose, execute the `<pivotal-cf-is>/pattern-2/bosh-release/dbscripts/mysql.sql` script.
127
-
128
-
```
129
-
DROP DATABASE IF EXISTS <wso2is.mysql.product_db>; CREATE DATABASE <wso2is.mysql.product_db>;
130
-
USE <wso2is.mysql.product_db>; SOURCE /dbscripts/mysql.sql;
131
-
```
118
+
wso2is.user_ds.url | Connection URL of the user data source. | -
119
+
wso2is.registry_ds.url | Connection URL of the registry data source. | -
120
+
wso2is.identity_ds.url | Connection URL of the identity data source. | -
121
+
wso2is.bps_ds.url | Connection URL of the BPS data source. | -
122
+
wso2is.db.driver | Database driver class name of the data source. | -
123
+
wso2is.db.username | Username of the WSO2 Identity Server product database user. | root
124
+
wso2is.db.password | Password of the WSO2 Identity Server product database user. | root
125
+
wso2is_analytics.user_ds.url | Connection URL of the user data source | -
126
+
wso2is_analytics.registry_ds.url | Connection URL of the Registry data source | -
127
+
wso2is_analytics.event_store_ds.url | Connection URL of the event store data source | -
128
+
wso2is_analytics.processed_data_store_ds.url | Connection URL of the processed data store data source | -
129
+
wso2is_analytics.db.username | Username of the WSO2 Identity Server Analytics product database user | root
130
+
wso2is_analytics.db.password | Password of the WSO2 Identity Server Analytics product database user | root
131
+
132
+
Among the above, the properties with no default values **must** be set in the deployment manifest,
133
+
prior deployment of the release.
134
+
If you intend to customize any of the properties with default values, you may set the customized values
135
+
in the deployment manifest, prior to deployment of the release.
132
136
133
-
This will create the tables to hold user management data, identity related data and workflow feature data
134
-
(see [Setting Up Separate Databases for Clustering](https://docs.wso2.com/display/IS541/Setting+Up+Separate+Databases+for+Clustering)).
135
-
136
137
2. Move to the root directory of deployment pattern 2 BOSH release.
137
138
138
139
```
@@ -150,74 +151,55 @@ In order to create the BOSH release for deployment pattern 2, you must follow th
150
151
```
151
152
bosh -e <environment-alias> upload-stemcell <URL/local_system_path_to_stemcell>
152
153
```
153
-
154
-
**e.g.** When uploading the stemcell to BOSH Lite environment created in previous section (see example steps under section [Create the BOSH Release](#create-the-bosh-release)),
155
-
156
-
```
157
-
bosh -e vbox upload-stemcell https://bosh.io/d/stemcells/bosh-warden-boshlite-ubuntu-trusty-go_agent
158
-
```
159
154
160
155
5. Upload the deployment manifest.
161
156
162
157
```
163
-
bosh -e <environment-alias> -d wso2is-pattern-2 deploy manifests/wso2is-manifest.yml
164
-
```
165
-
166
-
**e.g.** Uploading the deployment manifest to BOSH Lite environment
167
-
168
-
```
169
-
bosh -e vbox -d wso2is-pattern-2 deploy manifests/wso2is-manifest.yml
158
+
bosh -e <environment-alias> -d wso2is-pattern-2 deploy manifests/<deployment-manifest>.yml
170
159
```
171
160
172
161
## Output
173
162
174
-
To find the IP addresses of created instances via the BOSH CLI and access the WSO2 Identity Server and Analytics management consoles via a web browser,
163
+
To find the IP addresses of created instances via the BOSH CLI and access the WSO2 Identity Server management console via a web browser,
175
164
176
165
1. List all the instances within a deployment.
177
166
178
167
```
179
168
bosh -e <environment-alias> -d wso2is-pattern-2 vms
180
169
```
181
-
182
-
**e.g.** To find the deployed job instances within the deployment in BOSH Lite,
183
-
```
184
-
bosh -e vbox -d wso2is-pattern-2 vms
185
-
```
186
-
187
-
188
170
189
171
2. SSH into an instance.
190
172
191
173
```
192
174
bosh -e <environment-alias> -d wso2is-pattern-2 ssh <instance_id>
0 commit comments