Can't configure Apache connector
I've tried this on Fedora Core 9 with no success and now I'm
trying it on FC8 with the same error. After installing CF and
configuring it to work with Apache, I go to start it and I get
quote:
[root@ns1 ~]# /opt/coldfusion8/bin/coldfusion start
Starting ColdFusion 8...
The ColdFusion 8 server is starting up and will be available
shortly.
======================================================================
Running the ColdFusion 8 connector wizard
======================================================================
Configuring the web server connector (Launched on the first
run of the ColdFusion 8 start script)
Running apache connector wizard...
=======================================
There was an error while running the connector wizard
Connector installation was not successful
=======================================
======================================================================
ColdFusion 8 has been started.
ColdFusion 8 will write logs to
/opt/coldfusion8/logs/cfserver.log
======================================================================
I changed the paths in the 'apache-connector.sh' file, but I
still can't get it to work. Any ideas?
Ok, this is from this morning when trying:
07/25 09:05:39 info Macromedia JRun 4.0 (Build 108487)
07/25 09:05:40 debug Found JRun server coldfusion at
127.0.0.1:2930
07/25 09:05:40 debug Deleted directory
/opt/coldfusion8/runtime/lib/wsconfig/1/.libs
07/25 09:05:40 debug Deleted directory
/opt/coldfusion8/runtime/lib/wsconfig/1
07/25 09:05:40 info Fedora release 9 (Sulphur)
07/25 09:05:40 debug Using Apache binary /usr/sbin/httpd
07/25 09:05:40 info Server's Module Magic Number:
20051115:11. Supported major magic numbers on this platform are
20020628 and 20020903.
07/25 09:05:40 info Attempting to build connector from
sources
07/25 09:05:40 info Server version: Apache/2.2.8 (Unix)
07/25 09:05:40 debug Using Apache control script
/usr/sbin/httpd
07/25 09:05:40 debug Parsing Apache configuration file
/etc/httpd/conf/httpd.conf
07/25 09:05:40 debug Exec'ing chmod 777
/opt/coldfusion8/runtime/lib/wsconfig/1
07/25 09:05:40 debug Set permission to 777 on
/opt/coldfusion8/runtime/lib/wsconfig/1
07/25 09:05:40 debug Exec'ing chmod +x
/opt/coldfusion8/runtime/lib/wsconfig/1/build_jrun22
07/25 09:05:40 debug Set permission to execute on
/opt/coldfusion8/runtime/lib/wsconfig/1/build_jrun22
07/25 09:05:40 debug Exec'ing
/opt/coldfusion8/runtime/lib/wsconfig/1/build_jrun22
07/25 09:05:41 error Error running
"/opt/coldfusion8/runtime/lib/wsconfig/1/build_jrun22": exit code
was 1
07/25 09:05:41 error Could not build Apache2 web server
connector from source. Use build script /opt/coldfusion8/
runtime/lib/wsconfig/1/build_jrun22.
jrunx.connectorinstaller.ConnectorInstallerException: Could
not build Apache2 web server connector from source. U
se build script
/opt/coldfusion8/runtime/lib/wsconfig/1/build_jrun22.
at
jrunx.connectorinstaller.ApacheInstaller.buildModuleFromSource(ApacheInstaller.java:1234)
at
jrunx.connectorinstaller.ApacheInstaller.copyFiles(ApacheInstaller.java:1126)
at
jrunx.connectorinstaller.ApacheInstaller.installConnector(ApacheInstaller.java:223)
at
jrunx.connectorinstaller.ConnectorInstaller.installConnector(ConnectorInstaller.java:337)
at
jrunx.connectorinstaller.ConnectorInstaller.doIt(ConnectorInstaller.java:271)
at
jrunx.connectorinstaller.ConnectorInstaller.main(ConnectorInstaller.java:759)
Similar Messages
-
Can't configure SPML connector IDM 8.1
Hello
I try to configure SPML connector in IDM 8.1 (Solaris 10 x64, Java Web Server 7.0). When I try to add "New Resource", I choose "LOCAL", when I fill name,password, URL and add ObjectClassMapping, I add two rows ACCOUNT and GROUP. After "Next", I get "nullPointer Exception". I don't understand, what I do wrong.Have you solved the problem?
What kind of data you have insert into this field:
# objectClassNames
# spmlClassNames
# targetNames
# IDMAttribute
BTW i try to connect 2 idm 8.1 using the connector 1.0.4828
http://wikis.sun.com/display/IdentityConnectors/SPMLv2+Connector
thanks in advance
Alberto -
Integrating SOA and Peoplesoft: Configuring JMSTARGET Connector in IB.
Hi All,
I have created JMS queue/topic in oracle application server. Can anybody idea how can we configure JMS connector of peoplesoft integration broker.
Let me first explain my requirement, I am working in peoplesoft outbound interface design with SOA integration.
So my approach will be creating JMS queue in oracle application Server and then configuring this JMS to any node of peoplesoft IB.
Then extracted information from peoplesoft need to send to the above node so that once the node receive the message it should
populate the JMS queue inturn SOA BPEL will be triggered to write into third party file/database.
Please give your inputs on this approach if you any other suggetion for peoples soft outbound integration with SOA.
Thanks inadvance.Its published, but somehow you are unable to see it..issues with Meatlink for sure..
Here is its content :
Applies to:
PeopleSoft Enterprise PT PeopleTools - Version: 8.4 - Release: 8.4
Information in this document applies to any platform.
This document was previously published as Customer Connection Solution 201077819
Symptoms
Please see below.
Cause
Not Applicable
Solution
<<Document:664816.1>> E-IB: Configuring Integration Broker with IBM MQ on AIX
SPECIFIC TO: Enterprise, PeopleTools, Integration Broker Release 8.49
ISSUE:
How to setup Integration Broker to PUT messages to an IBM MQ Server on a remote machine?
SOLUTION:
<See attachment for documentation with screenshot examples.>
Configuring Integration Broker with IBM MQ on AIX
The following guide is intended to outline the setup between Peoplesoft Integration Broker and IBMs Websphere MQ version 6 client on AIX. Note: This is not a certification, but a working example, specifically using the MQ client to connect to a remote machine running the MQ server.
Platform Information:
PeopleSoft PeopleTools 8.49
IBM Websphere MQ Release 6
AIX
Steps
1) Install and IBM Websphere MQ (WMQ) client
2) Configure WMQ connection
3) Configure Peoplesoft
4) TEST using PING and a Peoplesoft message to PUT data onto the WMQ server
Steps
1) Install and configure Websphere MQ client on AIX where Peoplesoft is located
NOTE: This is one optional architecture. It is also possible to install Peoplesoft and MQ on the same server, which avoids the client software altogether.
a. IBM deliveres an MQ client that is installed on the same box as the Peoplesoft with the following options.
i. Installed to /usr/mqm, all objects owned by local user mqm
ii. Ensure that the MQ Extended Transactional Client is installed
1. This includes com.ibm.mqetclient.jar file
iii. Mq specific environment variables
1. $MQ_JAVA_DATA_PATH=/usr/mqm
2. $MQ_JAVA_INSTALL_PATH=/usr/mqm/java
3. $MQ_JAVA_LIB_PATH=/usr/mqm/java/lib
4. jms.jar, fscontext.jar, jndi.jar, providerutil.jar, stcjms.jar
iv. CLASSPATH
1. Includes the following MQ jar files
i. com.ibm.mqetclient.jar
ii. providerutil.jar
iii. com.ibm.mqjms.jar
iv. ldap.jar
v. jta.jar
vi. jndi.jar
vii. jms.jar
viii. connector.jar
ix. com.ibm.mq.jar
2. Example
a. > echo $CLASSPATH
i. echo $CLASSPATH /usr/mqm/java/lib/com.ibm.mqetclient.jar:/usr/mqm/java/lib/providerutil.jar:/usr/mqm/java/lib/com.ibm.mqjms.jar:/usr/mqm/java/lib/ldap.jar:/usr/mqm/java/lib/jta.jar:/usr/mqm/java/lib/jndi.jar:/usr/mqm/java/lib/jms.jar:/usr/mqm/java/lib/connector.jar:/usr/mqm/java/lib/fscontext.jar:/usr/mqm/java/lib/com.ibm.mq.jar:/usr/mqm/java/lib:/usr/mqm/java/bin
3. When setting up Peoplesoft, add these jar files to the classpath setting in the setenv.sh file and reboot PIA
2) Configure WMQ
a. Edit JMSAdmin.config (located in /usr/mqm/java/bin)
ii. Set Initial Context Factory = com.sun.jndi.fscontext.RefFSContextFactory
# The following line specifies which JNDI service provider is in use.
# It currently indicates an LDAP service provider. If a different
# service provider is used, this line should be commented out and the
# appropriate one should be uncommented.
#INITIAL_CONTEXT_FACTORY=com.sun.jndi.ldap.LdapCtxFactory
INITIAL_CONTEXT_FACTORY=com.sun.jndi.fscontext.RefFSContextFactory
#INITIAL_CONTEXT_FACTORY=com.ibm.ejs.ns.jndi.CNInitialContextFactory
iii. Set PROVIDER_URL=file:/usr/mqm/java
# The following line specifies the URL of the service provider's initial context. It currently refers to an LDAP root context. Examples of a file system URL and WebSphere's JNDI namespace are also shown, commented out.
#PROVIDER_URL=ldap://polaris/o=ibm,c=us
PROVIDER_URL=file:/usr/mqm/java
#PROVIDER_URL=iiop://localhost/
b. Run JMSAdmin to setup queue and qcf to the MQ server
i. def qcf(PLAS160_QCF) HOSTNAME(GSPLVP006-VM2) PORT(1414) CHANNEL(SYSTEM.DEF.SVRCONN) QMANAGER(QM_gsplvp006_vm2) TRANSPORT(CLIENT)
ii. NOTE: When connecting from a client to a remote server, it is important to specify the hostname, port and transport along with the other values.
iii. def q(PLAS160_Q) queue(PLAS160_Q)
1. Note: The q is a local naming alias, whereas the queue is the physical queue name on the MQ server
iv. Screenshot:
v. This creates a .bindings file
vi. NOTE: It is also possible to use IVTSetup for this, but JMSAdmin is recommended.
vii. NOTE: It is possible to gain a .bindings file from your MQ server administrator. Be sure that this format is correct, and the location on the client is referenced correctly.
viii. JMSAdmin can also be used to determin what connections are available from this machine using command dis ctx as shown
b. Optional: Test the connection to the MQ server using IBM software.
NOTE: Testing the ivtQ and ivt QCF can be accomplished using the IVTRun program, provided that the ivtQ and ivtQCF have been setup in the .bindings file with the same available on the MQ server (some mq administrators do not enable this by default)
i. Example IVTRun, see Appendix 1
ii. Example .bindings file see Appendix 2
3) Configure PeopleSoft
a. Create an external NODE representing the target JMS queue
i. Example node, see appendix 3
b. Setup the connectors properties for the new node
i. Use the connector ID= JMSTARGET
ii. Example properties screenshot, see Appendix 4
1. Notes
a. JMSProvider is MQSeries
b. JMSFactory, JMSQueue are those specified in the .bindings file representing that on the JMS server. In this case, PLAS160_QCF and PLAS160_Q are used for this example.
c. JMSUrl is the location of the working .bindings file on the web server (in this case file:/D:/apps/IBM/WebSphereMQ/Java )
c. Setup Gateway Properties
i. Access the Gateway Properties using PIA and add the JMS information for MQSeries to the integrationgateway.properties file as shown:
## JMS configuration Section
# <the following line is required>
ig.jms.JMSProvider.JNDIFactory.MQSeries=com.sun.jndi.fscontext.RefFSContextFactory
ii. Queue information here is only needed if going to GET message using the JMSListeningConnector. Not needed for the target PUT (or ping)
iii. Example integrationgateway.properties, See appendix 5
4) Test PUT connection from Peoplesoft to WMQ
1. Ping the JMS node from the node definition
b. Setup routings to PUT messages to the MQ node
i. Example using USER_PROFILE
ii. Submit the message and check the Operations Monitor
iii. Verify that the message made it to MQ (this is viewed by browsing the queue on the Websphere MQ Explorer, message browser. A better utility is rfhutil which is included in the MQ windows client development kit)
NOTE: This document is intended for 1 way communication TO Mq from Peoplesoft. Setup for GET using the JMSListeningConnector is a separate topic for documentation.
Appendix 1 IVTRun
Appendix 2 .bindings file.
NOTE: The PLAS160_QCF and PLAS160_Q references are applicable to this example.
#This file is used by the JNDI FSContext.
#Wed Sep 17 11:43:13 PDT 2008
PLAS160_QCF/RefAddr/9/Type=SRC
PLAS160_Q/RefAddr/5/Encoding=String
PLAS160_QCF/RefAddr/13/Content=5000
PLAS160_QCF/RefAddr/3/Content=GSPLVP006-VM2
PLAS160_Q/RefAddr/8/Content=PLAS160_Q
PLAS160_QCF/RefAddr/13/Type=PINT
PLAS160_QCF/RefAddr/1/Type=TRAN
MYPUT/RefAddr/2/Content=-2
PLAS160_QCF/RefAddr/6/Encoding=String
PLAS160_QCF/RefAddr/17/Type=RINT
PLAS160_QCF/RefAddr/5/Type=CHAN
PLAS160_QCF/RefAddr/18/Encoding=String
PLAS160_Q/RefAddr/2/Content=-2
PLAS160_PUT/RefAddr/1/Encoding=String
PLAS160_QCF/RefAddr/20/Content=SYSTEM.DEFAULT.MODEL.QUEUE
PLAS160_PUT/RefAddr/3/Type=PER
MYPUT/RefAddr/6/Encoding=String
PLAS160_Q/RefAddr/5/Content=0
PLAS160_PUT/RefAddr/8/Content=PLAS160_PUT
PLAS160_Q/RefAddr/6/Encoding=String
MYPUT/RefAddr/0/Type=VER
PLAS160_PUT/RefAddr/7/Type=FIQ
PLAS160_QCF/RefAddr/7/Encoding=String
MYPUT/RefAddr/4/Type=CCS
PLAS160_PUT/RefAddr/2/Content=-2
PLAS160_QCF/RefAddr/19/Encoding=String
PLAS160_PUT/RefAddr/5/Content=0
PLAS160_PUT/RefAddr/2/Encoding=String
PLAS160_Q/RefAddr/3/Type=PER
MYPUT/RefAddr/8/Type=QU
MYPUT/RefAddr/7/Encoding=String
PLAS160_Q/RefAddr/7/Encoding=String
MYPUT/ClassName=com.ibm.mq.jms.MQQueue
PLAS160_Q/RefAddr/7/Type=FIQ
PLAS160_QCF/RefAddr/8/Encoding=String
PLAS160_QCF/RefAddr/6/Type=CCS
MYPUT/RefAddr/9/Content=
PLAS160_QCF/RefAddr/10/Type=SFIPS
PLAS160_QCF/RefAddr/10/Encoding=String
PLAS160_PUT/RefAddr/3/Encoding=String
PLAS160_QCF/RefAddr/20/Type=TM
MYPUT/RefAddr/8/Encoding=String
PLAS160_Q/RefAddr/8/Encoding=String
PLAS160_QCF/RefAddr/14/Type=MBS
PLAS160_QCF/RefAddr/17/Content=5000
PLAS160_QCF/RefAddr/2/Type=QMGR
PLAS160_PUT/FactoryName=com.ibm.mq.jms.MQQueueFactory
PLAS160_QCF/RefAddr/7/Content=\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000\u0000
MYPUT/FactoryName=com.ibm.mq.jms.MQQueueFactory
MYPUT/RefAddr/3/Content=-2
PLAS160_PUT/RefAddr/0/Type=VER
MYPUT/RefAddr/6/Content=273
PLAS160_QCF/RefAddr/18/Type=TCM
PLAS160_QCF/RefAddr/9/Encoding=String
PLAS160_QCF/RefAddr/11/Content=false
PLAS160_QCF/RefAddr/1/Content=1
PLAS160_Q/RefAddr/6/Content=273
PLAS160_QCF/RefAddr/11/Encoding=String
PLAS160_QCF/RefAddr/20/Encoding=String
PLAS160_PUT/RefAddr/4/Type=CCS
PLAS160_PUT/RefAddr/4/Encoding=String
PLAS160_QCF/RefAddr/14/Content=10
PLAS160_QCF/RefAddr/4/Content=1414
PLAS160_Q/RefAddr/9/Content=
MYPUT/RefAddr/9/Encoding=String
MYPUT/RefAddr/0/Content=6
MYPUT/RefAddr/1/Type=EXP
PLAS160_Q/RefAddr/9/Encoding=String
PLAS160_PUT/RefAddr/8/Type=QU
PLAS160_Q/RefAddr/0/Content=6
PLAS160_Q/RefAddr/0/Type=VER
MYPUT/RefAddr/5/Type=TC
PLAS160_Q/RefAddr/3/Content=-2
PLAS160_QCF/RefAddr/0/Encoding=String
PLAS160_PUT/RefAddr/6/Content=273
PLAS160_QCF/RefAddr/21/Content=
PLAS160_Q/RefAddr/4/Type=CCS
MYPUT/RefAddr/9/Type=QMGR
PLAS160_QCF/RefAddr/21/Encoding=String
PLAS160_PUT/RefAddr/9/Content=
PLAS160_QCF/RefAddr/12/Encoding=String
PLAS160_PUT/RefAddr/5/Encoding=String
MYPUT/RefAddr/0/Encoding=String
PLAS160_Q/RefAddr/8/Type=QU
PLAS160_Q/RefAddr/0/Encoding=String
PLAS160_PUT/RefAddr/0/Content=6
PLAS160_Q/FactoryName=com.ibm.mq.jms.MQQueueFactory
PLAS160_PUT/RefAddr/3/Content=-2
PLAS160_QCF/RefAddr/7/Type=CT
PLAS160_QCF/RefAddr/1/Encoding=String
PLAS160_QCF/RefAddr/11/Type=SPAG
PLAS160_QCF/RefAddr/21/Type=TQPFX
PLAS160_QCF/RefAddr/13/Encoding=String
PLAS160_QCF/RefAddr/22/Encoding=String
PLAS160_PUT/RefAddr/6/Encoding=String
PLAS160_QCF/RefAddr/15/Type=FIQ
PLAS160_QCF/RefAddr/3/Type=HOST
MYPUT/RefAddr/1/Encoding=String
PLAS160_PUT/RefAddr/1/Type=EXP
PLAS160_QCF/RefAddr/19/Type=MNST
PLAS160_QCF/RefAddr/2/Encoding=String
PLAS160_PUT/RefAddr/5/Type=TC
PLAS160_QCF/FactoryName=com.ibm.mq.jms.MQQueueConnectionFactoryFactory
PLAS160_QCF/RefAddr/14/Encoding=String
PLAS160_QCF/RefAddr/18/Content=true
MYPUT/RefAddr/2/Type=PRI
PLAS160_QCF/RefAddr/8/Content=0
MYPUT/RefAddr/4/Content=1208
MYPUT/RefAddr/2/Encoding=String
PLAS160_PUT/RefAddr/9/Type=QMGR
PLAS160_Q/ClassName=com.ibm.mq.jms.MQQueue
PLAS160_Q/RefAddr/1/Encoding=String
MYPUT/RefAddr/7/Content=1
PLAS160_Q/RefAddr/1/Type=EXP
MYPUT/RefAddr/6/Type=ENC
PLAS160_QCF/RefAddr/12/Content=true
PLAS160_QCF/RefAddr/2/Content=QM_gsplvp006_vm2
PLAS160_Q/RefAddr/7/Content=1
PLAS160_QCF/RefAddr/3/Encoding=String
PLAS160_Q/RefAddr/5/Type=TC
PLAS160_QCF/RefAddr/15/Content=1
PLAS160_QCF/RefAddr/5/Content=SYSTEM.DEF.SVRCONN
MYPUT/RefAddr/1/Content=-2
PLAS160_PUT/RefAddr/7/Encoding=String
PLAS160_QCF/RefAddr/15/Encoding=String
PLAS160_Q/RefAddr/9/Type=QMGR
MYPUT/RefAddr/3/Encoding=String
PLAS160_Q/RefAddr/1/Content=-2
PLAS160_Q/RefAddr/2/Encoding=String
PLAS160_Q/RefAddr/4/Content=1208
PLAS160_QCF/RefAddr/8/Type=CTO
PLAS160_PUT/RefAddr/7/Content=1
PLAS160_QCF/RefAddr/22/Content=1
PLAS160_QCF/RefAddr/12/Type=UCP
PLAS160_QCF/RefAddr/0/Type=VER
PLAS160_QCF/RefAddr/4/Encoding=String
PLAS160_QCF/RefAddr/22/Type=MRET
PLAS160_QCF/RefAddr/16/Type=LA
PLAS160_PUT/ClassName=com.ibm.mq.jms.MQQueue
PLAS160_QCF/RefAddr/4/Type=PORT
PLAS160_PUT/RefAddr/8/Encoding=String
PLAS160_QCF/RefAddr/16/Encoding=String
PLAS160_PUT/RefAddr/1/Content=-2
PLAS160_PUT/RefAddr/4/Content=1208
PLAS160_Q/RefAddr/3/Encoding=String
PLAS160_PUT/RefAddr/2/Type=PRI
PLAS160_PUT/RefAddr/6/Type=ENC
PLAS160_QCF/RefAddr/5/Encoding=String
MYPUT/RefAddr/3/Type=PER
PLAS160_PUT/RefAddr/9/Encoding=String
PLAS160_QCF/RefAddr/17/Encoding=String
MYPUT/RefAddr/4/Encoding=String
PLAS160_Q/RefAddr/2/Type=PRI
MYPUT/RefAddr/7/Type=FIQ
PLAS160_Q/RefAddr/4/Encoding=String
PLAS160_QCF/ClassName=com.ibm.mq.jms.MQQueueConnectionFactory
PLAS160_QCF/RefAddr/16/Content=
PLAS160_Q/RefAddr/6/Type=ENC
PLAS160_QCF/RefAddr/6/Content=819
PLAS160_QCF/RefAddr/19/Content=true
PLAS160_QCF/RefAddr/9/Content=0
MYPUT/RefAddr/5/Content=0
PLAS160_PUT/RefAddr/0/Encoding=String
MYPUT/RefAddr/8/Content=PLAS160_PUT
PLAS160_QCF/RefAddr/10/Content=false
MYPUT/RefAddr/5/Encoding=String
PLAS160_QCF/RefAddr/0/Content=6
Appendix 3 Node definition
Appendix 4 - Node JMSTarget Connectors Properties
Appendix 5 integrationgateway.properties JMS configuration section
## JMS configuration Section
#The JNDIFactory Classnames for Weblogic, IPlanet, MQSeries.
#ig.jms.JMSProvider.JNDIFactory.Weblogic=weblogic.jndi.WLInitialContextFactory
#ig.jms.JMSProvider.JNDIFactory.IPlanet=com.sun.jndi.fscontext.RefFSContextFactory
ig.jms.JMSProvider.JNDIFactory.MQSeries=com.sun.jndi.fscontext.RefFSContextFactory
#ig.jms.JMSProvider.JNDIFactory.OracleApplicationServer=com.evermind.server.rmi.RMIInitialContextFactory
# Enter the number of Queue listners to instantiate
#ig.jms.Queues=1
# For each queue specify the following properties
# Name
# Provider
# JMSFactory name (which is binded to the JNDI)
# MessageSelector (optional Message Filter)
# JNDI System File URL
# JMS User
# JMS Password
# Example :
#ig.jms.Queue1=QUEUE_VAS
#ig.jms.Queue1.Provider=MQSeries
#ig.jms.Queue1.JMSFactory=QCF
# ig.jms.Queue1.MessageSelector=
#ig.jms.Queue1.Url=file:/D:/apps/IBM/WebSphereMQ/Java
# ig.jms.Queue1.User=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Queue1.Password=EncryptedPassword
# ig.jms.Queue1.SecurityPrincipal=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Queue1.SecurityCredentials=EncryptedPassword
#IBInfoHeaders
#ig.jms.Queue1.MessageName=QE_F18_ASYNC
#ig.jms.Queue1.MessageVersion=VERSION_1
#ig.jms.Queue1.RequestingNode=FromNode
#ig.jms.Queue1.DestinationNode=ToNode
# Use the supplied encryption utility to provide an encrypted password for the entry below
#ig.jms.Queue1.NodePassword=EncryptedRequestingNodePassword
#ig.jms.Queue1.SubChannel=SubChannel
# Enter the number of Topic Subscribers to instantiate
# ig.jms.Topics=1
# For each Topic specify the following properties
# Name
# Provider
# JMSFactory name (which is binded to the JNDI)
# MessageSelector (optional Message Filter)
# JNDI System File Url
# JMS User
# JMS Password
# Example :
# ig.jms.Topic1=ExampleTopic
# ig.jms.Topic1.Provider=MQSeries
# ig.jms.Topic1.JMSFactory=TopicConnectionFactory
# ig.jms.Topic1.MessageSelector=
# ig.jms.Topic1.Url=file:c:/
# ig.jms.Topic1.User=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Topic1.Password=EncryptedPassword
# ig.jms.Queue1.SecurityPrincipal=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Queue1.SecurityCredentials=EncryptedPassword
#IBInfo Headers
#ig.jms.Topic1.MessageName=QE_F18_ASYNC
#ig.jms.Topic1.MessageVersion=VERSION_1
#ig.jms.Topic1.RequestingNode=FromNode
#ig.jms.Topic1.DestinationNode=ToNode
# Use the supplied encryption utility to provide an encrypted password for the entry below
#ig.jms.Topic1.NodePassword=EncryptedRequestingNodePassword
#ig.jms.Topic1.SubChannel=SubChannel
#For sending error either ErrorQueue or ErrorTopic must be configured
#If both exists, errors are only sent to ErrorQueues.
#Configure the Error-Queue configuration
# ig.jms.ErrorQueue=ErrorQ
# ig.jms.ErrorQueue-Provider=Weblogic
# ig.jms.ErrorQueue-User=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.ErrorQueue-Password=sam
# ig.jms.Queue1.SecurityPrincipal=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.Queue1.SecurityCredentials=EncryptedPassword
# ig.jms.ErrorQueue-JMSFactory=TopicConnectionFactory
# ig.jms.ErrorQueue-Url=file:c:/
#Configure the Error-Topic configuration
# ig.jms.ErrorTopic=Error
# ig.jms.ErrorTopic-Provider=IPlanet
# ig.jms.ErrorTopic-User=sam
# Use the supplied encryption utility to provide an encrypted password for the entry below
# ig.jms.ErrorTopic-Password=sam
# ig.jms.ErrorTopic-JMSFactory=TopicConnectionFactory
# ig.jms.ErrorTopic-Url=file:c:/
## End of JMS configuration Section
# Profile Information
# Set it to either TRUE or FALSE
ig.ProfileInformation=FALSE
#End-Of Profile Information
##EIPTestTool Properties
#Class name of the Gateway Manager to use during processing
#ig.gatewayManagerClass=com.peoplesoft.pt.integrationgateway.eiptesttool.EIPTestToolGatewayManager
#Contains a true or false value.
#True for LoopBack
#ig.EIPLoopBack=TRUE
#Contains the directory path that will be used
#to store request/response files during recording.
#ig.EIPOutputDirectory=c:/temp/output
# Number of ig.EIPMsgProp.N.propFile's
#ig.EIPMsgProp.count=0
#Certification root directory
#ig.EIPInputDirectory=c:/temp/input
#MessageProperty file names with locations.
#ig.EIPMsgProp.1.propFile=c:/temp/input/properties/pro1.xml
#ig.EIPMsgProp.2.propFile=c:/temp/input/properties/pro2.xml
#Overrides input directory for an EIP
#ig.EIPMsgProp.1.inputDirectory=c:/temp/input/properties1/
#EIPNodemapFileName
#ig.EIPNodeMap=c:/temp/nodemap.xml
##End of EIPTestToolProperties
#File connector password.
# Use the supplied encryption utility to provide an encrypted password for the entry below
ig.fileconnector.password=EncryptedPassword
#End of file connector properties.
## Query Access Services (QAS) Configuration Section.
# QAS Repository Home Directory. This is the directory where Query result blocks will be
# temporarily persisted.
# Example:
#ig.qas.repositoryHomeDir=C:/QASRepository
# Uncomment the following line and replace the value with the actual QAS Repository Home Directory.
#ig.qas.repositoryHomeDir=<Full-Path-For-Directory>
## END of QAS Configuration.
## AS2 Connector Properties.
# These Properties need to be set to use either the AS2TargetConnector or the AS2ListeningConnector
# REQUIRED:
# AS2 KeyStore Properties
# Uncomment the following two lines to specify your key keystore path and password.
# Use the PSCipher.bat utility to encrypt the keystore password.
# example:
# ig.AS2.KeyStorePath=C://pt846//webserv//peoplesoft//keystore//pskey
# ig.AS2.KeyStorePassword=GD9klUFw8760HVaqeT4pkg==
# OPTIONAL:
# AS2 Log Directory, logs all incoming and outgoing AS2 requests and responses.
# Uncomment and specify the correct directory name to enable logging.
# example:
# ig.AS2.LogDirectory = c://temp//as2//logs
## End of AS2 Connector Properties
## AS2ListeningConnector Only Properties.
# OPTIONAL:
# AS2From and AS2To http header parameters are required on all incoming AS2 messages. These parameters must
# map to PeopleSoft node definitions either directly or indirectly via AS2 From & To map specifications.
# AS2 From & To Map
# This map translates incoming AS2From and AS2To http header parameters into PeopleSoft node names.
# This property is not required if your incoming messages use AS2From and AS2To parameters that match
# existing PeopleSoft node definitions.
# ig.AS2.AS2ListenerMap.From.<AS2From>= Specify the PSFT Source Node Name.
# ig.AS2.AS2ListenerMap.To.<AS2To>= Specify the PSFT Target Node Name.
# This example translate AS2From from AS2SENDER to PSFT_SRC_NODE, and AS2To from AS2RECEIVER to PSFT_TGT_NODE.
# example:
# ig.AS2.AS2ListenerMap.From.AS2SENDER=PSFT_SRC_NODE
# ig.AS2.AS2ListenerMap.To.AS2RECEIVER=PSFT_TGT_NODE
# AS2 Message name
# Message name used to publish AS2 transactions.
# Use this property if the incoming AS2 Message Name is not in the HTTP Header or the URL.
# Replace <source> and <target> with either the incoming AS2From and AS2To http header parameters .
# when those match existing PeopleSoft node definitions, or with the PeopleSoft nodes names specified in the
# AS2 From & To map above.
# ig.AS2.<source>.<target>.MessageName= Specify the Message Name
# example:
# ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.MessageName=AS2_ORDER_REQUEST
# These Properties need to be set to use either the AS2TargetConnector or the AS2ListeningConnector
# REQUIRED:
# AS2 Certificates
# CertificateAlias is the certificate of the AS2 Listening Node used to decrypt incoming messages.
# SignerCertificateAlias is the certificate of the AS2From trading partner of Listening Node used to verify
# the incoming signature.
# Replace <source> and <target> with either the incoming AS2From and AS2To http header parameters
# when those match existing PeopleSoft node definitions, or with the PeopleSoft nodes names specified in the
# AS2 From & To map above.
# ig.AS2.<source>.<target>.CertificateAlias = Specify the target AS2 Listening Node certificate alias.
# ig.AS2.<source>.<target>.SignerCertificateAlias = Specify the source AS2From trading partner certificate alias.
# example:
# ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.CertificateAlias=<GeneratedAS2certificatealias>
# ig.AS2.PSFT_SRC_NODE.PSFT_TGT_NODE.SignerCertificateAlias=<GeneratedAS2certificatealias>
## End of AS2ListeningConnector Only Properties
## AS2 Target Connector Properties
# These Properties need to be set to use the AS2TargetConnector
# AS2 Original Request Information Log Directory
# This is required for Async MDN only. The Async MDN receiver uses this directory
# to find original request information.
# example:
# ig.AS2.AS2Directory=c://temp//as2
## END of AS2 Target Connector Properties.
#XML dtd lookup flag
# true - enable dtd reference lookup dtd on gateway. this is also the default value.
# false - disable dtd reference lookup on gateway.
ig.dtdLookup=true
# Maximum active connections to be cached on gateway
# These are connections from gateway to peoplesoft application server
# Caching connections will improve integration broker throughput
ig.connection=10
##################### -
CF10 64bit Apache connector (mod_jk.so) does not work for Apache2.4.3 (win64), where can I get a module that works?
I get this error from Apache :
C:\www\Apache2.4\bin>httpd -t
httpd: Syntax error on line 741 of C:/www/Apache2.4/conf/httpd.conf: Syntax error on line 2 of C:/www/Apache2.4/conf/mod_jk.conf: Cannot load C:\\ColdFusion10\\config\\wsconfig\\1\\mod_jk.so into server: The specified procedure could not be found.
I have already tried manually extracting the pre-built mod_jk22.so from the wsconfig.jar with same results.
If I switch to Apache 2.2.22 64bit, it does work. what I need is to be able to run on Apache 2.4.Please check out this link.
http://rob.brooks-bilson.com/index.cfm/2012/2/21/Installing-ColdFusion-10-with-Apache-on-W indows
In this link, they are configuring with Apache 2.2 only.
When we were working colfusion 9 with Linux and apache, we had the same problem, it will work when it connect to Apache 2.0 but not with Apache 2.2 version. -
WebLogic 9.2 with Apache Connector Config
Hi I am new to this forum, WebLogic, and all Oracle products for that matter. I am a college intern and I have been asked to learn how to use WebLogic 9.2. I was told that they want it to be connected to apache with the mod_wl_22.so shared module for Apache. I have placed the module in the directory and added the LoadModule line to the httpd.conf file and the module loads fine. From reading through the WebLogic documentation I now know that I need to create a <Location> block in httpd.conf for the connector. I also know that the arguments that you need to use are WebLogicHost and WebLogicPort. So in my httpd.conf I have added the following.
<Location /weblogic>
WebLogicHost 10.15.107.90/weblogic
WebLogicPort 7001
</Location>
I also tried.....
<Location /weblogic>
WebLogicHost /weblogic
WebLogicPort 7001
</Location>
and.....
<Location /weblogic>
WebLogicHost 10.15.107.90
WebLogicPort 7001
</Location>
All with no luck. When I browse to http://10.15.107.90/weblogic I get nothing. Can anybody help me out here?
Thanks
ScottHi,
This is a template for 'httpd.conf'. Please make it sure that you are following this:
===
# Based upon the NCSA server configuration files originally by Rob McCool.
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs-2.0/> for detailed information about
# the directives.
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do not begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "C:/Program Files/Apache Group/Apache2" will be interpreted by the
# server as "C:/Program Files/Apache Group/Apache2/logs/foo.log".
# NOTE: Where filenames are specified, you must use forward slashes
# instead of backslashes (e.g., "c:/apache" instead of "c:\apache").
# If a drive letter is omitted, the drive on which Apache.exe is located
# will be used by default. It is recommended that you always supply
# an explicit drive letter in absolute paths, however, to avoid
# confusion.
### Section 1: Global Environment
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation (available
# at <URL:http://httpd.apache.org/docs-2.0/mod/mpm_common.html#lockfile>);
# you will save yourself a lot of trouble.
# Do NOT add a slash at the end of the directory path.
ServerRoot "C:/Program Files/Apache Group/Apache2"
# ScoreBoardFile: File used to store internal server process information.
# If unspecified (the default), the scoreboard will be stored in an
# anonymous shared memory segment, and will be unavailable to third-party
# applications.
# If specified, ensure that no two invocations of Apache share the same
# scoreboard file. The scoreboard file MUST BE STORED ON A LOCAL DISK.
#ScoreBoardFile logs/apache_runtime_status
# PidFile: The file in which the server should record its process
# identification number when it starts.
PidFile logs/httpd.pid
# Timeout: The number of seconds before receives and sends time out.
Timeout 300
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
KeepAlive On
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
MaxKeepAliveRequests 100
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
KeepAliveTimeout 15
## Server-Pool Size Regulation (MPM specific)
# WinNT MPM
# ThreadsPerChild: constant number of worker threads in the server process
# MaxRequestsPerChild: maximum number of requests a server process serves
<IfModule mpm_winnt.c>
ThreadsPerChild 250
MaxRequestsPerChild 0
</IfModule>
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses (0.0.0.0)
#Listen 12.34.56.78:80
Listen 80
# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available before they are used.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule access_module modules/mod_access.so
LoadModule actions_module modules/mod_actions.so
LoadModule alias_module modules/mod_alias.so
LoadModule asis_module modules/mod_asis.so
LoadModule auth_module modules/mod_auth.so
#LoadModule auth_anon_module modules/mod_auth_anon.so
#LoadModule auth_dbm_module modules/mod_auth_dbm.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
LoadModule cgi_module modules/mod_cgi.so
#LoadModule dav_module modules/mod_dav.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
LoadModule dir_module modules/mod_dir.so
LoadModule env_module modules/mod_env.so
#LoadModule expires_module modules/mod_expires.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule headers_module modules/mod_headers.so
LoadModule imap_module modules/mod_imap.so
LoadModule include_module modules/mod_include.so
#LoadModule info_module modules/mod_info.so
LoadModule isapi_module modules/mod_isapi.so
LoadModule log_config_module modules/mod_log_config.so
LoadModule mime_module modules/mod_mime.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
#LoadModule proxy_module modules/mod_proxy.so
#LoadModule proxy_connect_module modules/mod_proxy_connect.so
#LoadModule proxy_http_module modules/mod_proxy_http.so
#LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule negotiation_module modules/mod_negotiation.so
#LoadModule rewrite_module modules/mod_rewrite.so
LoadModule setenvif_module modules/mod_setenvif.so
#LoadModule speling_module modules/mod_speling.so
#LoadModule status_module modules/mod_status.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule userdir_module modules/mod_userdir.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
#LoadModule ssl_module modules/mod_ssl.so
LoadModule weblogic_module modules/mod_wl_20.so
# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
#ExtendedStatus On
### Section 2: 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. [email protected]
ServerAdmin [email protected]
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If this is not set to valid DNS name for your host, server-generated
# redirections will not work. See also the UseCanonicalName directive.
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address anyway, and this will make
# redirections work in a sensible way.
ServerName beatest.kpit.com:80
# UseCanonicalName: Determines how Apache constructs self-referencing
# URLs and the SERVER_NAME and SERVER_PORT variables.
# When set "Off", Apache will use the Hostname and Port supplied
# by the client. When set "On", Apache will use the value of the
# ServerName directive.
UseCanonicalName Off
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "C:/Program Files/Apache Group/Apache2/htdocs"
# Each directory to which Apache has access can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
# First, we configure the "default" to be a very restrictive set of
# features.
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
# This should be changed to whatever you set DocumentRoot to.
<Directory "C:/Program Files/Apache Group/Apache2/htdocs">
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
# Note that "MultiViews" must be named explicitly --- "Options All"
# doesn't give it to you.
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs-2.0/mod/core.html#options
# for more information.
Options Indexes FollowSymLinks
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# Options FileInfo AuthConfig Limit
AllowOverride None
# Controls who can get stuff from this server.
Order allow,deny
Allow from all
</Directory>
# UserDir: The name of the directory that is appended onto a user's home
# directory if a ~user request is received. Be especially careful to use
# proper, forward slashes here. On Windows NT, "Personal/My Website"
# is a more appropriate choice.
UserDir "My Documents/My Website"
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
# You must correct the path for the root to match your system's configured
# user directory location, e.g. "C:/WinNT/profiles/*/My Documents/My Website"
# or whichever, as appropriate.
#<Directory "C:/Documents and Settings/*/My Documents/My Website">
# AllowOverride FileInfo AuthConfig Limit
# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
# <Limit GET POST OPTIONS PROPFIND>
# Order allow,deny
# Allow from all
# </Limit>
# <LimitExcept GET POST OPTIONS PROPFIND>
# Order deny,allow
# Deny from all
# </LimitExcept>
#</Directory>
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
# The index.html.var file (a type-map) is used to deliver content-
# negotiated documents. The MultiViews Option can be used for the
# same purpose, but it is much slower.
DirectoryIndex index.html index.html.var
# AccessFileName: The name of the file to look for in each directory
# for additional configuration directives. See also the AllowOverride
# directive.
AccessFileName .htaccess
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<FilesMatch "^\.ht">
Order allow,deny
Deny from all
</FilesMatch>
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
TypesConfig conf/mime.types
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
DefaultType text/plain
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
<IfModule mod_mime_magic.c>
MIMEMagicFile conf/magic
</IfModule>
<IfModule mod_weblogic.c>
WebLogicCluster 127.0.0.1:7003,127.0.0.1:7004
WLLogFile C:/proxylog/wl-proxy.log
WLTempDir C:/temp/wl-proxy.log
MatchExpression /*
</IfModule>
<Location />
SetHandler weblogic-handler
WebLogicCluster 127.0.0.1:7003,127.0.0.1:7005
Debug ALL
WLLogFile C:/proxylog/wl-proxy.log
WLTempDir C:/temp/wl-proxy.log
DebugConfigInfo On
PathTrim /
DynamicServerList OFF
</Location>
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
HostnameLookups Off
# EnableMMAP: Control whether memory-mapping is used to deliver
# files (assuming that the underlying OS supports it).
# The default is on; turn this off if you serve from NFS-mounted
# filesystems. On some systems, turning it off (regardless of
# filesystem) can improve performance; for details, please see
# http://httpd.apache.org/docs-2.0/mod/core.html#enablemmap
#EnableMMAP off
# EnableSendfile: Control whether the sendfile kernel support is
# used to deliver files (assuming that the OS supports it).
# The default is on; turn this off if you serve from NFS-mounted
# filesystems. Please see
# http://httpd.apache.org/docs-2.0/mod/core.html#enablesendfile
#EnableSendfile off
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you do define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog logs/error.log
# LogLevel: Control the number of messages logged to the error.log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
# You need to enable mod_logio.c to use %I and %O
#LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio -
Coldfusion 8 /Apache Connector Bug??????
I have wasted almost 3 weeks now on this problem. It will
cost us $500 to get a answer if this is a bug on Coldfusion 8.
Almost ready to jump this ship and go to the Open source camp!
Install went fine.
Running Red Hat 4AES
Apache 2.0
ColdFusion 8
I rebuilt the connector about 10 times now....using
the following document
http://kb.adobe.com/selfservice/viewContent.do?externalId=121a0b29&sliceId=2
when I try to start Coldfusion I get the following error....
The ColdFusion 8 server is starting up and will be available
shortly.
======================================================================
Running the ColdFusion 8 connector wizard
======================================================================
Configuring the web server connector (Launched on the first
run of the ColdFusion 8 start script)
Running apache connector wizard...
=======================================
There was an error while running the connector wizard
Connector installation was not successful
=======================================
======================================================================
ColdFusion 8 has been started.
ColdFusion 8 will write logs to
/usr/coldfusion8/logs/cfserver.logCould use similar assistance with our CF8 Standard upgrade.
I have spent a week trying to upgrade our dedicated server
from CFMX7 to CF8 with no success. I submitted an Adobe support
request ticket (Case #0180044098) about five days ago, but am still
waiting for them to help me resolve the problem. Thought I would
post this in case someone can offer assistance while I am waiting
for the Adobe school solution.
Our server configuration is as follows:
-- LINUX version: REDHAT Enterprise 4 i686 on standard - WHM
X v3.1.0
-- Apache version: 2.0.63
-- MySQL version: 5.0.45-community
-- PHP version: 5.2.5
-- WebHost Manager: version 11.15.0
-- cPanel Version: 11.18.1-RELEASE, cPanel Build: 20683
Here is what I have done most recently:
(1) Uninstalled CF8 (for about the fourth time).
(2) Deleted /opt/coldfusionmx7 and /opt/coldfusion8
directories.
(3) Restarted Apache, ensured the httpd-devel version of
Apache was installed.
(4) Reinstalled CF8 (for about the 5th time); it is running
and appears to have installed successfully (except for Apache
connectors).
(5) Modified
/opt/coldfusion8/bin/connectors/apache_connector.sh as follows:
../../runtime/bin/wsconfig \
-server coldfusion \
-ws apache \
-dir /etc/httpd/conf \
-bin /usr/local/apache/bin/httpd \
-script /usr/local/apache/bin/apachectl \
-coldfusion
(6) Ran ./wsconfig -uninstall to remove old/incorrect
connectors.
(7) Ran ./wsconfig per the information below which indicated
that JRun Apache connector install was successful.
Here are the results of running the ./wsconfig ...
[root@_______ bin]# ./wsconfig -uninstall
[Wed Mar 05 01:15:06 2008] [warn] NameVirtualHost *:80 has no
VirtualHosts
Restarted Apache server
The Apache connector was removed from /etc/httpd/conf
[root@_______ bin]# ./wsconfig -server coldfusion -ws Apache
-dir /etc/httpd/conf -bin /usr/local/apache/bin/httpd -script
/usr/local/apache/bin/apachectl -coldfusion -v
Found JRun server coldfusion at 127.0.0.1:2930
Red Hat Enterprise Linux ES release 4 (Nahant Update 6)
Using Apache binary /usr/local/apache/bin/httpd
Using resource gcc3/mod_jrun20.so.20020903
Server version: Apache/2.0.63
Using Apache control script /usr/local/apache/bin/apachectl
Parsing Apache configuration file /etc/httpd/conf/httpd.conf
Exec'ing chmod 777 /opt/coldfusion8/runtime/lib/wsconfig/1
Set permission to 777 on
/opt/coldfusion8/runtime/lib/wsconfig/1
Red Hat Enterprise Linux ES release 4 (Nahant Update 6)
Using resource gcc3/mod_jrun20.so.20020903
Server version: Apache/2.0.63
Exec'ing chmod +x
/opt/coldfusion8/runtime/lib/wsconfig/1/mod_jrun20.so
Set permission to execute on
/opt/coldfusion8/runtime/lib/wsconfig/1/mod_jrun20.so
Created file
/opt/coldfusion8/runtime/lib/wsconfig/1/mod_jrun20.so
Red Hat Enterprise Linux ES release 4 (Nahant Update 6)
Using resource gcc3/mod_jrun20.so.20020903
Server version: Apache/2.0.63
Red Hat Enterprise Linux ES release 4 (Nahant Update 6)
Using resource gcc3/mod_jrun20.so.20020903
Server version: Apache/2.0.63
Wrote file /etc/httpd/conf/httpd.conf
Added JRun configuration to Apache configuration file
/etc/httpd/conf/httpd.conf
Created file
/opt/coldfusion8/runtime/lib/wsconfig/1/README.txt
Wrote file
/opt/coldfusion8/runtime/lib/wsconfig/wsconfig.properties
Exec'ing /usr/local/apache/bin/apachectl restart
[Wed Mar 05 01:21:18 2008] [warn] NameVirtualHost *:80 has no
VirtualHosts
Restarted Apache server
The Apache connector was installed to /etc/httpd/conf
[root@_______ bin]#
Although everything appears to have installed correctly, our
server and website will still not recognize or process .cfm files.
So I am still unable to even access CF8 Administrator and our site
will not process Coldfusion files, just asks me, "Do you want to
save this file, or find a program online to open it?"
Never had any problems with CFMX7 install or operation, so
this is most disconcerting.
I am not a happy camper.
Any suggestions while I am waiting for my Adobe customer
support ticket to be answered will be most appreciated.
Thanks. -
How to configure apache and weblogic in windows 2000
i am novice,
i want to configure apache and weblogic in windows 2000
weblogic version is 6.1
apache version is 2.0
how to do?George,
I would take the following 'first steps'
1)Install Apache20 on your Windows machine following the Apache online documentation
http://httpd.apache.org/docs-2.0/misc/tutorials.html
2)Make sure you can 'serve up' static HTML content from your Apache Server
3)Install Weblogic Server per our online documentation
http://edocs.bea.com/wls/docs61/install/index.html
4)Also, make sure you can 'serve up' both static and dynamic (e.g., JSP) content
directly from WLS server
5)Once you have both of the above 'sanity' checks attempt to configure a simple
proxy by ppath or mime type via our online documentation
http://edocs.bea.com/wls/docs61/adminguide/apache.html#103803
Chuck Nelson
DRE
BEA Technical Support -
How to configure apache for ssl in windows platform
hi all,
can anyone help me expalin how to configure apache for ssl in windows platform.George,
I would take the following 'first steps'
1)Install Apache20 on your Windows machine following the Apache online documentation
http://httpd.apache.org/docs-2.0/misc/tutorials.html
2)Make sure you can 'serve up' static HTML content from your Apache Server
3)Install Weblogic Server per our online documentation
http://edocs.bea.com/wls/docs61/install/index.html
4)Also, make sure you can 'serve up' both static and dynamic (e.g., JSP) content
directly from WLS server
5)Once you have both of the above 'sanity' checks attempt to configure a simple
proxy by ppath or mime type via our online documentation
http://edocs.bea.com/wls/docs61/adminguide/apache.html#103803
Chuck Nelson
DRE
BEA Technical Support -
Hi all!
My web server used apache.
OS:solaris
I have installed oracle client.
But i can not connected db with jdbc_oci.
How can i configure to implement web query?
Any help would be greatly appreciated.
Thanks,I have no experience with nginx and varnish and asking configuration problems regarding these products is perhaps beyond the scope of this forum.
While configuring varnish, we are getting issues and unable to connect server from my browser if I change port 80.
You did not describe the issues, but it is possible and very common that your IP Firewall is blocking access to ports other than 80 and 22. For testing, you can simply turn it off. If you do not know how, please post your OS distribution version first, as it all depends. -
I'd like to open a bug regarding the Apache connector. We first ran into it back in 7.0 and I just confirmed today it still exists in 8.1 (at least Apache 2.0/win32).
The bug is that the connector only forwards bodies for a subset of HTTP methods, so Webdav, for instance, is unusable via the connector.
For instance, the ACL method, RFC 3744, when sent to apache looks similar to
--- snip --
ACL /dav/testuser/foo2 HTTP/1.1
Host: localhost:80
Depth: Infinity
Content-Length: 690
Content-type: text/xml; charset="utf-8"
Connection: close
<?xml version="1.0" encoding="utf-8" ?>
<D:acl xmlns:D="DAV:">
<D:ace>
<D:principal>
<D:href>xxx</D:href>
</D:principal>
<D:grant>
<D:privilege> <D:read/> </D:privilege>
</D:grant>
</D:ace>
</D:acl>
but the BEA connector forwards this to BEA as:
-- snip---
ACL /dav/testuser/foo2 HTTP/1.1
Host: localhost:80
Depth: Infinity
Content-Length: 690
Content-type: text/xml; charset="utf-8"
Connection: Keep-Alive
WL-Proxy-SSL: false
WL-PATH-TRIM: /
WL-Proxy-Client-IP: 127.0.0.1
Proxy-Client-IP: 127.0.0.1
X-Forwarded-For: 127.0.0.1
X-WebLogic-Force-JVMID: unset
... which of course times out since the body is not sent but CL is (correctly) specified.
We have to ship our product with a separate apache module which changes all methods to a POST, then stuffs the real method in a header. Then in our special servlet that we ship just for BEA, we extract the real method from the header and use it instead of the POST in the ServletRequest.
Can someone with karma at BEA file this bug? Other methods with bodies that I suspect will probably fail include OPTIONS, PROPPATCH, & PROPFIND. I also verified that arbitrary (ie non-RFC'd) http methods will fail to transmit a body as well.
Our last customer who used our application with BEA was supposed to open a bug about this via standard support means but I don't have any record of it ever being done.
Thanks,
KeithHi. Please send me an email address and I'll do what I can.
j
o
e
b
e
a
c
o
m
Keith Wannamaker wrote:
I'd like to open a bug regarding the Apache connector. We first ran into it back in 7.0 and I just confirmed today it still exists in 8.1 (at least Apache 2.0/win32).
The bug is that the connector only forwards bodies for a subset of HTTP methods, so Webdav, for instance, is unusable via the connector.
For instance, the ACL method, RFC 3744, when sent to apache looks similar to
--- snip --
ACL /dav/testuser/foo2 HTTP/1.1
Host: localhost:80
Depth: Infinity
Content-Length: 690
Content-type: text/xml; charset="utf-8"
Connection: close
<?xml version="1.0" encoding="utf-8" ?>
<D:acl xmlns:D="DAV:">
<D:ace>
<D:principal>
<D:href>xxx</D:href>
</D:principal>
<D:grant>
<D:privilege> <D:read/> </D:privilege>
</D:grant>
</D:ace>
</D:acl>
but the BEA connector forwards this to BEA as:
-- snip---
ACL /dav/testuser/foo2 HTTP/1.1
Host: localhost:80
Depth: Infinity
Content-Length: 690
Content-type: text/xml; charset="utf-8"
Connection: Keep-Alive
WL-Proxy-SSL: false
WL-PATH-TRIM: /
WL-Proxy-Client-IP: 127.0.0.1
Proxy-Client-IP: 127.0.0.1
X-Forwarded-For: 127.0.0.1
X-WebLogic-Force-JVMID: unset
... which of course times out since the body is not sent but CL is (correctly) specified.
We have to ship our product with a separate apache module which changes all methods to a POST, then stuffs the real method in a header. Then in our special servlet that we ship just for BEA, we extract the real method from the header and use it instead of the POST in the ServletRequest.
Can someone with karma at BEA file this bug? Other methods with bodies that I suspect will probably fail include OPTIONS, PROPPATCH, & PROPFIND. I also verified that arbitrary (ie non-RFC'd) http methods will fail to transmit a body as well.
Our last customer who used our application with BEA was supposed to open a bug about this via standard support means but I don't have any record of it ever being done.
Thanks,
Keith -
Configure send connector for exchange online protection
Hello Forum members,
I am trying to configure send and receive connectors for Exchange 2010 to route
on-premises mailboxes to Exchange OnLine Protection. The "help" info MS provides
is for Ex 2013 - and the EAC GUI and config does not lend a close fit to using the 2010
Exch Management Console. How can I configure connectors to properly connect to the Exchange Online Protection?
I have seen where the ip addresses are posted, etc. I am unclear how to configure the properties on the SBS 2011/EX 2010 server.
Any tips will help,
Thanks,
Eric H.
Network and Server InstallsHello Wesleyhe,
You cannot use AD anything with EOP - if you mean exchange on-line protection.
you have to set a smart host on the SBS server to connect to EOP, you may need to add the EOP server ips to your network config
on the SBS server. the smart host line (for the send connector on SBS server) is something like: yourdomainname-com.mail.protection.outlook.com.
Then you need to configure the outside ip for your SBS server access in the EOP admin area.
Hope this helps.
eholz
Network and Server Installs -
Configuring Apache HTTP as an RPS
Longback i configured Apache HTTP as an Reverse proxy to weblogic for singlesignon with OAM.
that time i downloaded the Apache HTTP server Plugin from the below link
http://e-docs.bea.com/wls/docs92/plugins/apache.html
but after oracle aquiring the oracle i can not able to find the link for Apache plugin .
can any one please upadte the new url to download APACHE HTTP server pluginHi,
You can download the latest apache plugins from the below link.
http://www.oracle.com/technology/software/products/ias/htdocs/wls_main.html
Click on the "see all files" options of the Oracle WebLogic Server 10.3, and you can download the same under the
Mandatory for 10.3 installers.
Cheers,
Raj -
Configuring Apache HTTP as an RPS to weblogic for SSO on PSFT
Longback i configured Apache HTTP as an Reverse proxy to weblogic for singlesignon with OAM.
that time i downloaded the Apache HTTP server Plugin from the below link
http://e-docs.bea.com/wls/docs92/plugins/apache.html
but after oracle aquiring the oracle i can not able to find the link for Apache plugin .
can any one please upadte the new url to download APACHE HTTP server pluginIt seems the WebLogic Server plug-ins for Apache web server are available for download only through My Oracle Support (MetaLink)
Check below:
http://www.oracle.com/technology/deploy/security/wls-security/2793.html
The page mentions that the web server plug-in is available for download via Doc ID # 7825156.
You can also have a look at http://www.oracle.com/technology/deploy/security/alerts/alert_cve2008-3257.html
Hope this helps. -
What are the steps to configure SAP Connector?
Hi Experts,
Please explain me how to configure SAP Connectors?
By how many ways we can configure SAP Connector?
Thanks & Regards,
Sharma.Please search yourself before posting, ask specific questions only, do not post this question a third time.
Thread locked.
Thomas
[Asking Good Questions in the Forums to get Good Answers|/people/rob.burbank/blog/2010/05/12/asking-good-questions-in-the-forums-to-get-good-answers] -
Can we configure webserver to loaedbalance multiple weblogic clusters?
Can we configure webserver to loadbalance to multiple weblogic clusters?
E.g. Web server X -> Cluster Y & Cluster Z
In the plugin documentation it is not explicit that you can or can't do so.Refer:- http://download.oracle.com/docs/cd/E17904_01/web.1111/e16435/apache.htm#CDEHDGJG
http://download.oracle.com/docs/cd/E12839_01/web.1111/e13709/failover.htm#i1040344
-Akshay
Maybe you are looking for
-
"Headers and Footers" error message
Often when I'm in a topic and double-click on a template to open it and get some standard text, I get a dialog box called "Headers and Footers" which scolds me about "This topic was created from a template and the header and footer has been modified.
-
I was updating my Macbook Air (i7, 4mb RAM, 256 gb) to Yosemite OS when the process was interrupted. After retry, my computer is showing the following message: "this core storage operation is not allowed on a sparse logical volume group". I tried to
-
I turned my iphone off when visiting the doctor's surgery and now it won't turn back on. It had 73% battery left and I have tried connecting it to my computer with USB but nothing happens. I have taken out and replaced the sim card too. Any sugges
-
hello!i have lumia 620 for 2 weeks.today i changed the sim and i have to take out the back cover.when i put the cover back,the screen has a crack from one side to other and it smells a bit burnt.i have also a screen protector.it didnt fall down ever.
-
Hi guys. Do need some help here. My task is to design a LabVIEW design shematic to display the regeneration current drawn from the BLDC motor through Kelly Controller with an output voltage range of 0-5V. The Kelly Controller is to communicate with t