DSXchange

IS8 is installed here in a 4-tier configuration: windows clients plus the domain, engine & Oracle repository all on 3 separate AIX hosts. Per the vendor, a full suite backup involves shutting everything down, doing filesystem and repository RDBMS backups, then restarting everything. The commands...

IBM confirmed that it should workable to just delete the admin.exe from the analyst's workstation after the IS8 client has been installed.

We have also requested and enhancement to the install utility to deselect the admin client at installation.

My id is definitely credential to just me. I'll report it to IBM and seen what their answer is. At this point, there truly is no way to block a DataStage developer from editting the DSParams information in 8x: We are still waiting on a patch to choose to not install it and we don't know if it can ju...

I just now tried it -- owner is dsadm, I am in the group but permissions ares set to 740, so it seemed that I should not be able to edit env vars in DSAdmin client. However, I was able to add a new one and the DSParams file was definitely updated as evidenced by an updated timestamp. We are in the m...

Thanks for all the input. Update: We have requested and are awaiting a patch from IBM to allow us to choose to not install the admin client. I now realize what I should have realized long ago -- the DSParams file needs to be locked down. Is it reasonable to have dsadm own the UNIX directory and file...

I agree that it could be helpful for developers to be able to view information in the Administrator client. Unfortuneately, that also opens the door for them to edit the values as they see fit. We all know that as application developers, we often are under time crunches that push us to do whatever i...

How do others handle access to the DataStage Administrator client? We have isolated its usage to only the tool administrators -- developers did not even receive the 7x admin client when requesting DataStage. I have not yet been able to find a way to block analysts from accessing the 8x admin client,...

IBM engineer replied with location in pdf of the essential information to include port number when logging to Designer or Administrator -- see "Migrating to IBM Information Server Version 8" page 14 ["Multiple server method (UNIX and Linux only)"] and page 20 ["Connecting to...

FYI: 8.0.1 install guide directs you to do a shared memory test via the "shmtest" utility that comes with the product. However, that command failed when we ran it -- failed both as dsadm and as root. IBM's response -- that command is only for Solaris & not for AIX. dsenv file has an LD...

IBM engineer asked if we had used the default port of 31538 when we installed on the engine host. We did not -- we are doing an in place upgrade and that port is already in use by our 7.5.2 installation. At that time, another IBM engineer suggested we use port 31801, which we did. When the current I...

Yes, DataStage is up and running, and so is the ASBagent on the same box. The WAS is up on the domain box, too. (We installed the respository, domain and engine on 3 separate AIX boxes.) We've checked file permissions -- they look the same as 7.5.2 does. We know that the UNIX userid used for the cre...

I can not open the 8.0.1 Administrator Client nor the Designer Client. Administrator Client error: Failed to connect to DataStage server: AURIGA, project: UV (The connection was refused or the RPC daemon is not running (81016)) Designer Client error: Failed to connect to DataStage server: AURIGA, pr...