help with unzipping .ANT file for activiti share connector

[bizilux]

Hello everyone,

we have activiti v1.3.3 installed, and alfresco 5.0.2.5   I believe both are latest.

so I managed to get AD working on alfresco, that was monumental success… anyways, now im trying to connect activiti to alfresco… and im having problems… or rather, I am stuck and have no clue what to do.

Provided documentation gives VERY LITTLE useful information when it comes to using .AMP files

It says:

Unzip the activiti.alfresco.repo-demo-ldap-X.X.X.amp file and take a look at the files, the settings you should pay most attention to are the ones marked with ACTIVITI SHARE CONNECTOR DEMO inside the ldap-authentication.properties file. Configure it to match your own LDAP, turn it back into an amp and finally drop it into your Alfresco One repository´s amps folder.
‍‍

Well thank you very much, but how do I do all of that? I have searched for over an hour online and everywhere, and i cannot find useful information about how to unzip this damn .AMP file… all I saw was some command lines, but where the heck do I put them in? I tried CMD and everything, and downloaded ANT and all that… no luck.


Can you please tell me how to open this god forsaken amp file?

[bizilux]

Workflow Admin Console maybe?  or Model and Messages Console? 

well im lost…

[bizilux]

I am nowhere closer than I was on friday…

I did manage to get Single sign on working with alfresco, so yeah… thats good.  Now I really just need to connect Alfresco and Activiti and I can start working

[erikwinlof]

Hi bizilux!

The .amp files are simply a .zip file, so the easiest thing is to rename them from .amp to .zip and then expand them like any other .zip file. But perhaps you already got by that since you said you managed to get single sign on working with Alfresco?

Feel free to post more question here and ill watch them, but generally when installing the Share connector for the first time I would recommend following the "Demo setup" section:
http://docs.alfresco.com/activiti/docs/admin-guide/1.3.2/#_demo_setup

Cheers, Erik

[bizilux]

Actually not hehe, I didnt get that, thats exactly what i was looking for… simply renaming .amp into .zip  
thats exactly where i got stuck… and funny thing is, I actually said to myself, what if i try to rename it into .zip, but then I started googling some other stuff and simply forgot about that

Yes i did manage to get SSO working with alfresco, but for SSO you dont need to fiddle with any .amp files

Thanks a bunch and happy holidays!

[bizilux]

Actually… I tried doing it… turns out i broke whole alfresco… searched a bit online, and deleted share.war and put backed share.war in that place, and deleted bunch of other stuff… and restarted alfresco, it kind of worked with ton of errors… so now im waiting for admins to make whole server restore from this morning

so yeah… turns out .amp files can really fuck up your day


All i did was this:
<code> Unzip the activiti.alfresco.repo-demo-ldap-X.X.X.amp file and take a look at the files, the settings you should pay most attention to are the ones marked with ACTIVITI SHARE CONNECTOR DEMO inside the ldap-authentication.properties file. Configure it to match your own LDAP, turn it back into an amp and finally drop it into your Alfresco One repository´s amps folder.

Deploy AMPs
If you don’t already have one installed, make sure you install an Alfresco One 4.0, 4.1, 4.2 or 5.0 server.

From the activiti-share-connector.zip copy the amps to the correct amps folder in your Alfresco One installation:

<zip>/alfresco/amps/activiti.alfresco.repo-X.X.X.amp           to <alfresco-dir>/amps
<zip>/alfresco/amps_share/activiti.alfresco.share-X.X.X.amp    to <alfresco-dir>/amps_share
Install the amps into Alfresco One by running the following command on a terminal from within your Alfresco One installation directory, and then follow its instructions:

bin/apply_amps.sh</code>

and i didnt do bin/apply_amps.sh … instead i went to bin folder and clicked apply_amps.bat   … then cmd opened up, and i had to press a key, and then again key to delete temporary stuff… and then it went on for like 1 more second and window closed… so i assume something broke along the way…

any tips on how to avoid using whole server backup next time i try to do this again? because it takes few hours to do restore backup 😕

I will use Module Management Tool (MMT) this time… but i doubt that will solve much. I think something is wrong with my settings in ldap-authentication.properties file…

it looks like this:
<code>############################
#  LDAP AD Authentication  #
############################

authentication.chain=alfinst:alfrescoNtlm,kerberos1:kerberos,ldap1:ldap-ad

ntlm.authentication.sso.enabled=false


# This flag enables use of this LDAP subsystem for authentication. It may be
# that this subsystem should only be used for synchronization, in which case
# this flag should be set to false.
ldap.authentication.active=true

# This properties file brings together the common options for LDAP authentication rather than editing the bean definitions
ldap.authentication.allowGuestLogin=true

# How to map the user id entered by the user to that passed through to LDAP
# In Active Directory, this can either be the user principal name (UPN) or DN.
# UPNs are in the form <sAMAccountName>@domain and are held in the userPrincipalName attribute of a user
ldap.authentication.userNameFormat=%s@SKB.LOCAL


# The LDAP context factory to use
ldap.authentication.java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory

# The URL to connect to the LDAP server
ldap.authentication.java.naming.provider.url=XXX

# The authentication mechanism to use
ldap.authentication.java.naming.security.authentication=simple

# Escape commas entered by the user at bind time
# Useful when using simple authentication and the CN is part of the DN and contains commas
ldap.authentication.escapeCommasInBind=false

# Escape commas entered by the user when setting the authenticated user
# Useful when using simple authentication and the CN is part of the DN and contains commas, and the escaped \, is
# pulled in as part of an LDAP sync
# If this option is set to true it will break the default home folder provider as space names can not contain
ldap.authentication.escapeCommasInUid=false

# Comma separated list of user names who should be considered administrators by default
ldap.authentication.defaultAdministratorUserNames=Administrator,janremic,tomazpevc,tadejremic,jozepiskur,admin

##############################
#   LDAP AD Synchronization  #
##############################

# This flag enables use of this LDAP subsystem for user and group
# synchronization. It may be that this subsytem should only be used for
# authentication, in which case this flag should be set to false.
ldap.synchronization.active=true

# The default principal to bind with (only used for LDAP sync). This should be a UPN or DN
ldap.synchronization.java.naming.security.principal=XXX

# The password for the default principal (only used for LDAP sync)
ldap.synchronization.java.naming.security.credentials=XXX

# If positive, this property indicates that RFC 2696 paged results should be
# used to split query results into batches of the specified size. This
# overcomes any size limits imposed by the LDAP server.
ldap.synchronization.queryBatchSize=1000

# If positive, this property indicates that range retrieval should be used to fetch
# multi-valued attributes (such as member) in batches of the specified size.
# Overcomes any size limits imposed by Active Directory.       
ldap.synchronization.attributeBatchSize=1000

# The query to select all objects that represent the groups to import.
ldap.synchronization.groupQuery=(objectclass\=group)

#####################################
# The query to select objects that represent the groups to import that have changed since a certain time.
# OB PRVEM ZAGONU JE POTREBNO PRENESTI VSE UPORABNIKE IN SKUPINE IZ AD ZATO JE POTREBNO SPODNJO NASTAVITEV ZAKOMENTIRATI
# (POTEM ODKOMENTIRAMO, DA NAM SINHRONIZIRA LE SPREMEMBE)
# ENAK POSTOPEK TUDI KO LE ZELIMO PRENESTI VSE UPORABNIKE IN SKUPINE IZ AD
ldap.synchronization.groupDifferentialQuery=(&(objectclass\=group)(!(modifyTimestamp<\={0})))
#####################################

# The query to select all objects that represent the users to import.
ldap.synchronization.personQuery=(&(objectclass\=user)(userAccountControl\:1.2.840.113556.1.4.803\:\=512))

#####################################
# The query to select objects that represent the users to import that have changed since a certain time.
# OB PRVEM ZAGONU JE POTREBNO PRENESTI VSE UPORABNIKE IN SKUPINE IZ AD ZATO JE POTREBNO SPODNJO NASTAVITEV ZAKOMENTIRATI
# (POTEM ODKOMENTIRAMO, DA NAM SINHRONIZIRA LE SPREMEMBE)
# ENAK POSTOPEK TUDI KO LE ZELIMO PRENESTI VSE UPORABNIKE IN SKUPINE IZ AD
ldap.synchronization.personDifferentialQuery=(&(objectclass\=user)(userAccountControl\:1.2.840.113556.1.4.803\:\=512)(!(modifyTimestamp<\={0})))
#####################################

# The group search base restricts the LDAP group query to a sub section of tree on the LDAP server.
ldap.synchronization.groupSearchBase=OU\=Domain Groups,DC\=skb,DC\=local

# The user search base restricts the LDAP user query to a sub section of tree on the LDAP server.
ldap.synchronization.userSearchBase=DC\=skb,DC\=local

# The name of the operational attribute recording the last update time for a group or user.
ldap.synchronization.modifyTimestampAttributeName=modifyTimestamp

# The timestamp format. Unfortunately, this varies between directory servers.
ldap.synchronization.timestampFormat=yyyyMMddHHmmss'.0Z'

# The attribute name on people objects found in LDAP to use as the uid in Alfresco
ldap.synchronization.userIdAttributeName=sAMAccountName

# The attribute on person objects in LDAP to map to the first name property in Alfresco
ldap.synchronization.userFirstNameAttributeName=givenName

# The attribute on person objects in LDAP to map to the last name property in Alfresco
ldap.synchronization.userLastNameAttributeName=sn

# The attribute on person objects in LDAP to map to the email property in Alfresco
ldap.synchronization.userEmailAttributeName=mail

# The attribute on person objects in LDAP to map to the organizational id  property in Alfresco
ldap.synchronization.userOrganizationalIdAttributeName=company

# The default home folder provider to use for people created via LDAP import
ldap.synchronization.defaultHomeFolderProvider=userHomesHomeFolderProvider

# The attribute on LDAP group objects to map to the authority name property in Alfresco
ldap.synchronization.groupIdAttributeName=cn

# The attribute on LDAP group objects to map to the authority display name property in Alfresco
ldap.synchronization.groupDisplayNameAttributeName=displayName

# The group type in LDAP
ldap.synchronization.groupType=group

# The person type in LDAP
ldap.synchronization.personType=user

# The attribute in LDAP on group objects that defines the DN for its members
ldap.synchronization.groupMemberAttributeName=member

# If true progress estimation is enabled. When enabled, the user query has to be run twice in order to count entries.
ldap.synchronization.enableProgressEstimation=true




# ACTIVITI SHARE CONNECTOR DEMO
# The authentication mechanism to use for synchronization
ldap.synchronization.java.naming.security.authentication=simple

# ACTIVITI SHARE CONNECTOR DEMO The attribute name on people objects found in LDAP to use as the uid in Alfresco
#ldap.synchronization.userIdAttributeName=uid</code>
note: those XXX values are masked for safety reasons i guess…

I didnt use activiti.alfresco.repo-1.3.2.amp    , but i used activiti.alfresco.repo-demo-ldap-1.0.0.amp    which is the one i was changing… I noticed that non demo amp is much bigger in size… so i wonder whats up with that… it does not have ldap-authentication.properties file  though… so im really confused as to what i should do 😕

[erikwinlof]

Hi again, hope you had a nice holiday!

I'm improving the docs right now so they mention that you shall unzip the .amp by renaming it, thanks for the feedback. I have also added a comment that, when re-creating the .amp, you shall pay attention to the folder structure you have created and make sure that it matches the original .amp file's paths, more specifically that the root folders are the same and that you have not added in a new top level root directory in your new .zip file. So make sure to do the same.

When it comes to backing up your Alfresco server I have no recommendations. The amp deployment tool is meant to do that be saving the previous version of your alfresco.war and share.war files but it sounds like something might have gone wrong when clicking it and thus running it from the "'bin' folder" instead of from "the folder above the 'bin' folder" using a terminal.

Do note that the activiti.alfresco.repo-1.3.2.amp and activiti.alfresco.repo-demo-ldap-1.0.0.amp are meant for 2 completely different things. The former contains the actual Share connector files to make the Alfresco repository communicate with Activiti. The latter contains sample settings to get Alfresco running with an Apache DS server (which is what will start up if you use the activiti-demo-ldap.war). I have added this information to the docs as well.

When it comes to getting your Alfresco LDAP settings right for your LDAP server I think you should visit the Alfresco One forums instead. The settings I have added in ldap-authentication.properties is to communicate with ApacheDS server running in webapps-ldap/activiti-demo-ldap.war). If you use that it shall work without any modifications, if you are using another LDAP server you need to read its own manual or consult the Alfresco One forum.

Cheers and good luck!

[bizilux]

Hey erikwinlof, thanks for your reply….

yes, its true when i was re-creating .amp file, I zipped it and it broke folder structure because it adds one more folder into it… so I had to do some tweaking there.

yes, before when i broke everything, i just double clicked apply_amps.bat and it broke everything when i pressed key to continue… Not really sure what happened before. I do remember that i didnt put activiti.alfresco.repo-1.3.2.amp into amps folder so yeah maybe that broke everything then… because those connections were missing

3 hours ago I tried it again, this time i used run window, and typed in path to apply_amps.bat, and ran it from there, which should be the same as double clicking it i think… but yeah this time it went on… like i said on first try it didnt load my .amp file because folder structure was wrong, so i changed it, and re-ran apply_amps.bat, and then it went on without problems, so now i have these 3 .amps installed.


(AD and SSO (kerberos) were both working just fine on alfresco… so what i did was, i copied most of stuff from my working alfresco AD properties, to ldap-authentication.properties inside .amp)

now here is the catch, after applying those 3 amps. alfresco wont start… and I get no useful errors in alfresco.log, but I do get some in tomcat logs

there are some SEVERE errors preventing share from starting… obviously they have to do with these 3 new .amp files… I will try to fiddle again with ldap-authentication.properties file in that .amp, and redeploying it again… but yeah, if you can help somehow, that would be great. The thing is… im not sure wether its that properties file inside .amp, or if its some other stuff, because i followed all steps, even those that have to do with changing activiti files… but activiti starts just fine… so I think its something to do with that demo .amp… I will try and change some values in it.

if i try to open my share/alfresco in chrome, i get this error.
<code>HTTP Status 404 - /share
type Status report
message /share
description The requested resource is not available.
Apache Tomcat/7.0.59</code>


and this is how my log files look like: alfrescotomcat-stderr.log
<blockcode>2016-01-04 11:59:29 Commons Daemon procrun stderr initialized
jan. 04, 2016 11:59:30 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: Loaded APR based Apache Tomcat Native library 1.1.32 using APR version 1.5.1.
jan. 04, 2016 11:59:30 AM org.apache.catalina.core.AprLifecycleListener lifecycleEvent
INFO: APR capabilities: IPv6 [true], sendfile [true], accept filters [false], random [true].
jan. 04, 2016 11:59:31 AM org.apache.catalina.core.AprLifecycleListener initializeSSL
INFO: OpenSSL successfully initialized (OpenSSL 1.0.1j 15 Oct 2014)
jan. 04, 2016 11:59:31 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-apr-8080"]
jan. 04, 2016 11:59:31 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["ajp-apr-8019"]
jan. 04, 2016 11:59:31 AM org.apache.coyote.AbstractProtocol init
INFO: Initializing ProtocolHandler ["http-bio-8443"]
jan. 04, 2016 11:59:32 AM org.apache.catalina.startup.Catalina load
INFO: Initialization processed in 1973 ms
jan. 04, 2016 11:59:32 AM org.apache.catalina.core.StandardService startInternal
INFO: Starting service Catalina
jan. 04, 2016 11:59:32 AM org.apache.catalina.core.StandardEngine startInternal
INFO: Starting Servlet Engine: Apache Tomcat/7.0.59
jan. 04, 2016 11:59:32 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deploying configuration descriptor C:\Alfresco\Alfresco5.0.2.5\tomcat\conf\Catalina\localhost\solr4.xml
jan. 04, 2016 11:59:32 AM org.apache.catalina.startup.SetContextPropertiesRule begin
WARNING: [SetContextPropertiesRule]{Context} Setting property 'debug' to '0' did not find a matching property.
jan. 04, 2016 11:59:41 AM org.apache.catalina.startup.HostConfig deployDescriptor
INFO: Deployment of configuration descriptor C:\Alfresco\Alfresco5.0.2.5\tomcat\conf\Catalina\localhost\solr4.xml has finished in 9,484 ms
jan. 04, 2016 11:59:42 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\alfresco.war
jan. 04, 2016 11:59:44 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error listenerStart
jan. 04, 2016 11:59:44 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/alfresco] startup failed due to previous errors
jan. 04, 2016 11:59:44 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\alfresco.war has finished in 2,711 ms
jan. 04, 2016 11:59:44 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\ROOT.war
jan. 04, 2016 11:59:44 AM org.apache.catalina.startup.SetContextPropertiesRule begin
WARNING: [SetContextPropertiesRule]{Context} Setting property 'debug' to '100' did not find a matching property.
jan. 04, 2016 11:59:44 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\ROOT.war has finished in 198 ms
jan. 04, 2016 11:59:44 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\share.war
jan. 04, 2016 11:59:45 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Error listenerStart
jan. 04, 2016 11:59:45 AM org.apache.catalina.core.StandardContext startInternal
SEVERE: Context [/share] startup failed due to previous errors
jan. 04, 2016 11:59:45 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\share.war has finished in 701 ms
jan. 04, 2016 11:59:45 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deploying web application archive C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\_vti_bin.war
jan. 04, 2016 11:59:45 AM org.apache.catalina.startup.HostConfig deployWAR
INFO: Deployment of web application archive C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\_vti_bin.war has finished in 124 ms
jan. 04, 2016 11:59:45 AM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\alfresco-1451900180736.bak
jan. 04, 2016 12:00:53 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\alfresco-1451900180736.bak has finished in 68,019 ms
jan. 04, 2016 12:00:53 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\host-manager
jan. 04, 2016 12:00:53 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\host-manager has finished in 77 ms
jan. 04, 2016 12:00:53 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\manager
jan. 04, 2016 12:00:53 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory C:\Alfresco\Alfresco5.0.2.5\tomcat\webapps\manager has finished in 64 ms
jan. 04, 2016 12:00:53 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-apr-8080"]
jan. 04, 2016 12:00:53 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-apr-8019"]
jan. 04, 2016 12:00:53 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-8443"]
jan. 04, 2016 12:00:53 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 81953 ms
na.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jsp/jstl/core is already defined
jan. 04, 2016 11:59:56 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/fmt_rt is already defined
jan. 04, 2016 11:59:56 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/fmt is already defined
jan. 04, 2016 11:59:56 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jsp/jstl/fmt is already defined
jan. 04, 2016 11:59:56 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jsp/jstl/functions is already defined
jan. 04, 2016 11:59:56 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://jakarta.apache.org/taglibs/standard/permittedTaglibs is already defined
jan. 04, 2016 11:59:56 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://jakarta.apache.org/taglibs/standard/scriptfree is already defined
jan. 04, 2016 11:59:56 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/sql_rt is already defined
jan. 04, 2016 11:59:56 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/sql is already defined
jan. 04, 2016 11:59:56 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jsp/jstl/sql is already defined
jan. 04, 2016 11:59:56 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/xml_rt is already defined
jan. 04, 2016 11:59:56 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jstl/xml is already defined
jan. 04, 2016 11:59:56 AM org.apache.catalina.startup.TaglibUriRule body
INFO: TLD skipped. URI: http://java.sun.com/jsp/jstl/xml is already defined
jan. 04, 2016 11:59:56 AM org.apache.catalina.core.ApplicationContext log
INFO: No Spring WebApplicationInitializer types detected on classpath
jan. 04, 2016 11:59:57 AM org.apache.catalina.core.ApplicationContext log
INFO: Initializing Spring root WebApplicationContext
jan. 04, 2016 12:00:30 PM org.artofsolving.jodconverter.office.ProcessPoolOfficeManager <init>
INFO: ProcessManager implementation is PureJavaProcessManager
jan. 04, 2016 12:00:30 PM org.artofsolving.jodconverter.office.OfficeProcess start
INFO: Using GNU based LibreOffice command: [C:\Alfresco\Alfresco5.0.2.5\libreoffice\App\libreoffice\program\soffice.bin, –accept=socket,host=127.0.0.1,port=8100;urp;, -env:UserInstallation=file:///C:/Alfresco/ALFRES~1.5/tomcat/temp/.jodconverter_socket_host-127.0.0.1_port-8100, –headless, –nocrashreport, –nodefault, –nofirststartwizard, –nolockcheck, –nologo, –norestore]
jan. 04, 2016 12:00:30 PM org.artofsolving.jodconverter.office.OfficeProcess start
INFO: Using GNU based LibreOffice 3.6 command: [C:\Alfresco\Alfresco5.0.2.5\libreoffice\App\libreoffice\program\soffice.bin, –accept=socket,host=127.0.0.1,port=8100;urp;, -env:UserInstallation=file:///C:/Alfresco/ALFRES~1.5/tomcat/temp/.jodconverter_socket_host-127.0.0.1_port-8100, –headless, –nocrashreport, –nodefault, –nofirststartwizard, –nolockcheck, –nologo, –norestore]
jan. 04, 2016 12:00:30 PM org.artofsolving.jodconverter.office.OfficeProcess start
INFO: starting process with acceptString 'socket,host=127.0.0.1,port=8100,tcpNoDelay=1' and profileDir 'C:\Alfresco\ALFRES~1.5\tomcat\temp\.jodconverter_socket_host-127.0.0.1_port-8100'
jan. 04, 2016 12:00:30 PM org.artofsolving.jodconverter.office.OfficeProcess start
INFO: started process
jan. 04, 2016 12:00:32 PM org.artofsolving.jodconverter.office.ManagedOfficeProcess$6 attempt
WARNING: office process died with exit code 81; restarting it
jan. 04, 2016 12:00:32 PM org.artofsolving.jodconverter.office.OfficeProcess start
INFO: Using GNU based LibreOffice command: [C:\Alfresco\Alfresco5.0.2.5\libreoffice\App\libreoffice\program\soffice.bin, –accept=socket,host=127.0.0.1,port=8100;urp;, -env:UserInstallation=file:///C:/Alfresco/ALFRES~1.5/tomcat/temp/.jodconverter_socket_host-127.0.0.1_port-8100, –headless, –nocrashreport, –nodefault, –nofirststartwizard, –nolockcheck, –nologo, –norestore]
jan. 04, 2016 12:00:32 PM org.artofsolving.jodconverter.office.OfficeProcess start
INFO: Using GNU based LibreOffice 3.6 command: [C:\Alfresco\Alfresco5.0.2.5\libreoffice\App\libreoffice\program\soffice.bin, –accept=socket,host=127.0.0.1,port=8100;urp;, -env:UserInstallation=file:///C:/Alfresco/ALFRES~1.5/tomcat/temp/.jodconverter_socket_host-127.0.0.1_port-8100, –headless, –nocrashreport, –nodefault, –nofirststartwizard, –nolockcheck, –nologo, –norestore]
jan. 04, 2016 12:00:32 PM org.artofsolving.jodconverter.office.OfficeProcess start
INFO: starting process with acceptString 'socket,host=127.0.0.1,port=8100,tcpNoDelay=1' and profileDir 'C:\Alfresco\ALFRES~1.5\tomcat\temp\.jodconverter_socket_host-127.0.0.1_port-8100'
jan. 04, 2016 12:00:32 PM org.artofsolving.jodconverter.office.OfficeProcess start
INFO: started process
jan. 04, 2016 12:00:33 PM org.artofsolving.jodconverter.office.OfficeConnection connect
INFO: connected: 'socket,host=127.0.0.1,port=8100,tcpNoDelay=1'
jan. 04, 2016 12:00:49 PM com.sun.xml.ws.transport.http.servlet.WSServletContextListener contextInitialized
INFO: WSSERVLET12: JAX-WS context listener initializing
jan. 04, 2016 12:00:53 PM com.sun.xml.ws.transport.http.servlet.WSServletDelegate <init>
INFO: WSSERVLET14: JAX-WS servlet initializing</blockcode>

localhost.log file
<blockcode>jan. 04, 2016 11:59:44 AM org.apache.catalina.core.ApplicationContext log
INFO: No Spring WebApplicationInitializer types detected on classpath
jan. 04, 2016 11:59:44 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Error configuring application listener of class org.apache.myfaces.webapp.StartupServletContextListener
java.lang.NoClassDefFoundError: javax/faces/context/ExternalContext
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Unknown Source)
at java.lang.Class.getConstructor0(Unknown Source)
at java.lang.Class.newInstance(Unknown Source)
at org.apache.catalina.core.DefaultInstanceManager.newInstance(DefaultInstanceManager.java:116)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4932)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5524)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:901)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:877)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:649)
at org.apache.catalina.startup.HostConfig.deployWAR(HostConfig.java:1081)
at org.apache.catalina.startup.HostConfig$DeployWar.run(HostConfig.java:1877)
at java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
at java.util.concurrent.FutureTask.run(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.ClassNotFoundException: javax.faces.context.ExternalContext
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1720)
at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1571)
… 18 more

jan. 04, 2016 11:59:44 AM org.apache.catalina.core.StandardContext listenerStart
SEVERE: Skipped installing application listeners due to previous error(s)

</blockcode>

[erikwinlof]

Hi,

To me those errors suggest something is seriously wrong (classes missing etc), something that probably happened in previous steps where you had problems. I would suggest first doing the "Demo setup" installation against a fresh alfresco installation and see if you get that running. Once that is done try to do the same thing against your own alfresco server.


When that is ok, try moving over to your own alfresco server.

[bizilux]

Hi, 

thanks for reply. We had to do a restore of server again, because after unistalling these .amps with mmt, it still didnt want to start up, and there were some errors about some files that werent deleted and were left over, and even old .war backups didnt want to work anymore… so yeah thanks god for restores i guess. I do have really good documentation written (I write it as I go), so yeah it wouldnt be a problem to start installing alfresco and activiti from scratch, since i only had some test processes going on, nothing major.

Now i will move my alfresco and activiti into one folder, and then i will install new alfresco and activiti according to that demo setup, and then try to see if connector will be working. If it will be, then i will just configure files from this new demo setup to use our AD and SSO and outlook configs, and not the other way around… hopefully that will be working then.

Its a bit foggy to me about which LDAP server/AD will be used with demo setup… there is really no mentions of changing any properties file inside .amp file….so I can only assume that it will use some alfrescos test database? Well it has to i suppose… Im gonna find out soon enough, just need to wait for server administrators to give me more space. I will report back with what i've come up with.