Error using wldeploy in unix environment

I am trying to use wldeploy ant task to deploy and undeploy applications from my server in a unix environment, and keep getting errors there, and not locally on a XP development workstation. Below are my buildfile and the error that I am getting. Anyone have any ideas as to what may be wrong?
build.xml
<target name="undeploy" description="Undeploys app">
<wldeploy user="${user}" password="${password}"
adminurl="${adminurl}" remote="true"
     action="stop" name="${appname}" debug="true"
verbose="true"/>
</target>
And here is the error:
[wldeploy] weblogic.Deployer -debug -remote -verbose -noexit -name ${appname} -adminurl iiop://${host}:${port} -user ${user} -password ${password} -stop
[wldeploy] weblogic.Deployer invoked with options: -debug -remote -verbose -noexit -name broker-co
ntact.ear -adminurl iiop://${host}:${port} -user ${user} -stop
[wldeploy] [WebLogicDeploymentManagerImpl.<init>():103] : Constructing DeploymentManager for J2EE v
ersion V1_4 deployments
[wldeploy] [WebLogicDeploymentManagerImpl.getNewConnection():146] : Connecting to admin server at a
lice.healthpartners.com:8001, as user system
[wldeploy] [ServerConnectionImpl.getEnvironment():288] : setting environment
[wldeploy] [Debug.say():43] : getting context using iiop://alice.healthpartners.com:8001
[wldeploy] [Debug.say():43] : Connecting to MBeanServer at service:jmx:iiop://${host}:${port}/jndi/weblogic.management.mbeanservers.domainruntime
[wldeploy] java.io.IOException
[wldeploy] at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProvide
rBase.java:135)
[wldeploy] at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProvid
erBase.java:79)
[wldeploy] at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.j
ava:341)
[wldeploy] at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:262)
[wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(Serve
rConnectionImpl.java:240)
[wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServerForTyp
e(ServerConnectionImpl.java:191)
[wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectio
nImpl.java:147)
[wldeploy] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(Web
LogicDeploymentManagerImpl.java:148)
[wldeploy] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeplo
ymentManagerImpl.java:118)
[wldeploy] at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentMan
ager(DeploymentFactoryImpl.java:84)
[wldeploy] at weblogic.deploy.api.tools.SessionHelper.getDeploymentManager(SessionHelper.java:4
32)
[wldeploy] at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:302
[wldeploy] at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:137)
[wldeploy] at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:158)
[wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:115)
[wldeploy] at weblogic.Deployer.run(Deployer.java:70)
[wldeploy] at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
[wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java
:43)
[wldeploy] at java.lang.reflect.Method.invoke(Method.java:615)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
[wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
[wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
[wldeploy] at org.apache.tools.ant.Task.perform(Task.java:364)
[wldeploy] at org.apache.tools.ant.Target.execute(Target.java:341)
[wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:369)
[wldeploy] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1216)
[wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1185)
[wldeploy] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:4
0)
[wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1068)
[wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:668)
[wldeploy] at org.apache.tools.ant.Main.startAnt(Main.java:187)
[wldeploy] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:246)
[wldeploy] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:67)
[wldeploy] Caused by: javax.naming.CommunicationException [Root exception is java.rmi.ConnectIOException: error during JRMP connection establishment; nested exception is:
[wldeploy] java.io.EOFException]
[wldeploy] at weblogic.jrmp.Context.lookup(Context.java:189)
[wldeploy] at weblogic.jrmp.Context.lookup(Context.java:195)
[wldeploy] at javax.naming.InitialContext.lookup(InitialContext.java:363)
[wldeploy] at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProvide
rBase.java:126)
[wldeploy] ... 35 more
[wldeploy] Caused by: java.rmi.ConnectIOException: error during JRMP connection establishment; nest
ed exception is:
[wldeploy] java.io.EOFException
[wldeploy] at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:293)
[wldeploy] at sun.rmi.transport.tcp.TCPChannel.newConnection(TCPChannel.java:190)
[wldeploy] at sun.rmi.server.UnicastRef.newCall(UnicastRef.java:321)
[wldeploy] at weblogic.jrmp.BaseRemoteRef.invoke(BaseRemoteRef.java:221)
[wldeploy] at weblogic.jrmp.RegistryImpl_Stub.lookup(Unknown Source)
[wldeploy] at weblogic.jrmp.Context.lookup(Context.java:185)
[wldeploy] ... 38 more
[wldeploy] Caused by: java.io.EOFException
[wldeploy] at java.io.DataInputStream.readByte(DataInputStream.java:269)
[wldeploy] at sun.rmi.transport.tcp.TCPChannel.createConnection(TCPChannel.java:234)
[wldeploy] ... 43 more
[wldeploy] [Debug.say():43] : Closing DM connection
[wldeploy] [Debug.say():43] : Unregistered all listeners
[wldeploy] weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 'iiop://${host}:${port}': null. Ensure the url represents a running admin server and that the crede
ntials are correct. If using http protocol, tunneling must be enabled on the admin server.
Thanks.
Scott

Hi Richard,
I had the same issue using Eclipse. I just tried to run the
ant script outside of Eclipse and it worked fine.
This is an Eclipse-Ant Class Loader issue.
In order to make it work in Eclipse, You have to :
1. Open the External Tool Run Configuration.
2. Select your Ant script.
3. Select JRE Tab.
4. In Runtime JRE section, choose Seperate JRE.
Hope this helps !
Eric

Similar Messages

  • Crazy Errors using B1 Dev't Environment Project

    I had created an Add-On using the B1 Dev't Environment code wizard.  On my machine, it works great.  I built the setup program also using the B1 Dev't Environment.  That too worked well.
    I tried installing the add-on onto a different PC, but keep getting an unhandled error from the common language runtime debugging services.  It just says "Application has generated an error that cannot be handled".  But I have error handling all throughtout the code.
    I then built a simple "Hello World" app with only one event.  It exhibits the same behaviour.
    Has anyone seen anything like this?
    I've built apps the "old school" way, but I really like the Dev't environment.
    Hopefully, there's a work-around or a fix for this.
    Thanks!

    Hi Curtis,
    I have been investigating the problem you found to run addons generated with B1DE CodeGenerator wizard when Microsoft Visual Studio .NET is not installed in the client machine.
    I have found the problem and fixed it, I'm doing some testing on it and it should be released very soon on SDN as a new B1DE version 1.1.
    The problem was due to the B1Wizard.dll referenced in your addons, this dll contains all wizard functionality and uses .NET dlls that are not included in the .NET Framework. In the next B1DE release addons will reference a B1WizardBase.dll that only contains the classes needed by your addons.
    I will add some information in this main weblog as soon as the new B1DE release is published into SDN.
    Regards
    Trinidad.

  • Monitor process on windows or unix environment

    Could we monitor a process using windows or unix environment using OEM?

    Look at the Program Resource Utilization, Program's Max/Min Process Count metrics, which are documented here, to see if they met your need.
    http://docs.oracle.com/cd/E11857_01/em.111/e17018/host.htm#BABIBAHD
    Regards,
    - Loc

  • Using wldeploy from NT to deploy over Unix

    WLS 8.1 sp2 / solaris
    I 'm using wldeploy ant task.
    quite good for undeploying, if I put the weblogic.jar in the classpath before
    calling ant.
    But I fail using deploy because my source file path is always converted from unix
    "/" to windows "\". So it always fails with a "java.io.FileNotFoundException:
    No such path".
    Thanks for any clue.
    My goal it to undeploy/redeploy from my NT workstation to my Unix WLS server.

    Rob/Philippe,
    It is a bug and a case has already been created.
    -shailesh
    Rob Woollen <[email protected]> wrote:
    Hmm, that sounds like a bug. Can you show me the stack trace or error
    message it emits?
    -- Rob
    Philippe MARSOLLIER wrote:
    Rob Woollen <[email protected]> wrote:
    Is the file that you are deploying on the local windows machine or
    on
    the remote machine?
    By default Deployer treats any path to be on the local machine. If
    you
    pass -remote, it uses the server's file system to resolve the path.
    -- RobYes, I use -remote but it convert / (unix separator) in \ (windowsseparator)
    >

  • How do I use a UNIX environment variable for the path of a file name

    We are running Forms 6i over the web. The forms server runs on a UNIX (HP-UX) machine.
    I want to read the contents of a file, which is simple enough, using the TEXT_IO package. However, I want to reference a UNIX environment variable that specifies the file path i.e
    PROCEDURE get_file IS
    in_file Text_IO.File_Type;
    linebuf VARCHAR2(1800);
    filename VARCHAR2(200);
    BEGIN
    filename:= '$LOG_DIR/RCAS181.log';
    in_file := Text_IO.Fopen(filename, 'r');
    .....other stuff
    Notice the filename string references my unix env variable '$LOG_DIR'. However, this doesnt work. If I put the full pathname it works fine.
    Any suggestions ?

    Have a look at TOOL_ENV.GETVAR()

  • Error Registering 11g SOA Composite in Unix environment

    Hi All,
    We are trying to register a SOA Approval Composite with OIM 11.1.1.3 in the Unix environement . The SOA Process is getting successfully deployed , but when we are registering it , its throwing error as : "The task definition at default/ProvisioningApprovalFlow!1.0*soa_***************/ApprovalTask could not be read".
    However, same workflow is getting successfully registered and executed in Windows environment. Any suggestion what could go wrong here. I am providing here the error details . Any help is heartly appreciated.
    Exception in thread "main" oracle.iam.platform.workflowservice.exception.IAMWorkflowException: Tasklist mapping failed for workflowdefinition:
    default/ProvisioningApprovalFlow!1.0 due to Invalid task definition.Ni
    [java] The task definition at default/ProvisioningApprovalFlow!1.0*soa_7abcd53a-69ca-4c93-909b-88e59015e026/ApprovalTask could not be read. The task definition is
    associated with workflow default/ProvisioningApprovalFlow!1.0*soa_7abcd53a-69ca-4c93-909b-88e59015e026/ApprovalTask.
    [java] Make sure that the task definition is available at the specified URL and that it is a valid XML document.
    [java]
    [java] at weblogic.rjvm.ResponseImpl.unmarshalReturn(ResponseImpl.java:234)
    [java] at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:348)
    [java] at weblogic.rmi.cluster.ClusterableRemoteRef.invoke(ClusterableRemoteRef.java:259)
    [java] at
    oracle.iam.platformservice.api.WorkflowRegistrationServiceEJB_f4otyb_WorkflowRegistrationServiceRemoteImpl_1033_WLStub.registerWorkFlowDefinitionx(Unknown
    Source)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java] at java.lang.reflect.Method.invoke(Method.java:597)
    [java] at weblogic.ejb.container.internal.RemoteBusinessIntfProxy.invoke(RemoteBusinessIntfProxy.java:84)
    [java] at $Proxy2.registerWorkFlowDefinitionx(Unknown Source)
    [java] at oracle.iam.platformservice.api.WorkflowRegistrationServiceDelegate.registerWorkFlowDefinition(Unknown Source)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java] at java.lang.reflect.Method.invoke(Method.java:597)
    [java] at Thor.API.Base.SecurityInvocationHandler$1.run(SecurityInvocationHandler.java:68)
    [java] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
    [java] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
    [java] at weblogic.security.Security.runAs(Security.java:41)
    [java] at Thor.API.Security.LoginHandler.weblogicLoginSession.runAs(weblogicLoginSession.java:52)
    [java] at Thor.API.Base.SecurityInvocationHandler.invoke(SecurityInvocationHandler.java:79)
    [java] at $Proxy3.registerWorkFlowDefinition(Unknown Source)
    [java] at oracle.iam.platformservice.workflowregclient.WorkflowRegistration.main(WorkflowRegistration.java:42)
    [java] Caused by: oracle.iam.platform.workflowservice.exception.IAMWorkflowException: Tasklist mapping failed for workflowdefinition:
    default/ProvisioningApprovalFlow!1.0 due to Invalid task definition.
    [java] The task definition at default/ProvisioningApprovalFlow!1.0*soa_7abcd53a-69ca-4c93-909b-88e59015e026/ApprovalTask could not be read. The task definition is
    associated with workflow default/ProvisioningApprovalFlow!1.0*soa_7abcd53a-69ca-4c93-909b-88e59015e026/ApprovalTask.
    [java] Make sure that the task definition is available at the specified URL and that it is a valid XML document.
    [java]
    [java] at oracle.iam.platform.workflowservice.impl.WorkflowRepositoryImpl.mapWorkflow(WorkflowRepositoryImpl.java:132)
    [java] at oracle.iam.platform.workflowservice.impl.WorkflowRepositoryImpl.registerWorkFlowDefinition(WorkflowRepositoryImpl.java:113)
    [java] at oracle.iam.platform.workflowservice.impl.WorkflowServiceImpl.registerWorkFlowDefinition(WorkflowServiceImpl.java:231)
    [java] at oracle.iam.platformservice.impl.WorkflowRegistrationServiceImpl.registerWorkFlowDefinition(WorkflowRegistrationServiceImpl.java:38)
    [java] at oracle.iam.platformservice.api.WorkflowRegistrationServiceEJB.registerWorkFlowDefinitionx(Unknown Source)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [java] at java.lang.reflect.Method.invoke(Method.java:597)
    [java] at com.bea.core.repackaged.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:310)
    [java] at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:182)
    [java] at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149)
    [java] at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
    [java] at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
    [java] at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    [java] at com.bea.core.repackaged.springframework.jee.spi.MethodInvocationVisitorImpl.visit(MethodInvocationVisitorImpl.java:37)
    [java] at weblogic.ejb.container.injection.EnvironmentInterceptorCallbackImpl.callback(EnvironmentInterceptorCallbackImpl.java:54)
    [java] at com.bea.core.repackaged.springframework.jee.spi.EnvironmentInterceptor.invoke(EnvironmentInterceptor.java:50)
    [java] at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    [java] at com.bea.core.repackaged.springframework.aop.interceptor.ExposeInvocationInterceptor.invoke(ExposeInvocationInterceptor.java:89)
    [java] at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    [java] at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.doProceed(DelegatingIntroductionInterceptor.java:131)
    [java] at com.bea.core.repackaged.springframework.aop.support.DelegatingIntroductionInterceptor.invoke(DelegatingIntroductionInterceptor.java:119)
    [java] at com.bea.core.repackaged.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171)
    [java] at com.bea.core.repackaged.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:204)
    [java] at $Proxy507.registerWorkFlowDefinitionx(Unknown Source)
    [java] at
    oracle.iam.platformservice.api.WorkflowRegistrationServiceEJB_f4otyb_WorkflowRegistrationServiceRemoteImpl.registerWorkFlowDefinitionx(WorkflowRegistrationServiceEJ
    B_f4otyb_WorkflowRegistrationServiceRemoteImpl.java:193)
    [java] at oracle.iam.platformservice.api.WorkflowRegistrationServiceEJB_f4otyb_WorkflowRegistrationServiceRemoteImpl_WLSkel.invoke(Unknown Source)
    [java] at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:589)
    [java] at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:230)
    [java] at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:477)
    [java] at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
    [java] at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
    [java] at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:473)
    [java] at weblogic.rmi.internal.wls.WLSExecuteRequest.run(WLSExecuteRequest.java:118)
    [java] at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
    [java] at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
    Thanks
    Swati Pandey

    Has any one faced similar issue ?

  • JQuery.js not working in UNIX environment

    Hi All,
    My development environment is Linux with Apache and we are using Coldfusion 9.
    We have developed some part of our code using jQuery.
    This is perfectly working in our DEV environment.
    We shipped the same code to the Production Environment. Which is Coldfusion 5 and Unix Environment with Apache Server.
    The problem is the parameter passing to jQuery is always null.
    Is jQuery will not work in Coldfusion 5?
    Your help is needed.
    Thanks in advance!

    1. CF versions 9 and 5 and radically different.  I wouldn't expect code written for CF9 to run on CF5.
    2. CF runs on the server, jQuery runs in the brower, the version of CF on your server shouldn't be relavent.  You should look for the problem in the HTML, Javascript, CSS, etc. in the browser.
    3. We cannot help diagnose your problem without seeing the code that is causing the problem and any error messages you receive.
    4. If this is a issue with jQuery on the browser you might consider posting a question to a jQuery specific forum.

  • How to compile form orginal file(*.fmb) in UNIX environment

    These days, i encounter a problem, i create a form application in Windows2000 or WindowsXP environment, then i compile this .fmb file to .fmx, then i transport this .fmx file to Unix environment which is our Application Server, the Oracle Application Server is in this Unix environment, i put this file in the directory which is directed in the Forms_Path variable, however, when i started to run this application by entering a valid url, the message shows that this fmx file is not runtime file, someone told me that i should recompile the orginal file under unix environment, so i transport the orginal file(.fmb) to unix environment, then i want to use the f90genm tool to compile the .fmb file, however, it shows that this command can not execute, it shows that can not open a lib file under:/project/.../../..,however, this directory does not exist at all, what case this error? i also use f90gen command, it shows: can not execute/finish creation, i want to know, how to use the two commands and what parameters i should set before using the commands? thanks

    If you are talking about forms 10g then here is the method
    1) run x windows interface on your machine
    2) login to linux server
    $ export DISPLAY=<IP address of machine>:0.0
    $ frmcmp.sh module_type=form module=myform.fmb userid=user/password@connectstring compile_all=yes
    Regards
    Anuj

  • Could not deploy my project in unix environment

    I am using windows for development environment, my code was deploying fine in windows environment. But when i tried to deploy in unix environment I got this error
    bpel_IRobo_Workflow1_1.0.jar failed to deploy.
    Error while loading process. The process domain encountered the following errors while loading the process "IRobo_Workflow1" (revision "1.0"): BPEL validation failed. BPEL source validation failed, the errors are: [Error ORABPEL-10902]: compilation failed [Description]: in "bpel.xml", XML parsing failed because "undefined part element. In WSDL at "file:/u01/app/oracle/product/AS10.1.3.3.0/bpel/domains/default/tmp/.bpel_IRobo_Workflow1_1.0_e580208857197172fe72bbfca5d9d8b6.tmp/workflow2.wsdl", message part element "{http://schemas.xmlsoap.org/ws/2003/03/addressing}RelatesTo" is not defined in any of the schemas. Please make sure the spelling of the element QName is correct and the WSDL import is complete. ". [Potential fix]: n/a. . . If you have installed a patch to the server, please check that the bpelcClasspath domain property includes the patch classes.
    Can any one knidly help. I have to fix this thing in a day so any help would be of great use thanks

    bpel.xml
    <?xml version = '1.0' encoding = 'UTF-8'?>
    <BPELSuitcase>
    <BPELProcess id="IRobo_Workflow1" src="IRobo_Workflow1.bpel">
    <partnerLinkBindings>
    <partnerLinkBinding name="client">
    <property name="wsdlLocation">IRobo_Workflow1.wsdl</property>
    </partnerLinkBinding>
    <partnerLinkBinding name="combtecbsnk03NetworkInstallationsService">
    <property name="wsdlLocation">combtecbsnk03NetworkInstallationsServiceRef.wsdl</property>
    </partnerLinkBinding>
    <partnerLinkBinding name="fr_pots_dj_schedule">
    <property name="wsdlLocation">fr_pots_dj_schedule.wsdl</property>
    <property name="retryInterval">60</property>
    </partnerLinkBinding>
    <partnerLinkBinding name="fr_staa_response">
    <property name="wsdlLocation">fr_staa_response.wsdl</property>
    <property name="retryInterval">60</property>
    </partnerLinkBinding>
    <partnerLinkBinding name="fr_jumper_info">
    <property name="wsdlLocation">fr_jumper_info.wsdl</property>
    <property name="retryInterval">60</property>
    </partnerLinkBinding>
    <partnerLinkBinding name="eet_mismatch_correction">
    <property name="wsdlLocation">eet_mismatch_correction.wsdl</property>
    <property name="retryInterval">60</property>
    </partnerLinkBinding>
    <partnerLinkBinding name="TaskService">
    <property name="wsdlLocation">TaskServiceWSIF.wsdl</property>
    </partnerLinkBinding>
    <partnerLinkBinding name="IRobo_Workflow2">
    <property name="wsdlLocation">workflow2.wsdl</property>
    </partnerLinkBinding>
    </partnerLinkBindings>
    </BPELProcess>
    </BPELSuitcase>
    Workflow2 WSDL
    <?xml version="1.0" encoding="UTF-8"?>
    <definitions
    name="IRobo_Workflow2"
    targetNamespace="http://xmlns.oracle.com/IRobo_Workflow2"
    xmlns="http://schemas.xmlsoap.org/wsdl/"
    xmlns:tns="http://xmlns.oracle.com/IRobo_Workflow2"
    xmlns:wsa="http://schemas.xmlsoap.org/ws/2003/03/addressing"
    xmlns:plnk="http://schemas.xmlsoap.org/ws/2003/05/partner-link/"
    xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
    xmlns:client="http://xmlns.oracle.com/IRobo_Workflow2">
    <types>
    <schema xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://xmlns.oracle.com/IRobo_Workflow2" schemaLocation="IRobo_Workflow2.xsd"/>
    </schema>
    <schema xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://01hw127125.India.TCS.com:8888/orabpel/xmllib/ws-addressing.xsd"/>
    </schema>
    </types>
    <message name="IRobo_Workflow2ResponseMessage">
    <part name="payload" element="tns:IRobo_Workflow2ProcessResponse"/>
    </message>
    <message name="IRobo_Workflow2RequestMessage">
    <part name="payload" element="tns:IRobo_Workflow2ProcessRequest"/>
    </message>
    <message name="WSARelatesToHeader">
    <part name="RelatesTo" element="wsa:RelatesTo"/>
    </message>
    <message name="WSAReplyToHeader">
    <part name="ReplyTo" element="wsa:ReplyTo"/>
    </message>
    <message name="WSAMessageIDHeader">
    <part name="MessageID" element="wsa:MessageID"/>
    </message>
    <portType name="IRobo_Workflow2Callback">
    <operation name="onResult">
    <input message="tns:IRobo_Workflow2ResponseMessage"/>
    </operation>
    </portType>
    <portType name="IRobo_Workflow2">
    <operation name="initiate">
    <input message="tns:IRobo_Workflow2RequestMessage"/>
    </operation>
    </portType>
    <binding name="IRobo_Workflow2CallbackBinding" type="tns:IRobo_Workflow2Callback">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="onResult">
    <soap:operation style="document" soapAction="onResult"/>
    <input>
    <soap:header message="tns:WSARelatesToHeader" part="RelatesTo" use="literal" encodingStyle=""/>
    <soap:body use="literal"/>
    </input>
    </operation>
    </binding>
    <binding name="IRobo_Workflow2Binding" type="tns:IRobo_Workflow2">
    <soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
    <operation name="initiate">
    <soap:operation style="document" soapAction="initiate"/>
    <input>
    <soap:header message="tns:WSAReplyToHeader" part="ReplyTo" use="literal" encodingStyle=""/>
    <soap:header message="tns:WSAMessageIDHeader" part="MessageID" use="literal" encodingStyle=""/>
    <soap:body use="literal"/>
    </input>
    </operation>
    </binding>
    <service name="IRobo_Workflow2CallbackService">
    <port name="IRobo_Workflow2CallbackPort" binding="tns:IRobo_Workflow2CallbackBinding">
    <soap:address location="http://set.by.caller"/>
    </port>
    </service>
    <service name="IRobo_Workflow2">
    <port name="IRobo_Workflow2Port" binding="tns:IRobo_Workflow2Binding">
    <soap:address location="http://01hw127125.India.TCS.com:8888/orabpel/default/IRobo_Workflow2/1.0"/>
    </port>
    </service>
    <plnk:partnerLinkType name="IRobo_Workflow2">
    <plnk:role name="IRobo_Workflow2Provider">
    <plnk:portType name="tns:IRobo_Workflow2"/>
    </plnk:role>
    <plnk:role name="IRobo_Workflow2Requester">
    <plnk:portType name="tns:IRobo_Workflow2Callback"/>
    </plnk:role>
    </plnk:partnerLinkType>
    </definitions>
    James I am making the endpoint reference available at run time so I think I need not change it while deploying.I think this is the problem the problem.
    <schema xmlns="http://www.w3.org/2001/XMLSchema">
    <import namespace="http://schemas.xmlsoap.org/ws/2003/03/addressing" schemaLocation="http://01hw127125.India.TCS.com:8888/orabpel/xmllib/ws-addressing.xsd"/>
    </schema>

  • Question related to remote weblogic deployment using wldeploy task

    Problem Description: Iam trying to perform a remote deployment using wldeploy task from one of the unix box(this box does not have a weblogic instance at all) to a remote unix weblogic server. I get the following connection exception. This script works fine when I do a remote deployment from my windows machine(this has a local weblogic server)to the same remote unix weblogic server.
    Question:
    1. Do I need to have a weblogic instance locally where this wldeploy task is executing?
    2. What configuration should be done in the remote weblogic server to support remote deployment?
    The ant task is:
    <property name="wlantjars" value="/ftmp/users/usrgrb/tmp/antjars" />
    <path id="wlappc.classpath">
    <fileset dir="${wlantjars}">
    <include name="*.jar"/>
    </fileset>
    </path>
    <taskdef name="wldeploy" classpathref="wlappc.classpath" classname="weblogic.ant.taskdefs.management.WLDeploy"/>
    <target name="deployear_dev2">
    <wldeploy user="weblogic" password="*******" adminurl="t3://he3unxd189v01:9100" action="deploy" upload="true" remote="true" source="${build.dir}/mktpx.ear" name="mktpx" targets="devCluster" />
    </target>
    I receive the following error when I execute the ant task "deployear_dev2"
    Buildfile: build.xml
    deployear_dev2:
    [wldeploy] weblogic.Deployer -remote -upload -noexit -name mktpx -source /usrdata/dev/cashdesk/gcp/mktprice/quickbuild_prototype_ccview/prototype.vws/vob/mktprice_vob/mkt_price/dist/mktpx.ear -targets devCluster -adminurl t3://he3unxd189v01:9100 -user weblogic -password ******** -deploy
    [wldeploy] weblogic.Deployer invoked with options: -remote -upload -noexit -name mktpx -source /usrdata/dev/cashdesk/gcp/mktprice/quickbuild_prototype_ccview/prototype.vws/vob/mktprice_vob/mkt_price/dist/mktpx.ear -targets devCluster -adminurl t3://he3unxd189v01:9100 -user weblogic -deploy
    [wldeploy] javax.enterprise.deploy.spi.exceptions.DeploymentManagerCreationException: [J2EE Deployment SPI:260010]Unable to connect to 't3://he3unxd189v01:9100' as user, 'weblogic'. Error received: Couldn't connect to any host
    [wldeploy] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:121)
    [wldeploy] at weblogic.deploy.api.spi.factories.internal.DeploymentFactoryImpl.getDeploymentManager(DeploymentFactoryImpl.java:84)
    [wldeploy] at weblogic.deploy.api.tools.SessionHelper.getRemoteDeploymentManager(SessionHelper.java:496)
    [wldeploy] at weblogic.deploy.api.tools.deployer.Jsr88Operation.connect(Jsr88Operation.java:297)
    [wldeploy] at weblogic.deploy.api.tools.deployer.Deployer.perform(Deployer.java:137)
    [wldeploy] at weblogic.deploy.api.tools.deployer.Deployer.runBody(Deployer.java:88)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:158)
    [wldeploy] at weblogic.utils.compiler.Tool.run(Tool.java:115)
    [wldeploy] at weblogic.Deployer.run(Deployer.java:70)
    [wldeploy] at weblogic.Deployer.mainWithExceptions(Deployer.java:62)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:597)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.invokeMain(WLDeploy.java:419)
    [wldeploy] at weblogic.ant.taskdefs.management.WLDeploy.execute(WLDeploy.java:349)
    [wldeploy] at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    [wldeploy] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    [wldeploy] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    [wldeploy] at java.lang.reflect.Method.invoke(Method.java:597)
    [wldeploy] at org.apache.tools.ant.dispatch.DispatchUtils.execute(DispatchUtils.java:105)
    [wldeploy] at org.apache.tools.ant.Task.perform(Task.java:348)
    [wldeploy] at org.apache.tools.ant.Target.execute(Target.java:357)
    [wldeploy] at org.apache.tools.ant.Target.performTasks(Target.java:385)
    [wldeploy] at org.apache.tools.ant.Project.executeSortedTargets(Project.java:1329)
    [wldeploy] at org.apache.tools.ant.Project.executeTarget(Project.java:1298)
    [wldeploy] at org.apache.tools.ant.helper.DefaultExecutor.executeTargets(DefaultExecutor.java:41)
    [wldeploy] at org.apache.tools.ant.Project.executeTargets(Project.java:1181)
    [wldeploy] at org.apache.tools.ant.Main.runBuild(Main.java:698)
    [wldeploy] at org.apache.tools.ant.Main.startAnt(Main.java:199)
    [wldeploy] at org.apache.tools.ant.launch.Launcher.run(Launcher.java:257)
    [wldeploy] at org.apache.tools.ant.launch.Launcher.main(Launcher.java:104)
    [wldeploy] Caused by: weblogic.deploy.api.spi.exceptions.ServerConnectionException: [J2EE Deployment SPI:260010]Unable to connect to 't3://he3unxd189v01:9100' as user, 'weblogic'. Error received: Couldn't connect to any host
    [wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:251)
    [wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServerForType(ServerConnectionImpl.java:191)
    [wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.init(ServerConnectionImpl.java:147)
    [wldeploy] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.getNewConnection(WebLogicDeploymentManagerImpl.java:148)
    [wldeploy] at weblogic.deploy.api.spi.deploy.WebLogicDeploymentManagerImpl.<init>(WebLogicDeploymentManagerImpl.java:118)
    [wldeploy] ... 32 more
    [wldeploy] Caused by: java.io.IOException: Couldn't connect to any host
    [wldeploy] at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:156)
    [wldeploy] at weblogic.management.remote.common.ClientProviderBase.newJMXConnector(ClientProviderBase.java:79)
    [wldeploy] at javax.management.remote.JMXConnectorFactory.newJMXConnector(JMXConnectorFactory.java:338)
    [wldeploy] at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:247)
    [wldeploy] at weblogic.deploy.api.spi.deploy.internal.ServerConnectionImpl.getMBeanServer(ServerConnectionImpl.java:240)
    [wldeploy] ... 36 more
    [wldeploy] Caused by: javax.naming.NamingException: Couldn't connect to any host [Root exception is org.omg.CORBA.OBJECT_NOT_EXIST: Unknown object in LOCATE_REQUEST  vmcid: 0x0  minor code: 0  completed: No]
    [wldeploy] at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:83)
    [wldeploy] at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:590)
    [wldeploy] at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:547)
    [wldeploy] at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:85)
    [wldeploy] at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:31)
    [wldeploy] at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)
    [wldeploy] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)
    [wldeploy] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:288)
    [wldeploy] at javax.naming.InitialContext.init(InitialContext.java:223)
    [wldeploy] at javax.naming.InitialContext.<init>(InitialContext.java:197)
    [wldeploy] at weblogic.management.remote.common.ClientProviderBase.makeConnection(ClientProviderBase.java:143)
    [wldeploy] ... 40 more
    [wldeploy] Caused by: org.omg.CORBA.OBJECT_NOT_EXIST: Unknown object in LOCATE_REQUEST vmcid: 0x0 minor code: 0 completed: No
    [wldeploy] at weblogic.iiop.LocateReplyMessage.needsForwarding(LocateReplyMessage.java:171)
    [wldeploy] at weblogic.iiop.IORManager.locateInitialReference(IORManager.java:254)
    [wldeploy] at weblogic.corba.orb.ORB.resolve_initial_references(ORB.java:258)
    [wldeploy] at weblogic.corba.client.naming.ClientORBInfo.<init>(ClientORBInfo.java:34)
    [wldeploy] at weblogic.corba.client.naming.ClientORBHelper.createORBInfo(ClientORBHelper.java:42)
    [wldeploy] at weblogic.corba.j2ee.naming.ORBHelper.cacheORB(ORBHelper.java:314)
    [wldeploy] at weblogic.corba.j2ee.naming.ORBHelper.cacheORBAndCreateURL(ORBHelper.java:323)
    [wldeploy] at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:583)
    [wldeploy] ... 49 more
    BUILD FAILED
    /usrdata/dev/cashdesk/gcp/mktprice/quickbuild_prototype_ccview/prototype.vws/vob/mktprice_vob/mkt_price/build/build.xml:366: weblogic.Deployer$DeployerException: weblogic.deploy.api.tools.deployer.DeployerException: Unable to connect to 't3://he3unxd189v01:9100': Unknown object in LOCATE_REQUEST. Ensure the url represents a running admin server and that the credentials are correct. If using http protocol, tunneling must be enabled on the admin server.
    Total time: 9 seconds

    regarding error:
    Caused by: org.omg.CORBA.OBJECT_NOT_EXIST: Unknown object in LOCATE_REQUEST vmcid: 0x0 minor code: 0 completed: No
    Make sure to place the wlfullclient.jar at the beginning of the classpath ...any other WLS specific Jars need not to be added additionally. For above error please refer to : Client SAF error
    Few Things:
    1). When I execute the ant build from a remote box , should I have a weblogic server running...the reason I ask is..does the wldeploy task work only if there is an active weblogic domain in the local machine. When I execute the same build from my windows machine where I have a local instance of weblogic , it works uccessfully .Whenever you try to deploy any application on WebLogic Domain then the Admin Server must be running. Because the deployment entries goes inside the "config.xml" and the original copy of this file is maintained by AdminServer only. So the Admin Server must be running for any kind of configuration changes or for Deployment.
    2). I am told that http protocol is not an option in my work place and I have to use t3 protocol only. In that case, based on the error below, is it possible that the connection between my local unix box and the remote weblogic box is stricted? How to I test the connectivity using t3? I pinged the server from the local unix server and it came back with reply, but could not telnet to that remote box nor ftp to that box does not work.You can check t3 protcol is working fine or not by using the following one line command:
    java weblogic.Admin -url t3://he3unxd189v01:9100 -username weblogic  -password weblogic    PING
    If above command fails to ping the server it means either you are using a wrong HostName & Port OR your N/W is doesnot allow t3 protocol connections OR there may be a N/W Issue.
    Thanks
    Jay SenSharma

  • Migration Windows to unix environment.

    Hi,
    we planning to convert our SAP Development Server from Windows
    to unix environment.
    In first step We planned to take System copy in our Development Server.
    While we executing the SAPINST file it terminates with error in
    Export_ABAP phase.
    SAP INST file Location
    ======================
    SAP ERP 2005 Support Release 2 > Additional Software Life-Cycle Tasks >
    System Copy > Oracle > Source System > Central System > Based on AS
    ABAP > Database Instance Export
    In the Phase 4 (Export Abap) the follwing message occurs
    "Your SAP System may be running.Stop the system and continue with data
    Unload".
    Hereby attached  log
    files.
    We are waiting for your reply.
    .Log file
    =======
    E:\usr\sap\D02\SYS\exe\nuc\NTAMD64\R3load.exe -e SAPSDIC.cmd -l SAPSDIC.log -stop_on_error
    (DB) INFO: connected to DB
    (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
    (EXP) ERROR: there are incomplete incremental conversions
                 export not allowed
    E:\usr\sap\D02\SYS\exe\nuc\NTAMD64\R3load.exe: job finished with 1 error(s)
    E:\usr\sap\D02\SYS\exe\nuc\NTAMD64\R3load.exe: END OF LOG: 20090818170548
    Regards
    Senthil Kumar

    > we planning to convert our SAP Development Server from Windows
    > to unix environment.
    First info:
    Heterogeneous system migrations (changing database or operating system - or both) must be done by a certified migration consultant with special knowledge; if you do it yourself, you will loose support for problems in,  during and after the migration for the target system --> OSS support will be billed separately.
    See http://service.sap.com/osdbmigration
    --> FAQ
    > (DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): WE8DEC
    > (EXP) ERROR: there are incomplete incremental conversions
    >              export not allowed
    I can think of several reasons for this problem:
    - This system was migrated recently to Unicode (using ICNV) and you have not done all delta conversions yet
    - You still have tables/indexes in your mass processing (transaction SE14)
    - you have inconsistencies between ABAP DDIC and database
    Markus

  • Pass a Value to Variable from the unix environment in ODI (ELT)

    Hi
    i am very new to ODI environment.
    i want know how to pass a value to variables in oracle data integrator from unix environment.
    Example:
    Variable name : Sales
    for variable name sales i want to pass the value from unix environment.
    Regards,
    Raj
    Edited by: user11137587 on Aug 19, 2009 6:26 AM

    Work Around !
    You can execute OS commands using Jython script. Probably you need to flush your enviornment variables value into a file using jython script and then read those value into ODI variable from the file.
    BUt may I know why you want to read environment variable vaules in ODI, Dont you think this will make your application less portable
    Regards,
    Amit

  • Why do I get -18001 Errors using Customised TestStand User Interface

    Hi all
    I have a problem when attempting to run my application on my host NT PC. I have a customised operator interface to TestStand written using Labview 5.1.1 and built using the LabVIEW application builder. I am running the TestStand Development (Run-Time) System on my host PC.
    The problem is that as soon as I go to run my sequence of vis (mass compiled using the same version of LabVIEW and assembled for run-time distribution) I receive the error '-18001 VI Not Executable.'
    I think this is probably to do with how I've included the ActiveX server in my LabVIEW User Interface application, but knowing very little about ActiveX I'm not sure exactly what the problem is.
    If anyone
    has any ideas, I would be extremely grateful for any assistance you could offer. My TS version is 1.0.1
    Thanks
    Dave

    David,
    I would like to add to Richard's input. The typical reasons a VI cannot be executed that cause this message are:
    1) There is an error in the VI such that the run arrow of the VI is broken when the VI is open in the LV development environment. This problem is usually easy to debug because you should get the error (shown below) when running your sequence in the sequence editor using the default "LabVIEW" ActiveX server provided by the LV development environment (not the LV ActiveX server provided by your operator interface which is by default named "TestStandLVGUIRTS" ).
    An error occurred in the 'MyVIStep' step of the 'MainSequence' sequence in 'MySequence.seq'.
    LabVIEW : VI is not executable.
    An error occurred accessing the LabVIEW ActiveX automation server. Error Code: -18001
    2) The same error will occur when
    a. you are using any LV ActiveX server other than the "LabVIEW" server provided by the LV development environment, AND
    b. at least one of the called VI was not assembled for distribution properly. This means that not all test VIs and their *entire* hierarchy were distributed.
    I am not sure exactly what you have done so have compiled some information that I think will help. Below I have included the document, Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter, which will appear in the NIDZ shortly. Another useful document is the NIDZ document Distributing LabVIEW Test VIs, which you can obtain from our website. Read these documents before preceding with the steps immediately below, which give you an example process for distributing. This may help provide a better understanding and guidance in the distribution process. We are working to simplify this process in future versions of TestStand.
    For the following example distribution I recommend that you are use default shipping code so that the problem is not complicated with potential errors added through customizations you have made.
    Building The Operator Interface
    The following are steps if you are using a LabVIEW operator interface.
    1) Copy the contents of \OperatorInterfaces\NI\LV to \OperatorInterfaces\User\LV.
    2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
    3) In LabVIEW Select Tools>>Build Application or Shared Library
    4) In the builder click the Load button and load \OperatorInterfaces\User\LV\testexec.bld. This build script is configured to create testexec.exe that contains the LV ActiveX server with the name of TestStandLVGUIRTS (see the Application tab of the builder).
    5) In the builder click Build.
    6) Once the application testexec.exe is built, run it once so that the server TestStandLVGUIRTS is automatically registered. You do not need to run a sequence. Close texec.exe.
    Creating a LabVIEW Run-time Server
    If you are using the LabVIEW operator interface then skip this section. The following steps are meant for those who use an operator interface written in a ADE other than LabVIEW. They provide you with a LabVIEW run-time server that is used by TS to run your VIs.
    1) Copy the contents of \Components\NI\RuntimeServers to \Components\User\RuntimeServers.
    2) Open a new VI in LabVIEW. Make sure all other VIs are closed.
    3) In LabVIEW Select Tools>>Build Application or Shared Library
    4) In the builder click the Load button and load \Components\User\RuntimeServers\LabVIEW\TestStandLVRTS.bld. This build script is configured to create TestStandLVRTS.exe that contains the LV ActiveX server with the name of TestStandLVRTS (see the Application tab of the builder).
    5) In the builder click Build.
    6) Once the application TestStandLVRTS.exe is built, run it once so that the server TestStandLVRTS is automatically registered on your development machine. Close TestStandLVRTS.exe.
    Assembling the Test VIs for Run-Time Distribution
    This distribution process uses one of the shipping TS examples that calls LV VIs.
    1) From LV mass compile all VIs in the directory \Examples\AccessingArrays\UsingLabVIEW\. Please make sure that there were no error messages in the Status tab of the Mass Compile dialog box.
    2) In the sequence editor open \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq
    3) Confirm that the sequence runs without problem.
    4) In the sequence editor select Tools>>Assemble Test VIs for Run-time Distribution.
    5) If you are using TestStand 2.0 select \Examples\AccessingArrays\UsingLabVIEW\AccessingArrays.seq as the file from which the VIs should be assembled.
    6) Set the target directory to be something distinct like C:\temp\AssblVIs.
    7) If you are using TestStand 2.0 skip adding Dynamic VIs
    8) Save with or without diagrams. Its your choice.
    Change Search Directories
    Once the VIs are assembled successfully, you must add the new target directory to the TS search directories.
    1) In the sequence editor select Configure>>Search Directories.
    2) Add your target search directory (e.g. C:\temp\AssblVIs) to the search directories.
    3) Close the Edit Search Directories dialog box.
    4) Confirm that your sequence steps now reference the assembled VIs. Right click on a step in the sequence and select Specify Module.
    5) The dialog should show that the code module is found in the target directory (e.g. C:\temp\AssblVIs) that you just added to the search directories.
    6) Run the sequence. This is the initial test to see if the VIs are assembled properly.
    Switch the LV Adapter to use the TestStandLVRTS server or TestStandLVGUIRTS
    1) In the sequence editor select Configure>>Adpaters.
    2) In the Configurable Adapters control select the LabVIEW Standard Prototype Adapter and then click the Configure button.
    3a) If you are not using the LV operator interface then switch the ActiveX server to TestStandLVRTS.
    3b)If you are using the LV operator interface then switch the ActiveX server to TestStandLVGUIRTS.
    4) Close the adapter configuration dialog boxes. You will get a couple of questions boxes. Just click OK each time.
    5) Now run your sequence. If successful you are no longer using the LV development environment to run your VIs. This shows that the VIs were assembled correctly, the LV ActiveX server is working properly and that the search directories are configured properly.
    You can now try and run the sequence using your operator interface on you development computer. If this test works it means that you have also confirmed that your operator interface is working correctly with all the other components. Now it is just a matter of moving all the component correctly to the target machine.
    Distributing Components
    -To distribute your operator interface use the distribution tool of the application development environment (ADE) in which you built your operator interface.
    -To distribute the TS engine using the Run Engine Installation Wizard tool. This tool is typically not used for distributing your sequences and VIs, which you will probably distribute more frequently than the TS engine. It does distribute and register your LV run-time server (if you are using one) as long as you have stored it in \Components\User\RuntimeServers. It also distributes other TS components that you have stored under the directory \Components\User\.
    -You can use whatever distribution system you like to distribute your VIs and sequence files (e.g. ZIP and network transfer are popular) . Ensure that you distribute the assembled VIs and not the development VIs. Also ensure that the location of the VIs on the target machine is one of the TS search directories.
    Hope this helps.
    Regards,
    Kitt
    =========================================
    Title:
    Overview of Distributing TestStand when your Sequences use the LV Standard Prototype Adapter
    The general outline of the components to be distributed and the actions to take are followed by a more detailed description.
    Components that need to be distributed:
    TS engine
    Operator interface
    LabVIEW executable that will act as a LabVIEW ActiveX automation server (If the operator interfaces is written in LabVIEW, it can function as the LabVIEW ActiveX automation server.).
    LabVIEW run-time engine
    LabVIEW test VIs
    Test sequence files
    Actions before distributing:
    It is recommended that you test the distribution components on the development machine before you distribute them to your target machine. In this manner you can more easily debug errors that you may encounter
    Create the executable that will serve as your LabVIEW ActiveX server on the target machine (components 2 or 3 above).
    Assemble the test VIs for distribution.
    Update the TestStand search directories so that the sequences reference the assembled VIs.
    Configure the LabVIEW Standard Prototype Adapter to use the LabVIEW ActiveX server that you will install on the target machine.
    Test the distribution components on the development machine.
    Enter section headings, separating each section with a line break:
    TS Engine Component
    Operator Interface Component
    LabVIEW ActiveX Server
    Configuring the LabVIEW Standard Prototype Adapter
    LabVIEW Run-time Engine Component
    Assembling your Test VIs for Distribution
    Note
    TS Engine Component
    With any TestStand distribution you must install the TestStand runtime engine on the target machine. The Run Engine Installation Wizard tool, found under Tools menu of the Sequence Editor, facilitates this process. The wizard tool will create two files, SetupTSEngine.exe and TSEngine.cab. Move the two files to your target machine and run SetupTSEngine.exe to install the TestStand engine.
    These installation files include the current configuration settings that exist in the Sequence Editor at the time the tool is invoked. It also includes all process models, TestStand types and step type modules. If you have customized components of TestStand and saved them under the directory TestStand\Components\User, then the components will also be included with the engine installation.
    You must purchase at least a base deployment or debug deployment license for each machine on which you install the TestStand engine.
    Operator Interface Component
    You will also need to install an operator interface executable on the target machine. This program acts as a client to the TS runtime engine, controlling the execution of sequences and displaying their progress. TestStand ships with several versions of TestStand operator interfaces, which are written in different application development environments (ADE). For distributing the operator interface executable, refer to the application development environment in which it was created.
    LabVIEW ActiveX Server
    You must have a LabVIEW ActiveX server on the target machine. TestStand uses the LabVIEW ActiveX server to run VIs using either the LabVIEW development environment or the LabVIEW runtime engine. The LabVIEW ActiveX server is provided by either LabVIEW development environment or by any LabVIEW executable that has been built with �Enable ActiveX Server� selected. This setting can be accessed in the LabVIEW Application Builder during the build process. When this preference is enabled, you must enter a server name. You will use the server name to configure the LabVIEW Standard Prototype adapter in TestStand.
    If your operator interface is written in LabVIEW, then it can act as the LabVIEW ActiveX server on your target machine. TestStand ships with two operator interfaces written in LabVIEW. The standard LabVIEW operator interface is located in TestStand\OperatorInterfaces\NI\LV, while a simplified version is located in TestStand\Examples\OperatorInterfaces\Simple LV. LabVIEW buildscripts are provided for these applications to facilitate building an operator interface in the latest version of LabVIEW. The settings of these buildscripts are such that the applications are LabVIEW ActiveX servers with the server names of TestStandLVGUIRTS for the standard operator interface, and TestStandSimpleLVGUIRTS for the simple operator interface. The applications register the servers the first time they are executed. If you want to manually register or unregister one of the servers, you can invoke the executable with the /RegServer and /UnregServer command-line arguments respectively.
    If your operator interface is programmed in a language other than LabVIEW, then you will need a separate LabVIEW executable to provide the LabVIEW ActiveX server on your target machine. For this purpose, TestStand ships with a LabVIEW run-time server application located in TestStand\Components\NI\RuntimeServers\LabVIEW. A LabVIEW buildscript is provided for this application to facilitate building a run-time server in the latest version of LabVIEW. The settings of this buildscript are such that the application is a LabVIEW ActiveX server with the server name of TestStandLVRTS.
    Note: When an ActiveX executable server is accessed, the executable is launched automatically if it is not already executing.
    Configuring the LabVIEW Standard Prototype Adapter
    When TestStand runs a VI using the LabVIEW Standard Prototype adapter, it does so using a LabVIEW ActiveX server. By default the adapter is configured to use the �LabVIEW� server, which is provided by the LabVIEW development environment. If you do not have the LabVIEW development environment on your target machine then you must configure the LabVIEW Standard Prototype adapter within TestStand to use a different server (e.g. TestStandLVGUIRTS, TestStandLVRTS, or TestStandSimpleLVGUIRTS).
    To configure your LabVIEW Standard Prototype adapter, select Configure>>Adapters from the menu. In the Adapter Configuration dialog box that appears, select the LabVIEW Standard Prototype Adapter in the Configurable Adapters section. Click the Configure button. You can select or type a server name in the Select or Type Which LabVIEW ActiveX Server to User control. If your server name is not in the list you will need to type it.
    As explained in the LabVIEW ActiveX Server section above, TestStand ships with LabVIEW buildscripts to build a LabVIEW operator interface and a LabVIEW run-time server application. These applications are LabVIEW ActiveX servers with server names TestStandLVGUIRTS and TestStandLVGRTS, respectively. You can configure you LabVIEW Standard Prototype adapter to use one of these servers.
    LabVIEW Run-time Engine Component
    If any of your sequence steps use the LabVIEW adapter or if your operator interface is written in LabVIEW, then you must install the LabVIEW runtime engine on the target machine. It is important that your LabVIEW run-time engine is the same version as the VIs that TestStand executes.
    You can find installation files for the LABVIEW 5.1 run-time engine in the LabVIEW installation directory, Labview\APPLIBS\installs\RunTime. In addition, you can choose to automatically distribute and install the LabVIEW run-time engine with the distribution of a LabVIEW executable. Refer to LabVIEW documentation.
    Assembling your Test VIs for Distribution
    After distributing TestStand, you must ensure that your sequences are able to locate the VIs they call, and the VIs must be able to locate their required resources.
    One common mistake is to simply copy the original VIs from the development machine to the target machine. Once you have configured your LabVIEW Standard Prototype adapter to use a LabVIEW ActiveX server other than LabVIEW, your sequence will not be able to execute your original test VIs that your sequences call.
    TestStand provides the Assemble Test VIs for Distribution tool, which gathers test VIs and their required resources, and places them in a common location for distribution. You can then modify your TestStand search directories so that your sequences reference the assembled VIs. These topics are covered in the NIDZ document Distributing LabVIEW Test VIs.
    Links: See Distributing LabVIEW Test VIs below
    Note
    Remember to test your distribution components on your TestStand development system before distributing TestStand. If the execution does not work on the development system it is not going to work on your target machine. On your development machine you have more ability to debug problems you may encounter.
    Note: One common problem of testing distribution components on your TestStand development system is that your sequences reference the original Test VIs instead of the assembled test VIs. Refer to the NIDZ document Distributing LabVIEW Test VIs for assistance.
    Once the components work on your development machine, you are ready to install them on your target machine. The order in which you install these components on the target machine is irrelevant.
    ==============================================

  • SSO Configuration in UNIX Environment

    Hi,
    We are planning to impliment SSO between 2004s Portal with R/3, BW, and host of other non SAP application which supports SSO. All the applications are hosted in UNIX environment.
    Could anyone help us in understanding the pros and cons of having SSO in unix envrionment. Also you could give us any document (other than help.sap.com) which guides us in configuring will be of great help.
    Thanks
    Vivek Raj.

    Hi,
    There are no pros and cons for <b>SSO on Unix</b>. Needless to mention, the pros and cons of different operating systems supported by SAP.
    The steps involved to configure SSO remains the same for any of the SAP backend systems:
    1) Create a system on Portal and give a system alias to it.
    2) Download the verify.der file from Portal (System Administration -> System Configuration -> Keystore Administration)
    3) Log on to the backend SAP system.
    4) Use transaction STRUSTSSO2 and import the Portal certifcate (verify.der) to the SAP R3 or SAP BW or SAP CRM or for that matter any SAP system with ABAP stack.
    5) Give the values for EP system ID, client and language. Refer to this link : http://help.sap.com/saphelp_nw2004s/helpdata/en/78/f1a8490e7011d6999500508b6b8a93/content.htm
    6) Configure the backend SAP systems to accept and verify the logon ticket. Use RZ10 and set the parameters : login/accept_sso2_ticket=1 and login/create_sso2_ticket=1
    7) Restart your R3 or BW system.
    For non-SAP systems, can you just let me know which systems are you referring to ?
    Incase you need a document for SSO configuration, do send me your email address. You can also find documents in SDN Library.
    Regards,
    Sunil

  • Java program in UNIX environment

    Hi All,
    Could you please help me with how to configure a java program in UNIX environment..
    that is to schedule it to run every day from cron..
    I need to know what are the basic things we require to achieve the above..
    I guess it is:
    A script
    A config file containing db login details
    oher than this I don?t know what is required plz help

    You can execute any jar or class file with cron. If you are using a jar you might use something like java -jar /usr/bin/myapp.jar .
    I use Linux, this is my area of expertise.
    Here is an online guide "for complete newbies" on how to set up cron.
    http://www.unixgeeks.org/security/newbie/unix/cron-1.html
    Hope it helps.

Maybe you are looking for