Wiki source code of Connecteur Business Objects

Last modified by jhurst on 2021/04/21 10:01
Show last authors
1 {{ddtoc/}}
2
3 = Prerequisites =
4
5 * Follow instructions for deploying ddbobridge on Business Objects’ server (C.f. tutorial called “boconnector_technical_en.pdf”).
6 * A BO server and access identifiers (cf. below)
7 * A report ID (not mandatory)
8
9 = Selection of the datasource =
10
11 DigDash Enterprise allows you to retrieve information from your BusinessObjects' server.
12
13 Select the type of report you want to work with, in the toolbar at the bottom of the page.
14
15 [[image:bo_connector_en_html_1074d530141bae54.gif]]
16
17 [[image:bo_connector_en_html_96dfda34a50fc7f9.png||height="141" width="430"]]
18
19
20
21 **OR** click on **New model** in the datasource manager tab and choose **BusinessObjects Report**.
22
23 [[image:bo_connector_en_html_339522b845b92050.png||height="62" width="217"]]
24
25
26 [[image:bo_connector_en_html_6e5a78fd137b6cfb.png||height="384" width="267"]]
27
28
29 = Authentication =
30
31 For a first-time BO connection via Digdash, the following authentication fields are required (first in **Manual** connection mode ; change into **Named** connection mode to save the fields) :
32
33 [[image:bo_connector_en_html_64b99fc266a46b73.png||height="160" width="596"]]
34
35 __Screenshot: authentication fields to connect to BO via Digdash in Manual mode__
36
37
38 * **BO server URL** : it is the BO application server (Tomcat) followed by the port number :(((
39 http:~/~/{IP address of the BO application server}:{Tomcat’s port number}
40
41 __Example__ : http:~/~/boAppServer:8080
42 )))
43 * **CMS name** (or System) : it is the BO engine server followed by the port number :(((
44 {IP address of the BO engine}:{CMS’ port number}
45
46 __Exemple__ : boEngServer:6400
47 )))
48 * **Authentication type :** the type is «** Enterprise **» most of the time
49 * **User**
50 * **Password**
51
52 You can check if the connection is established with the button « **Test connection** ».
53
54 (% class="box warningmessage" %)
55 (((
56 **Warning**: if you deal with a **secured connection (https)**, please refer to the end of this document to know how to proceed (Cf Part VIII “**Importing the certificate for a secured connection**”).
57 )))
58
59 = Getting a BusinessObjects report =
60
61 Enter in the text field the ID of the report you want to charge as a DataSource and its type.
62
63 If the ID is valid, clicking the “Reload” button will automatically update the UI (User Interface) with data related to the chosen report.
64
65 [[image:bo_connector_en_html_d3f66d87ea5da7ea.png||height="189" width="598"]]
66
67 __Screenshot: entering the report ID the user wants to retrieve and choosing the report type__
68
69
70 [[image:bo_connector_en_html_737f7932ce2722fe.png||height="192" width="606"]]
71
72 __Screenshot: updating the text field with information related to the selected BO report__
73
74 = Getting a specific BusinessObjects report instance =
75
76 A dropdown list is available to give you the possibility to choose a specific instance for a given report.
77
78 Here are the available choices for picking an instance:
79
80 * Report: it is the original document (without any update via a scheduler)
81 * Last successful: it is the last successful report instance after the last schedule
82 * Last: it is the last successful or not report instance after the last schedule
83 * Penultimate: it is the penultimate report instance.
84
85 [[image:bo_connector_en_html_9d67f10804322beb.png||height="200" width="608"]]
86
87 __Screenshot: dropdown list displaying the options for picking a specific report instance__
88
89
90 By default, it is the report instance that is chosen.
91
92 (% class="box infomessage" %)
93 (((
94 __**Note**__: Of course, the dropdown list will only display the possible choices for the report (i.e. if the report only has one instance, the option “penultimate” will not appear). And as previously mentioned, if the report has no instance at all, the default choice (report instance) is chosen.
95 )))
96
97 = Handling a BusinessObjects report’s prompts =
98
99 Some BO reports contains prompts imposed by the Universe or prompts created by a user. You have the possibility via Digdash to fill these prompts in a dedicated interface to filter your BO query with the button called “**Prompt values**”.
100
101 [[image:bo_connector_en_html_d06ddc7dc417d7df.png||height="190" width="608"]]
102
103 __Screenshot: Button to access the prompts handler__
104
105
106 [[image:bo_connector_en_html_69a0a2234ae5dc56.png||height="210" width="494"]]
107
108
109 __Screenshot: UI to handle prompt values for a BO report__
110
111 The interface suggests you to enter for each prompt: its name (or label) and its associated value.
112
113 You can add as many name-value associations as needed.
114
115 (% class="box infomessage" %)
116 (((
117 __**Note **__: a prompt can be associated with a list of values. Use commas to separate each value.
118 Reload the report to apply these filters.
119 )))
120
121 = List of all BusinessObjects reports (Webi and DesktopIntelligence) =
122
123 The UI comes with a button that will allow you to see all the BO reports on your BO server.
124
125
126 [[image:bo_connector_en_html_5468454bbb3a1ea9.png||height="188" width="598"]]
127
128 __Screenshot: Button to display all reports on the BO server__
129
130
131 [[image:bo_connector_en_html_4f29806c0fa9ca89.png||height="332" width="606"]]
132
133 __Screenshot: the dialog displays all the WebI and DesktopIntelligence reports on the BO server__
134
135
136 The dialog will display all the BO reports with, for each report:
137
138 * its ID,
139 * its name,
140 * its number of instances,
141 * its type and its path on the BO server.
142
143 Besides, the dialog comes with a search bar that will allow you to search for a report, faster.
144
145 (% class="box infomessage" %)
146 (((
147 __**Note**__: the filtering works for the report ID as well as for its name, its number of instances, its type and its path on the BO server.
148 )))
149
150 By default, the interface lists the first 10,000 BO reports of the server. You have the possibility to increase or reduce the number of reports to display with the option “**Choose the number of reports to display in the lis**t”.*
151
152 [[image:bo_connector_en_html_65158ceaba96a20b.png||height="50" width="478"]]
153 \\
154
155 (% class="box infomessage" %)
156 (((
157 __**Note**__: when the option is not selected, the number of report to display comes back to 10,000;
158 )))
159
160 The unique selection of a report will automatically update the fields related to the selected BO report.
161
162 = Importing the certificate for a secured connection =
163
164 If you deal with a secured connection (https), you need proceed as follows:
165
166
167 First, you need to import the Digdash certificate so that Digdash can access the application:
168
169 * **With Windows**
170
171 * Launch the command prompt and go to:(((
172 C:\...\install_dd_20XX\jdk\jre\bin
173 )))
174 * Execute the command:(((
175 keytool -import -trustcacerts -file certificat.crt -alias CA_DIGDASH -keystore ..\lib\security\cacerts
176 )))
177 * Enter a password (changeit by default)
178 * Answer “yes” to the question
179
180 * **With Linux**
181
182 * Directly enter the command:(((
183 keytool -import -trustcacerts -file certificat.crt -alias CA_DIGDASH -keystore $JAVA_HOME/jre/lib/security/cacerts
184 )))
185 * Enter a password (changeit by default)
186 * Answer “yes’ to the question
187
188 In order to check if the previous operation is successful:
189
190 * **With Windows**
191
192 * Launch the command prompt and go to:(((
193 C:\...\install_dd_20XX\jdk\jre\bin
194 )))
195 * Execute the command:(((
196 keytool -list -v -keystore ..\lib\security\cacerts
197 )))
198
199 * **With Linux**
200
201 * Directly enter the command:(((
202 keytool -list -v -keystore $JAVA_HOME/jre/lib/security/cacerts
203 )))
204
205