1

Has anyone out there in SO land had to deal with this...when you go to build a new deployment profile in JCAPS, you have quite a few little boxes that you have to minimize before you can do the actual mapping (black boxes added to hide company specific info): horrible little boxes

We've tried autohotkey and are looking into Sikuli - does anyone know of a good way to get around this silly UI design flaw?

Glorfindel
  • 21,988
  • 13
  • 81
  • 109
javamonkey79
  • 17,443
  • 36
  • 114
  • 172
  • I don't really understand what's your problem here, as far as I remember (I don't use JCAPS anymore since August), you've got to prepare a 'deployement profile' when you map 'logical resources' to 'physical resources', so if you've got alot of physical resources in your 'environment', you'll have alot of 'little boxes of hell' :) ... did I get something wrong? – Kevin Jan 08 '11 at 17:10
  • @Kevin - nope you, got it right. In our case we have 100's of physical\logical resources - hence what you see here. I'll be posting a bounty on this eventually. Thanks for looking. – javamonkey79 Jan 08 '11 at 19:05
  • I'm not at all a JCAPS expert, but I would think that you've got too many resources in your environment, maybe you should split it? – Kevin Jan 09 '11 at 15:40
  • That's an interesting idea - I don't know that we've considered splitting the logical environments. We have prod and test now, but we could feasibly have prod1, prod2, prod3, etc. I'll have to talk it over with my team. If this works out for us then you'll have to post as an answer and I'll accept. Thanks! – javamonkey79 Jan 09 '11 at 22:10

3 Answers3

0

I've found that if you click on the "third" button in the deployment wizard that your logical hosts appear on the lower right. Other than that, the latest EAs you created are on the upper left.

Phil.Ng
  • 116
  • 8
0

You can build multiple environments that point to the same logical host. Just separate the resources into logical groups to make them more manageable.

Richard
  • 11
  • 2
0

I wrote a Netbeans plugin to take care of this. I can't publish the full source, but here is the main idea.

javamonkey79
  • 17,443
  • 36
  • 114
  • 172