Access BMC Developer Network RSS feed for easy use. Now users can see the top topics on the BMCDN Remedy community and go there directly.
Have fun answering all the questions.
We have restored the VM (Midtier, AR and database) on same machines(windows server 2008) on which they were installed earlier. Hence the hostnames are same.
Now after I have made the services up, there is an issue of authentication.
When I try to login to user tool with hardcoded password(done from DB level in user and user cache form), I am getting authentication failed. LDAP bind user password also has been changed but as of now it should atleast authenticate using user form.
There is JSS SSO enabled on the midter, but I am getting the error from User Tool.
Also when I try to create a tempadmin user via arcache utility, I am getting “Cannot establish network connection to AR System server localhost”RPC bindfailure RPC:Unable to receive”. However I am able to telnet the database from AR Server.
The host file of windows is also having entry of AR Server.
Could you please help me resolve it.
Is it possible to trigger smart reporting from workflow?
I.e. set some parametern, run it and possible email it to someone?
To create less confusion, it would be nice if downloaded patches had filenames that makes it easy to distinguish what it is.
Of less importance, but it would also be nice if the same would happen to the tree structure of the contents:
Our environment runs on Linux SUSE. We are currently on 8.1 SP2 and want to upgrade to 9.0 however we cannot for BMC Remedy Action Request System 9.0 no longer supports Linux SUSE. Need to get this added ASAP.
So I’m looking at leveraging some of the new functionality in 9.x and one of the things we are struggling with is how things move to production.
Naturally I was excited by learning of Deployment Management, I had already started work on something very similar using versioning, git and the driver tool, so I am kind of glad this came along (one less thing to maintain).
From what I’ve learned so far it looks very nice – I think some in our team will love the SRM functionality!
The one thing I really dislike is the zip file. I’d much prefer the data was transferred from dev to test (and eventually to prod) automatically using, I don’t know, Atrium Integrator or just workflow? I’d much prefer to have a menu Item saying “Promote to test”/”Promote to production”, well at least the option.
A minor issue is dealing with environment specific data like (URLs). It would be nice to have some sort of action to handle issues like that (like in an Atrium Integrator transformation).
Is anyone else using this yet? What are your experiences?
We are in process on Making a new 9.1 ARS+CMDB+ITSM+SRM+SLM setup in 4 server Server Group. Ideal way is to create server group by running installers on all 4 servers.
This takes time for all 4 servers.
Os will be – SUSE Linux
DB- Oracle 12 c
Remedy – 9.1 Suite
We were thinking of Running Installer on first Server and then Second server own wards us VM cloning for Remedy ARS Servers. Remove the references from Cloned Servers and then try to make ARS service up in second server and so on…………………….
My Queries are
(1) has anyone tried this method for making a server group in 9.1?
(2) Is this approach is reliable and robust ?
(3) Since in 9.1 Conf entries are created in DB too- So after cloning how make these conf entries in DB for 2,3 and 4 th servers if we go with Cloning approach? or when second server will be up DB entries will automatically created from Ar.Conf file.
Folks your input please – Purpose here is to explore this possibility and save some time to make 4 server- Server Group in quick time.
Is it possible to change the user password through the Remedy API (preferably Java) ?