datasource related queries

Hi,

1)I don't want to hardcode my datasource properties.So,I am using connection profile file.When I am publishing my report on iserver.Where should i place my connection profile file so as it is also visible on iserver?

2)And if in future if I want to edit it how should i make tha changes?

3)I also read about connection configuration file ,if we uplaod a file having following details e.g

<Config>
<Runtime>
<ConnectOptions Type="org.eclipse.birt.report.data.oda.jdbc_Customers">
<Property PropName="odaDriverClass">
com.mysql.jdbc.Driver
</Property>
<Property PropName="odaURL">
jdbc:mysql://192.168.218.226:3306/ClassicModels
</Property>
<Property PropName="odaUser">operator</Property>
<Property PropName="odaPassword">cm9vdA==</Property>
</ConnectOptions>
</Runtime>
</Config>

and upload it through cong mgmt console.Will it be updated for all the reports in iserver.How will we edit this file in future?

4)Which approach is best to use the connection configuration file or connection profile ?

Please help with these questions

Shilpa

Find more posts tagged with

Comments

Shilpa

Hi,

I got the help from this forum from my previous questions.
I need help in placing the connection profile at right place.Plz smbdy help this time also.

Shilpa

Linda Chan

I will first respond to your second question. The rest would need a bit more time to look into.

>> 2)And if in future if I want to edit it how should i make the changes (to connection profile)?

To change the content of a connection profile instance, you can use the Data Source Explorer view if you are on the Eclipse workbench. User doc can be found in Eclipse IDE's Help-> Help Contents; look under "Data Tools Platform User Documentation", "Creating a Connection Profile".

Or you can use the DTP console application tool to edit the property values in an exported connection profile store file, even when the file is encrypted. The tool also comes in handy when editing a profile store file directly on the deployed backend server.
The console tool is also documented under "Console Editor Application" in the DTP User Doc mentioned above.

Linda

Linda Chan

Here are what I found out for the rest of your questions.

>> 1) When I am publishing my report on iserver.Where should i place my connection profile file so as it is also visible on iserver?

There is no specific recommended location for where a connection profile store file should reside on iServer. It can be anywhere, as long as it is visible to the iServer process.
If the iServer has clustered setup, it is recommended to create a shared physical location that is mapped/mounted in a way such that the path name is exactly the same from each iServer machine.

>> 3) if we upload a connection configuration file, through cong mgmt console.Will it be updated for all the reports in iserver.How will we edit this file in future?

There is no functionality in Management Console to upload this file. You can only specify the location of the connection configuration file as a iServer configuration setting. This can be set from Management Console for each iServer in the cluster.
To edit the file, just use any text editor to directly edit its content.

>> 4)Which approach is best to use the connection configuration file or connection profile ?

It depends on your needs, and if you use other types of Actuate reporting products, besides the BIRT-based ones.
The connection config file is usable by iServer for all the supported Actuate reporting products.
On the other hand, the connection profile solution is only applicable for BIRT-based report designs. However, its pros are that connection profiles are 1) easily editable by various UI tools (as described in my previous response), and 2) supports basic encryption of the file content.

Hope that helps.