Re: WSIF0003W

David McDivitt wrote:
> I am using Websphere 5.1.1 and needed my application to perform IMS
> transactions on the mainframe. I created a service project to do this.
> Unfortunately the deployment people could not get the service project to
> work on the app server. It was their first one. So I copied all the java
> code from the service project into the application, and all the jar files
> needed, too. After changing the .classpath to reference the jar files,
> Websphere kept editing out the references. So I wrote a VB program to open
> .classpath with exclusive write, which stays resident. Following this the
> app worked great, and when deployed, it worked great, too. Everything the
> app needed was deployed with the app. It seems the way IBM enforces the
> IMSConnect license agreement is to edit the .classpath file, of all things.
> Websphere Enterprise suit whatever has license to use IMSConnect in a
> development environment, but a separate license is required for the app
> server. That license was purchased. They just couldn't get it to work.
>
> I wrote a plug-in scheduler to run batch jobs in the application scope. At
> start up it starts another thread, releasing the start up thread so the app
> will finish coming up. Everything works real nice with the scheduler. IMS
> transactions are being called from batch processes and client requests.
> Unfortunately a new standard says we have to do all scheduled jobs through
> CRON.
>
> I am now trying to get a standalone java app to run in UNIX, using stuff
> taken from the web app. My test classes work ok if I run them as a java
> application from within Websphere. It would seem, if stuff runs as a java
> application in Websphere, all I have to do to make a CRON job is find and
> copy out the necessary pieces.
>
> I almost have it working, but get the error "Port 'WSDL02IMSPort' is not
> available and  no alternative can be found". The console os pasted below. An
> IBM solution has the following:
>
>     WSIF0003W: An error occurred finding pluggable providers:
>     {0} Explanation: Parameters: {0} specific details about the
>     error. There was a problem locating a WSIF pluggable
>     provider using the J2SE 1.3 JAR file extensions to support
>     service providers architecture. The WSIF trace file will
>     contain the full exception details. User Response: Verify
>     that a META-INF/services/org.apache.wsif.spi.WSIFProvider
>     file exists in a provider jar, that each class referenced in
>     the META-INF file exists in the class path, and that each
>     class implements org.apache.wsif.spi.WSIFProvider. The class
>     in error will be ignored and WSIF will continue locating
>     other pluggable providers
>
> I verified this exists. The standalone java app still will not run. Help
> would be appreciated. Thanks
>   
hard to say what is going on (i have no idea what IMS is) but i would
try to use logger to see what provider is found (META-INF in multiple
jars can be tricky) or even override default WSIF provider for IMS
(WSIFPluggableProviders.overrideDefaultProvider())

HTH,

alek
>
>
>
> Last login: Tue Mar 14 15:32:49 2006 from c62046.idpa.sta
> Sun Microsystems Inc.   SunOS 5.9       Generic May 2002
> $ cd batch
> $ ls
> ApplicationObjects.jar         junk
> JobIMSTest.jar                 marshall.jar
> JobIMSTest.sh                  mfs.jar
> JobRefreshMmisAdjustments.jar  mfsadapter.jar
> JobRefreshMmisAdjustments.sh   physicalrep.jar
> RefreshMmisAdjustments.config  qname.jar
> a.txt                          tdlang.jar
> ccf2.jar                       tempRefreshMmisAdjustments
> commons-logging-api.jar        test.sh
> db2java.zip                    testA.sh
> dom.jar                        wsatlib.jar
> ibmjsse.jar                    wsdl4j.jar
> ims.txt                        wsif-j2c.jar
> imsico.jar                     wsif.jar
> imsjava.jar                    xerces.jar
> imstools.jar
> $ clear
> $ ls
> ApplicationObjects.jar         a.txt                          ims.txt
> mfs.jar                        test.sh                        xerces.jar
> JobIMSTest.jar                 ccf2.jar                       imsico.jar
> mfsadapter.jar                 testA.sh
> JobIMSTest.sh                  commons-logging-api.jar        imsjava.jar
> physicalrep.jar                wsatlib.jar
> JobRefreshMmisAdjustments.jar  db2java.zip                    imstools.jar
> qname.jar                      wsdl4j.jar
> JobRefreshMmisAdjustments.sh   dom.jar                        junk
> tdlang.jar                     wsif-j2c.jar
> RefreshMmisAdjustments.config  ibmjsse.jar                    marshall.jar
> tempRefreshMmisAdjustments     wsif.jar
> $ sh JobIMSTest.sh
> Mar 14, 2006 3:33:17 PM org.apache.wsif.logging.MessageLogger logIt
> WARNING: WSIF0003W: An error occurred finding pluggable providers:
> javax/resource/cci/ConnectionSpec
> Exception in thread "main" org.apache.wsif.WSIFException: Port
> 'WSDL02IMSPort' is not available and  no alternative can be found
>         at
> org.apache.wsif.base.WSIFServiceImpl.getPort(WSIFServiceImpl.java:599)
>         at WSDL.WSDL02Proxy.execute(WSDL02Proxy.java:136)
>         at WSDL.WSDL02Proxy.getAdjustmentInfo(WSDL02Proxy.java:73)
>         at
> persistence.ims.test.TestAdjustmentService.main(TestAdjustmentService.java:24)
> $
>
> http://publib.boulder.ibm.com/infocenter/wasinfo/v6r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/rwsf_msg.html
>   


-- 
The best way to predict the future is to invent it - Alan Kay