JCAPS Deployment Architecture

I'm struggling to understand the way JCAPS handles deployment. I
have managed to build an EAR file using the eDesigner but it
will not let me deploy it to my IS.
The funny thing is if I go into the Enterprise Manager and use
the deployment page to deploy the EAR file that eDesigner built
that works fine.
The error I get in eDesigner is;

JavaCAPS.[19 Jan 2007 10:46:59,971] ERROR
(com.stc.codegen.driver.module.DeploymentDeployActi on) - Illegal
operation for a disconnected DeploymentManager:
java.io.IOException: Unable to connect to admin-server. Please
check if the server is up and running and that the host and port
provided are correct.
java.lang.IllegalStateException: Illegal operation for a
disconnected DeploymentManager: java.io.IOException: Unable to
connect to admin-server. Please check if the server is up and
running and that the host and port provided are correct.
at
com.sun.enterprise.deployapi.SunDeploymentManager. getTargets(Sun
DeploymentManager.java:145)
at
com.stc.deployment.framework.impl.DefaultApplicati onServerManage
r.getAvailableModules(DefaultApplicationServer Manager.java:242)
at
com.stc.deployment.framework.impl.DefaultApplicati onServerManage
r.getAvailableModulesForDistribute(DefaultAppl icationServerManage
r.java:276)
at
com.stc.codegen.driver.module.DeploymentDeployActi on$DeploymentP
rogressListener.run(DeploymentDeployAction.jav a:1657)
at java.lang.Thread.run(Thread.java:534)

It looks like to me that eDesigner can't connect to my IS which
is running, I'm confused as to the relationship between the IS
and the Logical Components in eDesigner. In 5.0.5 is was
straightforward you had a properties file on your server and you
defined the environment the LH belong to and the LH name, you
then mimicked that your logical structure in the eDesigner and
it worked fine.
JCAPS doesn't appear to work like this so I'm at a loss to how
the eDesigner can find the IS?

I always use edesigner to build the EAR and then the Enterprise Manager
to deploy it, I was informed on a JavaCAPS coarse that you shouldn't
really use the deploy button in the edesigner (the instructor said that
in his opinion that the button shouldn't even be there). I believe this
is due to the fact that the runtime environment has now been decoupled
from the designer and registry, this makes it easier for the registry
and designer to support more runtime environments as they are only used
to create the J2EE compliant EAR file that you can then deploy to any of
the JavaCAPS approved application servers.

in JCAPS 5.1 the Environment definitions (and so the Logicalhost and IS) have no longer 1 to 1 relationships to the real Integration(Application)Server instances. It is now only a logical definition and collection of your configuration parameters.
That gives you the flexibility to define specific ENVs for each project/deployment.

You can deploy all these different ENV configs to the sam IS/AS.

That also means, when working with eInsight, that every deployment (EAR file) contains its own BPEL engine. So you may adjust the BPEL engine different for separate tasks.

I assume, you haven't set the IS properties correctly. If you set the hostname:port pointing to your physical IS/AS instance, the deployment from eDesigner should work.

Couple things on that.
Firstly, having a deploy button in edesigner is a convineince and
it works the way designed. The reason you are getting the error,
I think anyways, is because your environment configuration of
the Integration server and/jms server is not correct. Check to
make sure the URL is correcly configured for the IS.

The reason it was working when you manually deploy is that it is
using the runtime configuration automatically as the container
is already running and available. It is simmilar to any other
war file/ear file you deploy in the other web/application
servers like tomcat/weblogic etc.

Could you just elaborate on which IS properties need changing I
noticed that the Integration Server URL was pointing to
stcis://localhost:18000 which wouldn't be correct as the IS
isn't on the same machine as the eDesigner, so I've changed it
now to stcis://<hostname>:18000 but it still gives the same
error in the eDesigner after saving my changes.
Is there somewhere else I need to specify the hostname and port?

Hi Folks,
I am working on Seebeyond since 4.1.2, and currently working with ICAN 5.0.5. havent been to any training in JCAPS.

1. Is there any doc which specifies all the differences between ICAN and JCAPS, like 'Domain', and the Environment to IS relationship like mentioned below?

If not, just curiosity...
in ICAN, the relation between all entities is,
Project ---> Can have multiple DPs -----> Each DP pointing to 1 ENV. ----> And each Env can have 1 LH -----> And each LH can have multiple IS/JMS mgrs.

- the hostname you entered can be DNS-resolved from your eDesigner workstation (you may try IP address directly)
- the port number is correct (depends on your IS domain setup)
- you have entered the correct user (Administrator) and password

Now when you say, you have the domain running, how are you verifying it??

Are you able to access the domain server using the url directly??

SO let us say you started the domain on default port, 18000.
if you use http://<your server name>:18000, are you able to get the login page??

Are you using the correct user Id and password??

Also, by default the password is null, you have to enter password twice for the integration server in the edesigner. Did you check this??

If all these are correct, please let me know your steps . Here is how I would do.

1. Start the domain.
2. Access the domain via url.
3. Make sure you can add the server to the emanager.
4. Make sure you can access the is and JMS via emanager.
6. This should let you then configure and deploy projects on to it from designer.

1. Start the domain. DONE
2. Access the domain via url. DONE
3. Make sure you can add the server to the emanager. DONE
4. Make sure you can access the is and JMS via emanager. DONE
6. This should let you then configure and deploy projects on to it from designer. NOT DONE

I can do 4 of those steps the fifth one still won't work, what I really need to know is the steps to configure the edesigner end (step up of the logical components in the edesigner environment), I guess that is where the problem is.

In your edesigner, On the environment tab, you click on the
properties of the IS and modify the url to point to the domain
url. But here the url does not start with http but rather start
with stcis. For example, if the domain is running on host say
serverA at port 180000
Here is the url,

stcis://swerverA:18000

You do not have to touch the JMS configuration, if you did, put
it back to default and try it again. JMS server automatically
takes the uril during deplopyment time from the IS parameters if
it is not configured. As long as you are planing to use the JMS
server under that IS, you dont have to touch it.

Hope that helps. If you can post the configuration you have we
might be able to help better.