Data Integrator Components Deployment

[Former Member]

Hi all

We are going to deploy BO Data Integrator XI for the first time. We have 3 environments 'Development', 'UAT' and 'Production'. I was asked to research what is the best way to deploy the DI components on Windows platform. I searched a lot but couldn't find any resource! Honestly I'm frustrated by searching this site and google without any good result

Our server is Windows server 2003 and the database management server is MS SQL Server 2005. Could you please let me know what is the best way to deploy the DI components across the network? We will use batch jobs, so just need DI designer, DI Job server, DI Engine , DI repository and DI Meta data applications and DI administration.

What would be the best way to deploy DI components and also best way to deploy 3 central repositories for Development, UAT and Production environment? Every on one server or one server for each and how about the repositories? Should be on the same machine where these components are installed, or ....?

Any help is greatly appreciated!

[dennis_scoville4 · Accepted solution]

There are several install and administrator guide documents on the SAP Help Portal:

1) Go to the [SAP Help Portal|http://help.sap.com/]

2) From there, on the top navigation bar select SAP Business Objects > All Products

3) Choose the product from the dropdown. Data Integrator is the name of the tool up to version 11.x and was merged with Data Quality as of version 12, more commonly known as Data Services XI 3.x

4) Choose the version from the dropdown. Data Integrator 11.5.x is shown as Business Objects XI Release 2 (XI R2) and 11.7.x is shown as Business Objects XI Release 2 Accelerated. The DataServices versions are Business Objects XI 3.0, Business Objects XI 3.1 and SAP Business Objects XI 3.2.

[Former Member · Accepted solution]

Thanks so much for your quick response, but unfortunately I couldn't find there any manual about DI components deployment. If you know any specific document about deployment DI on Dev to Production environments, I would be grateful if you could send its link to me.

Any way the SAP Help which you referred me to, was a good resource for other Business Objects stuff. Thanks.

[dennis_scoville4 · Accepted solution]

We're installing Data Services XI 3.1 components, so I went to the 'Data Services Installation Gudie for Windows'. A PDF is opened and if you expand Standard Installation, the following topics are listed and have installation procuedures in teh document for:

1) Selection of Repository

2) Job Server configuration

3) Access Server configuration

4) Metadata Integrator configuration

5) Selection of Web Application Server

Is that what you're looking for?

[Former Member · Accepted solution]

Thanks for your time. I think you refer to DI Technical manual. I have read that, but I need to know what the best approach is to deploy components and repositories.

Once again thanks and please if you come across something as best practices of DI deployment, please kindly send it to me

[Former Member · Accepted solution]

Data Integrator has a simple distributed architecture well documented in the technical manual. To understand the deployment best practices, let's break down the components into a few simple categories:

1) Server components

- Job server: for running batch jobs. DI engine is a process started by the Job server when you run a batch job so it's NOT a deployable component.

- Access server: for running real time jobs.

- Web Administrator and Metadata reports: for DI administration and lineage analysis. It's web applications which can be deployed either on the Tomcat web server bundled with DI or a different web server in your company.

2) Client components

- Designer: this is the development tool for creating all batch/real time jobs.

3) Repositories:

- Local repository: this is a database instance that stores all DI built-in metadata and custom code. There should be one per developer in the DEV and QA, and only one in the Production.

- Central repository: you don't need 3 central repos. Centrol repo is nothing but a version control tool for DI. It keeps the versioning history for all code checked into it. One is good enough, and you may need another one at most (I always advise my customers to use just one central repo to keep it simple).

So let's start with a simple basic deployment. You can deploy all components (a standard installation) on the 3 Windows 2003 servers: DEV, UAT, and PROD. Then you need to install only the client component (Designer) on each developer's workstation. On the DEV database server, you can create one local repo for each developer (for example, DEV_John), and a central repo for source control. On the UAT database server, you can create one local repo for each developer. On the Prod database server, just create one local repo. Of course, after these steps, you need to follow the technical manual to configure the job server and local repositories to talk to each other and other things.

This should give you a good functioning environment to start your project.

-Larry

[Former Member · Accepted solution]

"On the UAT database server, you can create one local repo for each developer"

I actually meant "On the UAT database server, you can create one local repo for each TESTER".

-Larry

[Former Member · Accepted solution]

Thanks so much Larry for your comprehensive solution. Just one question remains and it is "Is it possible to install just one DI administration component and share it between three environments? I mean define the three level of security level to have access to just one repository from the DI administration?"

We would rather to have just one instance of DI administration, however from security point of view, we don't want the DEV administrator has access to admin side of PROD or UAT. No job or user in each area can be touched by other area administrators.

Is it possible to set the security level, so the administrator from each environment, can have just access to the valid objects and users in the relevant area?

Thank you for your assistance in advance.

[Former Member · Accepted solution]

You're welcome Tootia. The short answer is no, that's not possible. DI's security is not that sophisticated. There are only a few roles available: admin, monitor, user, etc. If someone is an administrator, he can see everything and do anything. From DI's point of view, it doesn't really care where a repo resides - DEV, UAT or PROD. So unfortunately you have to install the admin components in each of the 3 enviornments.

-Larry

[Former Member · Accepted solution]

Thanks so much Larry. You saved us from trying and errors!

[adil_nil · Accepted solution]

Hi Larry

I wonder if you are still around to answer my question.

I successfully installed DI on AIX 5.3, both DI Job server and web server are configured and I can login to the Administrator.

Now the requirement is to install DI web Administrator component (only) on the web tier.

The Web Tier is a Linux server used as web/application server (Apache/Tomcat).

Apache is already installed but not Tomcat

Can I install the web Administrator as a separate component on the Linux server.

If the answer is YES.

Could you please let me know the steps to install DI web Administrator on a separate server(Linux) and configure it to communicate with Apache the Job server on the AIX box.

I appreciate your help.

Thanks

[Private_Member_662719 · Accepted solution]

Do you have documentation on this and if you have and can you send it to me, I will appreciate your help!!